Articles on Scrum and Agile Project Management
In an ideal Agile world, the Scrum team can complete all user stories tasks that it planned for the current sprint. The real world is however different. In this article, Scott Lively explains how to use the sprint data to modify the team behavior.
The Manifesto for Agile Software Development says that you should prefer “Individuals and interactions over processes and tools”. But how do you hire the right people for your Scrum software development projects. In her article “Hiring for Agility – Mindset Matters in an Agile Organisation”, Nadia Smith suggests that you should look for more for Agility than Agile.
After presenting some basic retrospective techniques in the first part of this article, Jesus Mendez provides in the second part some additional techniques that focuses on the facilitating part of the Scrum sprint retrospectives.
If user stories are the start of the conversations to define user requirements, Scrum teams can also use other tools to obtain a more precise definition of these requirements. In the article “When and How to Create Customer Journey Maps”, Kate Williamson presents the concept of customer journey map, the visualization of the process that a person goes through in order to accomplish a goal, and when and how to use them.
Product backlog refinement (or grooming) is an important activity in Scrum projects where user stories are prioritizes, right-sized and estimated. In his book “Agile Reflections”, Robert Galen provides some hints about how to verify that that product backlog grooming has been done successfully and that the right requirements information is available for the next sprint.
Sprint retrospectives are an important tool for Agile software development teams that want to implement continuous improvement and adjustment to their working context. In this article, Jesus Mendez provides some techniques that could help improving the outcome of your Sprint retrospectives.
The Minimum Viable Product (MVP) is defined in Wikipedia as “a product which has just enough features to gather validated learning about the product and its continued development.” In this article, Sergiy Andriyenko proposes fives rules to apply successfully a Minimum Viable Product strategy.
Scrum Expert Copyright © 2009-2023 Martinig & Associates