Intro to Scrum Method

WHAT IS THE SCRUM METHOD? Scrum refers to a framework within which people can employ various techniques, methods and processes to address complex and adaptive problems, while productively delivering products of excellent value. Resulting Scrum Teams are highly flexible and adaptive and work with other teams within the same organization to develop, release, operate and sustain work and work products.

Who is Involved?

Scrum Team: consisting of a Product Owner, Development Team and Scrum Master.

• Self-organizing and self-sufficient teams have all necessary tools and support systems to accomplish their work.

• Team model is designed to increase flexibility, creativity and productivity.

• Teams deliver products repetitively and incrementally to allow for multiple opportunities for feedback.

A.) Product Owner (1 person):

• Responsible for retaining the value of the product using the work completed by the Development Team.

• Manages the Product Backlog by listing Product Backlog items and re-arranging the order of items to optimize the company’s goals and mission achievements.

• The Product Backlog content must be agreeable for all (in terms of steps in processes and overall language)

• The Product Backlog is responsible for documenting what the Scrum Team will work on next.

• Items in the Product Backlog are documented thoroughly for the Development Team’s use and future reference.

B.) The Development Team:

• Comprised of 3-9 members.

• Responsible for delivering a potentially releasable increment of “Done” product for each Sprint.

• Structured to be self-sufficient in organizing and managing work.

• Serves cross-functional purposes; every team member has a wide variety of skills to offer to achieve or reach a Sprint increment.

• No job titles are given for Development Team members.

• No sub-teams are defined (e.g. Testing, Architecture, Operations, Business Analysis) in order to force everyone to work together on a regular basis.

• The Development Team is accountable as a whole for the work completed.

C.) Scrum Master:

• Helps everyone understand Scrum theory, practices, rules and values.

• Facilitates proper and effective communication between Scrum Team and outsiders to maximize value.

SCRUM Events:

• Events are prescribed and time-boxed.

• Once a Sprint begins, its duration is fixed.

• Remaining events end whenever the purpose of the event has been achieved.

• Each event is an opportunity to inspect and adapt something.

1. The Sprint:

• Occurs once a month or less to achieve a “Done” status (a useable, releasable product increment)

• A new Sprint starts immediately after the previous Sprint has been achieved.

• Sprint steps: Sprint Planning, Daily Scrums, Development Work, Sprint Review, Sprint Retrospective

• Consider a Sprint to be like a one month project to accomplish something: reach the goal of what is to be built, a design and flexible plan to guide the building process, the work and resultant product increment.

• Enables predictability through routine inspections and adaptation of progress towards a Sprint Goal once per month.

• Reduces risks in overall costs to one month (trial period).

2. Sprint Planning:

• Exists to plan the work performed in the Sprint.

• Everyone from the Scrum Team pitches in their opinion.

• Occurs for a maximum of 8 hours for one-month Sprint.

• Guided by the Scrum Master.

• Discuss what is the next step in the Sprint?

• Discuss work involved in Sprint increment to reach “Done” status/Sprint Goal.

Sprint Goal: an objective set for the Sprint met through utilizing the Product Backlog.

3. Daily Scrum:

• Guided by the Scrum Master.

• Essentially a 15-minute meeting for Development Team held every day.

• Development Team plans workflow for the next 24 hours.

• An opportunity to reflect on work completed since last Daily Scrum and plan for upcoming Sprint work.

• A meeting that is held at the same time and place every day.

• A key inspect and adapt meeting to improve communications, identify obstacles to development and remove them, highlight quick decision-making and improve everyone’s knowledge.

4. Sprint Review:

• Guided by the Scrum Master.

• Held at the end of the Sprint to inspect the Increment and revise the Product Backlog.

• Scrum Team and Stakeholders discuss achievements in the Sprint.

• Attendees collaborate to identify the next steps to optimize product value.

• Facilitates feedback and encourages collaboration.

• Essentially, a four-hour meeting that occurs once per month/Sprint.

Discussion Topics during a Sprint Review:

• Product Owner explains what Product Backlog items have been delivered and what remains to be delivered.

• Development Team discusses Sprint successes, problems encountered and solutions.

• Development Team showcases work completed and answers questions about the Increment.

• Product Owner discusses Product Backlog- target dates, delivery dates revised based on progress to date.

• Entire Group discusses next steps.

• Revision of how the marketplace or use of product might have changed.

• Review timeline, budget, potential capabilities and marketplace for next Sprint.

• Revision of Product Backlog to meet new opportunities.

5. Sprint Retrospective:

• Scrum Team re-evaluates and creates a plan for improvements to be implemented during the next Sprint.

• Occurs after the Sprint Review.

• Essentially a three-hour meeting, once a month.

• Guided by the Scrum Master.

• Discuss how the last Sprint went regarding people, relationships, process and tools.

• Identify and order major items and acknowledge successes and failures to be improved upon.

• Plan for improvements in workflow (development processes and practices).