As I explained in a previous post, I have been tasked with learning what I can about Agile project management for a small project I have coming up. The first thing I did was ask a senior Business Systems Analyst about how her foray into the Agile process was going. She in turn sent me the link to a couple of videos on You Tube as an introduction to the Scrum process.
The first video is only eight minutes long, thus it’s title “Introduction to Scrum in just 8 Minutes”. The two presenters are Arif Gangji, the founder of Neon Rain Interactive and the founder of Agile for All, Bob Hartman.
The second video is an hour long and goes into considerably more depth on the topic, but I will save that for a later post.
As I started this video it was immediately apparent why the BI group had chosen it. Although it is short, it does do a reasonably good job of covering the basics of the method in a concise and clear manner.
The video sticks to the basics of the Scrum Framework. Here are a few of the main points covered in the video:
- The process starts with the product owner creating a prioritized, from most to least important, product backlog. A backlog is comprised of stories – who, what, why – that are the dreams and wishes of the customer in story form.
- The team uses the product backlog to determine how much work can be done in a sprint. The team should never commit to more work than they can deliver in a sprint with a sprint lasting between a week and a month.
- The speed at which a team can deliver work is their velocity.
- A team takes on the work in a sprint that delivers the most value to the customer so that the customer delivers the most value as early as possible.
- Each day there is a daily Standup Meeting or “Scrum” Meeting that lasts for 15 minutes or less. During this meeting the following is accomplished:
- Talk about what has been completed.
- Talk about what they intend to complete
- Talk about any impediments that may be preventing work from getting done.
- The team uses this time to determine how to best share information to best help each other to meet their sprint commitment.
- This exposes risk and knowledge to be shared to help the team be more effective
- Scrum requires there to be a Scrum Master who helps to ensure success by helping to remove impediments, aiding in making decisions and to support the team in any way possible. This role is vital for team to be successful.
This video was a good start for me, and I hope that you will find it helpful as well. Do you know of any good Agile related videos or books that helped you to get up to speed on Agile?