Just as we do in life, the same we should try in Scrum:
The truth is no one can forecast what jobs will exist in 10 years. So the solution for your career path is to try new things, keep learning by getting new skills, try new approaches and evaluating the results. Same apply to Scrum, a team comes up a with a plan, through the sprint the plan can change and on the retrospective event we evaluate the results and if we failed we try a new approach.
Agile means to be able to move quickly and easily, by accepting that we can’t know all the information beforehand and things will happen along the way where should make us adjust and adapt during the process. In Scrum team works together from beginning to end, rather than separate and in sequence. Doing this, we profit from each other’s knowledge and learn together.
Scrum Team
The team as a whole is accountable for creating a valuable, useful Increment every Sprint and every role has accountabilities.
Product Owner (Owns the product vision): Developing and explicitly communicating the Product Goal, Creating and clearly communicating Product Backlog items, Ordering Product Backlog items and ensuring that the Product Backlog is transparent, visible and understood
Developer: Creating a plan for the Sprint, the Sprint Backlog, Establish quality by adhering to a Definition of Done, Adapt their plan each day toward the Sprint Goal and holding each other accountable as professionals
Scrum Master
– serves the team by: Coaching the team members in self-management and cross-functionality, helping to focus on creating high-value Increments that meet the Definition of Done, remove of impediments to the team’s progress and ensure that all scrum events take place and are positive, productive and timeboxed.
– serves the product owner by: helping to find techniques for effective Product Goal definition and Product Backlog management, helping the Scrum Team understand the need for clear and concise Product Backlog items, establish empirical product planning for a complex environment and facilitate stakeholder collaboration as requested or needed.
Scrum team members: should work together as a tight-knit collaborative team supporting each other & fostering trust among members, are focused on creating value, have the diverse set of skills and experience needed to accomplish their goals, are self-managing, are non-hierarchical by acting as one team, the entire team is accountable fir the success in creating a valuable, useful Increment every Spring.
| Event | Inspection | Adaptation | Participants | Timebox |
|---|---|---|---|---|
| Sprint Planning | Product Backlog, Product Goal, Definition of Done | Sprint Backlog, Sprint Goal | Scrum Team | 8 hours for a 1 month Sprint |
| Daily Scrum | Progress toward Sprint Goal | Sprint Backlog | Developers | 15 minutes |
| Sprint Review | Increment, Sprint, Product Backlog, Progress toward Product Goal | Product Backlog | Scrum Team, Stakeholders | 4 hours for a 1 month Sprint |
| Sprint Retrospective | Sprint, Definition of Done | Actionable improvements, Definition of Done | Scrum Team | 3 hours for a 1 month Sprint |
Definition Of Done
Describes the quality standards for the Increment to be considered “done” and in a state that it can be effectively inspected. It provides to the Scrum Team and organization a common understanding of the completeness of the Increment. Without this crystal clarity, it’s not possible for stakeholders to provide informed and reliable feedback.
For a software product, the DoD may include items such as:
- Integrated into a clean build
- Promoted to a higher level environment
- Automated regression tests passed
- Feature level functional tests passed
- Non-Functional requirements met
- Meets compliance requirements
- Functionality documented in necessary user documentation.
Sources:
Professional Scrum Competency: Understanding and Applying the Scrum Framework | Scrum.org
Leave a Reply