Implementing SCRUM…the basics Part 1 I began to write a response on a recent blog post regarding the impact that a slowing economy would have on the adoption?Agile project management methods. Then I realized?from the comments that there may be some people here that are not familiar with Agile/SCRUM. SCRUM is the most popular Agile “flavor”. I will be speaking specifically about it. If you are already familiar with SCRUM, this is just another SCRUM 101… if not, this is the beginning of SCRUM 101. If you are new to the concept, you should read this first. These four tenets represent a departure for most organizations from the way they have always solved technical problems. I will be describing SCRUM from the perspective of a small business that uses a single team to develop its internal LOB applications. There are minor variations to this content for commercial products. And for situations where you might be a cog on a larger machine or performing non-appdev tasks such as hardware engineering, manufacturing, etc. These scenarios will be covered in detail in future posts. You should understand that SCRUM has a few simple roles.
The ultimate responsibility for the behavior and functionality of the system is held by the “Product Owner”, which is someone from the business. They also set the schedule of when and what features will be delivered.
ScrumMasters are responsible for removing organizational, technical, and inter-personal barriers. That might be preventing the team’s ability to fulfill its commitments.
A “Team” is a group of people involved in delivery. This could include architects, designers, business analysts and DBA’s. QA pros can also be included. Marketing, training developers, technical writers, and so on. Although it is common to recommend that a team consist of 5-9 people, it is possible to have more or less. However, it is important to have a reason to do it.
A few ground rules
All meetings are Time-Boxed.
Development is organized into fixed-length, fully encapusulated development windows (typically 30 days) called a Sprint.
The Product Owner is responsible to collect, prioritize, prioritize, and communicate the system requirements (called User Stories).
Each Sprint is made up of four major meetings…
Sprint Planning Meeting #1 is used to review the Product Backlog by the team and discuss the Sprint’s desired outcome.
The team uses Sprint Planning Meeting #2 to plan. They have used the interim between the previous meeting and estimate the size of each item in the Product Backlog. This allows them to decide how many top items can be delivered within the next 30 days. This subset of Product Backlog is called Sprint Backlog.
The team uses the “Daily Standup” to report on their progress, what each person is working on, and what impediments they face.
The Sprint’s end Retrospective Meeting is an opportunity to? The Retrospective meeting is a chance for Product Owners, ScrumMasters, and Team to share their experiences and to assign actions to improve the Sprint.
The “Team” is self-organizing. It is responsible for understanding and delivering product as envisioned by the Product Owner.
Vertical Scrum – Flickr Attribution License: jurvetson Now you should have an idea of who is involved and what their responsibilities are. To fully understand SCRUM, you first need to read the following: