Penulis: vpadmin

The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. This is at most a three-hour meeting for one-month Sprints. The retrospective session is basically an “improvement” meeting held to find ways and means to identify potential pitfalls, past mistakes, and seek out new ways to avoid those mistakes, which are attended by all — the product owner, scrum master, development team members, and optionally with the stakeholders.

Scrum itself is a simple framework for effective team collaboration on complex products. The Scrum Guide to explain scrum clearly and concisely. this guide contains a definition of scrum. This definition consists of Scrum’s roles, events, artifacts, and the rules that tie them together. Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage. The rules of Scrum bind together the roles, events, and artifacts, governing the relationships and interaction

A Scrum master is a member of a Scrum team. Their task is to create a productive work environment and guide others to understand the values, principles, and practices of Scrum. scrum directors tend to be people-oriented, have a high EQ, and find joy in helping their team members grow.

A Product Owner who owns the product on behalf of the company is a part of a Scrum team. However, a product owner has no authority over other members of the team, same as the Scrum Master. A Product Owner is responsible for looking after a product for an extended period of time and is accountable for achieving product success. As the product owner, you should directly interact with the customers and users, the development team, and other key stakeholders, as the picture below shows.

A Sprint Review is more than just a demo; it is a review of the completed Sprint, the Product Backlog, and the Marketplace. Admittedly, demos are an important part of the Sprint Review. The purpose of the Sprint Review meeting is for the team to show the customers and stakeholders the work they have accomplished over the sprint and compare it to the commitment given at the beginning of the sprint.

A Scrum development team has the autonomy to choose how best to accomplish their work, rather than being directed by others outside the team. Unlike traditional management principles, the self-organizing empowered teams are not directed and controlled from the top; rather they evolve from team members participating actively & collectively in all the Scrum practices and events.

Colocation is useful for meetings that require close listening, such as design discussions. It is also handy when new employees are training and need some amount of hand-holding or encouragement. Whiteboard is highly effective for colocated team but can be managed with online tools as well.

Release early, release often is a software development philosophy that emphasizes the importance of early and frequent releases in creating a tight feedback loop between developers and testers or users, contrary to a feature-based release strategy.

Not all items in the product backlog will be of the same size and level of detail (i.e. features/ eprics/ user stories and tasks) at the same time. PBIs that we plan to work on soon should be at the top of the backlog, smaller in size, and very detailed so that they can be worked on in the near-term sprint. PBIs that we won’t be working on for some time should be at the bottom of the backlog, larger, and less detailed.