Scrum

Understand Scrum?

If you carefully scrutinize scrum, you will find again and again the three pillars of empirical process control: transparency, inspection, and adaptation.?

What are the 5 values of Scrum??

A team's success with scrum depends on five values: commitment, courage, focus, openness, and respect.?

The 3 principles behind scrum tools - Transparency, Iteration, Empowerment.?

The Six Principles of Scrum?

• Control over the empirical process. In Scrum, the empirical process is based on observation of hard evidence and experimentation rather than theory. ...?
• Self-organization. ...?
• Collaboration. ...?
• Value-based prioritization. ...?
• Time-boxing. ...?
• Iterative development.?

What are the four Scrum ceremonies??

• Sprint planning.?
• Daily stand-up.?
• Sprint review.?
• Sprint retrospective.?

A sprint planning meeting is when the team (including the Scrum Master, Scrum Product Manager, and Scrum Team) meets to determine which backlog items will be handled in the next sprint. The sprint planning Scrum ceremony is a collaborative process that allows team members to have a say in when work happens.?

How long would a standup meeting take??

Most experts agree that stand-up meetings should last no longer than 15 minutes, and that each team member should plan to speak for up to one minute, but no longer. Depending on the size of your team, your stand-up meeting may be shorter or longer.?

?The Sprint Review takes place at the end of the Sprint and is designed to gather actionable feedback on what the Team has completed. Participants in the sprint review typically include the product owner, the Scrum team, the ScrumMaster, management, customers and developers from other projects. During the sprint review, the project is assessed against the sprint goal determined during the sprint planning meeting.?

?The sprint retrospective is a recurring meeting dedicated to discussing what went well and what can be improved in a sprint. It also gives a chance to recover from a sprint and prepare for the next one. With a sprint retrospective, you can make each sprint more streamlined and successful than the last.?

?As described in the Scrum Guide, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done.?

?The Product Owner?

The Product Owner is responsible for creating User Stories. Generally, the Product Owner creates those, but sometime they are developed by the Scrum team in consultation with the Product Owner.?

?These are the five golden rules in Scrum: Openness: Scrum sees collaboration as the most effective way to create the best possible product. So teamwork and transparency are essential. Rather than anxiously downplaying problems, Scrum team members are open about their progress and any roadblocks they encounter.?

?Top Skills of a Successful Scrum Master?

• Share Experiences and Encourages Collaboration.?
• Introducing Engineering Practices.?
• Communication and Good Listening Power.?
• Acting as a Coach for Team Development.?
• Flexibility and Persistence.?
• Partnership with the Product Owner.?
• Wanted and Dispensable.?
• Optimism and Servant Leadership.?
• Organization and Empathy?

?In Scrum, a sprint is a time-boxed event of one to four weeks in which your Scrum team focuses only on a sprint goal. The goal is typically a product increment or iteration — often an updated, improved version of your product or software.?

?Who prepares backlog??

In most cases, the product owner holds responsibility for organizing and maintaining the product backlog.?

?Who decides the sprint length??

Because the team is self-organize, the final decision is up to the team and no one should force fixed sprint duration. Having in mind that Scrum is an adaptive approach to do things, the team can always decide to change length of sprint while they do retrospective meeting.?

?Who prioritizes the backlog??

The product owner prioritizes the backlog at the start of the project, but doesn't adjust it as feedback rolls in from developers and stakeholders. The team limits items on the backlog to those that are customer-facing.?

?What is the 80/20 rule in Scrum??

The Pareto Principle, commonly referred to as the 80/20 rule, states that 80% of the effect comes from 20% of causes. Or, in terms of work and time management, 20% of your efforts will account for 80% of your results.?

?What is MMR in Scrum??

Minimum Marketable Release (MMR).?

An MMR is the release of a product that has the smallest possible feature set that addresses the current new needs of your customers.?

?What is the most important role in Scrum??

