what is Scrum-Introduction to Scrum

Introduction to Scrum 

Continuous Process Improvement

“Release Plan” for this Session

Intro to Agile

Intro to Agile-Myths and Facts

Agile Principles & Values

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value

Agile Principles..

Principle #1 Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Principle #2 Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

Principle #3 Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

Principle #4 Business people and developers must work together daily throughout the project.

Principle #5 Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

Principle #6 The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

Principle #7 Working software is the primary measure of progress.

Principle #8 Agile processes promote sustainable development. The sponsors,

developers, and users should be able to maintain a constant pace indefinitely. 

Principle #9 Continuous attention to technical excellence and good design enhances agility.

Principle #10 Simplicity--the art of maximizing the amount of work not done--is essential.

Principle #11 The best architectures, requirements, and designs emerge from self organizing teams.

Principle #12 At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Let’s Set the Stage….

1. Time Boxing : An act of putting Strict Time boundaries around an Action or Activity.
2. Sprint : In Scrum, Work is always done in regular repeatable work cycle known as Sprint.  Sprint is an iteration with fixed time box.

3. Velocity: is a measure of the amount of work a Team can tackle during a single Sprint and is the key metric in Scrum. Velocity is calculated at the end of the Sprint by totalling the Points of all fully completed User Stories. 

4. Scrum : Scrum is an Agile way of doing Projects usually Software Development but not limited to. It provides a lightweight process framework that embraces iterative and incremental practices, helping organizations deliver working projects more frequently.

Scrum Roles

Product Owner.

1. Responsible for maximizing the value of the product and the work of the Development Team. 

2. Creates and maintains the Product Backlog.

3. Prioritizes and sequences the Backlog according to business value or ROI.

4. Assists with the elaboration of Epics, Themes and Features into user stories that are granular enough to be achieved in a single sprint.

5. Represents the customer, interfaces and engages the customer.

6. Terminates a Sprint if it is determined that a drastic change in direction is required.

7. Inspects the product progress at the end of every Sprint and has complete authority to accept or reject work done.

Scrum Master.

1. Responsible for ensuring Scrum is understood and enacted

2. Responsible for enacting Scrum values and practices.

3. The Scrum Master serves the team (helping them remove any and all impediments 

that surface), protects the team (from any outside disruption or interference), and teaches and guides the team’s use of Scrum.

4. Gathers support from everyone to make sure that the change is accepted.

5. Train, mentor and make the team speak the same language.

6. Protects the team from the outside interference.

7. Unblocks impediments so that the team can achieve the sprint goal.

Scrum Team (Team).

1. Collectively responsible for converting product backlog into product increment.

2. Self-organizing. Self-Organize to collectively deliver product increment every sprint

3. A cross-functional team. Understand and commit to sprint goal. Create sprint backlog. Create Just enough design for the sprint goal

4. Understand the User stories, estimate them , break the stories in task etc..

5. Understand the product vision & help each other in achieving committed  Sprint goal.

6. Demonstrate the work done and understand both verbal and non-verbal feedback.

7. Actively participate in Retrospective and identify process improvements to get better at delivering value

Scrum Team- The Ultimate Responsibility

Scrum-Values.

A Good Product Backlog is.

Sprint Backlog.

1. The Product Backlog items selected for this Sprint + the plan for Delivering them is Sprint Backlog

2. During the sprint planning meeting, the team selects some number of product backlog items, usually in the form of user stories, and identifies the tasks necessary to complete each user story is Sprint Backlog.

Product Increment.

1. The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.

2. At the end of a Sprint, the new Increment must be “Done,” which means it must be in useable condition and meet the Scrum Team's definition of “Done.”

Backlog Grooming ( Product Backlog Refinement )

It is the act of adding detail, estimates, and order to PBI.

It’s a part-time activity during the sprint and how and when is decided by the Scrum Team.On going process of collaboration between PO and the Development Team

Sprint Planning Meeting

1. Takes place before the start of every Sprint

2. Attended by Team, Product Owner, Scrum Master, Stakeholders

3. The product owner presents the ordered PBIs to the Development Team.

4. The Development team Pulls and discuss PBIs, ask clarifying questions and understand the acceptance criteria. Select the PBI for Sprint. 

5. Continue step 4 until Sprint backlog is full.

6. The Scrum team crafts the sprint goal.

7. Team understands the details of what the Product Owner has prioritized on
the Product Backlog

8. Team decides how much productive time it has available during the Sprint.

9. Team decides how many Product Backlog items it can commit to complete during
the Sprint.

Sprint Planning.

Daily Stand up Meeting.

Daily Stand up Meeting.

DSM: The Agreement & The Protocol

Scrum Values and DSM.

Scrum Framework

Sprint Review Meeting.

1. At the end of the Sprint, the Product Owner, Team, Scrum Master, and Stakeholders come together and see a demo of what the team has produced.

2. Attended by Team, Product Owner, Scrum Master, Stakeholders.

3. The Development Team Demonstrates the work done to the PO and Other Stakeholders.

4. PO verifies things and accepts or rejects the work done.

5. Development team discusses how the last Sprint went.

6. PO identifies the work done and what has not been done.

7. The Purpose is to Inspect the product increment and adapt the product backlog.

8. PO gives feedback to the team and updates the Product Backlog.

Sprint Review Meeting.

Sprint Retrospective Meeting.

1. Inspect how last sprint went with regards to people, relationship, process, and tools

2. Attended by Team, Product Owner, Scrum Master.

3. This is the mechanism for continuous improvement where critical problems are identified and addressed.

4. The Team, Product Owner, and Scrum Master meet at the end of each Sprint to review their way of working, and look for ways to improve their effectiveness.

5. Primary Objective of this Meeting is to identify 

3 specific items.

1. Things the team needs to keep doing : ---- Best practices

2. Things the team needs to begin doing: ---- Process Improvements

3. Things the team needs to stop doing : ---- Process Problems and Bottlenecks

Sprint Burn Down Chart.

Release Burn Down Chart.

Thank You