All topics mentioned below will be followed by some activities to learn better.
Day 1:
Introduction to SCRUM and Agile
• What is the basis for Agile?
• What is the difference between Agile and traditional approaches like waterfall?
• When should you consider an Agile approach?
• When is waterfall or another approach appropriate?
• What project characteristics situations make it difficult for Agile to be successful?
Agile Manifesto!
• Define and describe the four values of Agile as stated in the Agile Manifesto
Empirical and defined processes
• Define and describe the two terms, including a description of inspect, adapt, and transparency as the three legs of an empirical process.
• Describe how the Scrum Framework is based on empirical process.
The Five Scrum Values
• Identify the five Scrum values and use examples of how Scrum practices support the application of each.
SCRUM Roles and Responsibilities
• Learn the basic rules of Scrum.
• What are the three major roles in Scrum?
• What are the responsibilities of a Product Owner?
• How does the Scrum Master help a Scrum team succeed?
• How is a Scrum Master different from a project manager?
• Who is responsible for deciding what the development team does?
• How team succeed when they are cross-functional?
Creating and managing Product Backlog
• Organize and prioritize all your team's work.
• How do you know the complete list of items that need to be done?
• What are the processes to use for prioritizing the work?
• How do you make sure that everything required gets done?
• How frequently do you change priorities?
• What is the best way to handle non-functional requirements?
• Product issues and bugs?
Estimating and Prioritizing Product Backlog Items
• Build a product backlog and learn how to manage it.
• What goes on the backlog?
• Who decides on the backlog priority?
• Who decides the order that the team does its tasks?
• Why is relative estimation important?
• What is velocity?
• How should ROI be calculated?
Day 2:
Sprint Planning and Execution
• Run an effective development cycle using Scrum.
• How do you decide what you commit to in a Sprint?
• Who does what, and who decides?
• What do you do if something comes up and the team can’t make its commitments?
• When is it ok to extend the length of a sprint?
• How should the entire Scrum team keep track of all the work items?
The “Definition of Done” And Why It’s Important
• Produce a potentially shippable product.
• Why is the concept of “done” important and how is it different from traditional software development?
• Who decides if something is done?
• What are the components of a good definition of done?
• How do you divide large stories that are too big into stories that can be completed in a single Sprint?
• What are the consequences of a weak definition of done?
Sprint Review and Retrospectives
• Assess your work and constantly improve.
• Why do we review our work at the end of each Sprint?
• Who determines when we’ve been successful?
• How do you make sure that the customer is being properly represented? What do you do to improve team processes?
• How do you make sure everyone contributes to the team?
• How do we address long term issues?
Tips to crack PSM-1 certification exam