One of the most important things for the success of scrum is the role of the Product Owner, who serves as an interface between the team and other involved parties (stakeholders).?

?What are the 8 stances of a Scrum Master??

As a Scrum Master, I'll try to be a servant-leader, facilitator, coach, conflict navigator, manager, mentor, teacher, impediment remover, and change agent.?

?What is the main goal of a Scrum Master??

Often a developer who is responsible for keeping the dev team on track. The scrum master's main objective is to make sure the team works according to the agile values. That they have the resources, time, and disruption-free environment to succeed.?

?Who can cancel a sprint??

A Sprint could be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the Sprint. This opens it up to the Scrum Team to decide what comes next should a Sprint Goal become obsolete, and the PO decide to cancel a Sprint.?

?Who writes tests in a scrum team??

The development team rounds out the Scrum team and is responsible for developing and testing the product based on the criteria from the user stories.?

?A Scrum team should consist of less than 9 people. For large enterprise projects, the ideal Scrum team size is 7 people (product owner, scrum master, and 5 developers). Smaller projects typically consist of four team members (product owner, scrum master, and 2 developers).?

?User Stories Per Sprint?

It also subtly takes the focus off of swarming and puts attention toward a developer per story. 5 to 15 user stories per sprint is about right. Four stories in a sprint may be okay on the low end from time to time.?

?A good Scrum Team is usually able to plan a two-week Sprint in less than three hours. Participants: The whole Scrum Team participates in this event: Product Owner (PO), Developers, and Scrum Master (SM). The event is usually facilitated by the Scrum Master.?

?Daily standup meeting?

In the Scrum process, this meeting might also be called the daily Scrum meeting. It's a chance for the team to connect about the work that was completed the previous day and what each person or team plans to complete over the course of the next 24 hours.?

?What are the types of backlog??

• Product backlog: Features you want to implement but have not yet prioritized for release.?
• Release backlog: Features that need to be implemented for a particular release.?
• Sprint backlog: User stories that need to be completed during a specific period of time.?

?Your backlog is usually a list of issues describing what your team is going to do on a project. Jira is a convenient place for creating, storing, and managing several kinds of issues: issues that you're currently working on (you can also see them on the board and in the current sprint if you're using a Scrum project).?

?During Backlog Refinement (Grooming) the Scrum Master facilitates as the Product Owner and Scrum Team review the user stories at the top of the Product Backlog in order to prepare for the upcoming sprint.?

?The three roles of a scrum master are to facilitate, lead, and communicate. A scrum master must facilitate scrum meetings, also called daily standups.?

?What is MVP and MMP??

MVP reduces the time to market and allows a quicker release of the product. MVP is a great risk reduction tool: it allows products or features to fail fast without investing in their development. A Minimum Marketable Product (MMP) is a more developed version of the MVP and it is ready to be sold to customers.?

?WHO removes obstacles in scrum??

According to the Scrum Guide one of the Scrum Master services to the Development Team is removing impediments to the Development Team's progress. As a servant leader, the Scrum Master guides the Development Team towards self-organization and cross-functionality.?

?An epic is a large user story which is too big to fit into a sprint. This high-level story is usually split into smaller ones, each of which can be completed within a sprint. In that sense, an epic is a collection of user stories with a unified goal.?

?What is a scrum roadmap? A scrum product roadmap visualizes upcoming sprints in your product development workflow. When juggling multiple initiatives, it can be difficult to keep track of which projects will be tackled during each sprint cycle.?

?A product roadmap is focused on the overall product development strategy. Whereas a backlog focuses on the task specifics and details. A roadmap is mainly for the executive team and other stakeholders. Whereas a product backlog is primarily for the development teams.?

?You do not "close a project" in Scrum. You retire a product. You can organize the work in groups of related Product Backlog Items to define a "project" and as such each Product Backlog would be used across many projects. Projects are not part of the Scrum framework?