Overview
Scrum is a framework that enhances the management of software development. It is a flexible, holistic, and incremental strategy that development teams rely upon to reach a common goal and to mitigate the challenges that creep in at the later stages of software development.
As the course moves through the disciplines promoted by Scrum, learners will gain a comprehensive hands-on understanding of this agile product development methodology while specifically reviewing the behaviors expected of a product owner. While many of us may be accustomed to the practice of establishing value and priority across projects, the product owner needs to consider value and priority across the features of a single project.
After successfully completing this training, participants will be registered with the Scrum Alliance as Certified Scrum Product Owners (CSPO), and will have online access to the class training materials and any updates for one year. PMPs can also claim 14 PDU’s with the PMI.
What You'll Learn
- The agile principle of software development
- The scrum framework and its origin
- Different scrum roles
- Planning & scheduling principles
- Prioritizing tasks & sub-tasks
- Meetings & sprint planning
- Project management variables & velocity
Curriculum
- How manufacturing has influenced software development
- The origins of agile thinking
- The Agile manifesto
- The complexity of projects
- Theoretical vs. empirical processes overview
- The “Iron Triangle” of project management
- Exercise: The “Art of the Possible”
- Exercise: The Ball Point game
- The different scrum roles
- Chickens and pigs
- Iterative development vs. waterfall
- Self-management concepts
- Full disclosure and visibility
- The scrum framework overview
- Exercise: The 59-minute scrum simulation
- The Team Member
- The Product Owner
- The Scrum Master
- Exercise: Product and project planning in an agile scrum environment
- Defining the product vision
- The contents of the product backlog
- Prioritizing our time spent on the product backlog
- Using user stories
- Bill Wake’s INVEST model
- Product backlog granularity
- Relative effort
- Planning poker and story points
- Ideal team days
- Team capacity
- Projecting a schedule
- Project management variables and velocity
- Bringing prioritization into a project
- Themes and relative weighted priority
- Prioritization questions and considerations
- The value of increasing our understanding
- The value of risk reduction
- Fixed date contracts
- Product backlog refactoring (“Grooming”)
- Release management
- The impact of project switching
- The impact of continuous forced marches
- Earned value in an agile environment
- A chart of scrum meetings
- The product backlog
- Sprint planning
- The sprint backlog
- The sprint
- The daily scrum
- Gathering Metrics
- The sprint demo/review
- Getting to “Done”
- The retrospective
- Why plan?
- Weighted impacts
- Theme screening
- Kano modeling
- The meta-scrum
- The scrum of scrums
- The integration scrum team
- Scaling scrum
- Developing architecture
- Where to go next with your scrum experience
- Some recommended reading
- Scrum reference materials
- Graduation ceremony
Who should attend
- Product Managers/Business Analysts
- Functional/Operational Managers/Directors
- Project Sponsors
- Project Managers
- Digital Experience Managers
- IT Leadership (Managers/Directors/VPs/CIOs/CTOs)
- Software Developers
- Product Architects
- Quality Assurance Managers
- Anyone interested in learning the benefits of Scrum for Product Management
