Professional Scrum Developer (PSD-I) – Contenuti

Contenuti dettagliati del Corso

  • Scrum
    • Agile Manifesto for Software Development
    • Why a Framework?
    • The Pillars of Scrum (Transparency, Inspection,Adaptation)
    • Scrum Roles (Product Owner, Development Team, Scrum Master, Others)
    • Scrum Artifacts (Product Backlog, Sprint Backlog, Increment, Others)
    • Scrum Events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, Other)
  • Application Lifecycle Management
    • What Is ALM?
    • Azure DevOps Services and Azure DevOps Server
    • Board
    • Pipelines
    • Repos
    • Artifacts
    • Test Plans
    • Design a version control strategy
    • Implement and integrate source control
    • CASE STUDY
  • Design and implement an Agile work management approach
    • identify and recommend project metrics, KPIs, and DevOps measurements (e.g., cycle time, lead time, WIP limit)
    • implement tools and processes to support Agile work management
    • mentor team members on Agile techniques and practices
    • recommend an organization structure that supports scaling Agile practices
    • recommend in-team and cross-team collaboration mechanisms
  • The Product Backlog
    • Refining the product Backlog
    • Evolution of a PBI
    • How we Estimate the best
    • Estimation in hours is not required
    • To be more accurate be less precise
    • Planning Poker
    • Anchoring
    • SPRINT 1
      • Activity: Sprint Planning
      • Activity: Development
      • Activity: Sprint Review
      • Activity: Sprint Retrospective
  • Agile Testing
    • Development with and without testing
    • Test in parallel with coding
    • Acceptance test driven development
    • Three types of testing
    • Development Test == Unit Test
    • Test driven Development
    • Code Coverage
    • User acceptance test
    • SPRINT 2
      • Activity: Sprint Planning
      • Activity: Development
      • Activity: Sprint Review
      • Activity: Sprint Retrospective
  • Emergent Architectures
    • Fit for Purpose
    • Architecture != Business Value
    • Allow architecture to emerge
    • Thinks in slices not in layers
    • Minimize documentation
    • SPRINT 3
      • Activity: Sprint Planning
      • Activity: Development
      • Activity: Sprint Review
      • Activity: Sprint Retrospective
  • Quality Code
    • Developing Vs. Coding
    • Quality Code == Quality Software
    • SOLID
    • Clean Code
    • Continuos Integration
    • Continuos Feedback
    • Refactoring
    • Technical Debt
    • SPRINT 4
      • Activity: Sprint Planning
      • Activity: Development
      • Activity: Sprint Review
      • Activity: Sprint Retrospective
  • Scrum Challenges
    • Common Scrum Challenges
    • Common Development Team Dysfunctions
    • Working as a Team
    • Become a High Performance Scrum Development Team
  • Closing and Next Step