Learn the key elements of Agile and Scrum to be an effective Scrum team member.
Course topics include:
Understand the foundations of Agile and Scrum. What is the basis for Agile? What is the difference between Agile and traditional approaches like waterfall? What are the different types of Agile? 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?
Learn the basic rules of Scrum. What are the three major roles in Scrum? What are the responsibilities of a Product Owner? How does a the Scrum Master help a Scrum team succeed? How is a Scrum Master different from a project manager? Are programmers forced to do QA? How can a documentation professional fully participate on a Scrum team with developers? Who is responsible for deciding what the development team does? Does everyone on a Scrum team need to be cross-functional?
Translate requirements from the customer to the entire team. What is a “user story” and how is it different from traditional requirements? Are we forced to use the story format? What happens if we don’t have all the detail when we start to write a story? How much work should be associated with a single story? How do we group stories into feature sets that we can actually implement, document and test?
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? Emergencies?
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? What’s a t-shirt size? Why is relative estimation important? What is velocity? How should ROI be calculated? What should the team do if the Product Owner says that “we need to get everything done”?
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?
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?
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?
Build a great working team. What is different about working in an Agile team from a traditional environment? Do I need to modify my behavior? How do you form good working agreements? Who’s responsible for assigning tasks? What should happen if the team can’t agree? How can you work with someone who doesn’t believe that Agile is a good approach?
Deal with the realities of the current situation. How can you optimize your work with distributed teams? What happens if members of your team are constantly being pulled into other projects? How can you increase management support? Are there good ways to share effective techniques and lessons learned? What’s the best way of encouraging a learning organization?
What are you waiting for? Register Now