What I learned about Scrum
on
What I learned about Scrum
Development methodologies weren't taught at Cornell when I took Computer Science 1982-1986. I first remember hearing about them in the early 1990's. At CivicActions, we've talked about "agile" and "scrum" for some time. But it really took the last couple of projects for me to embrace these methods.
I had hoped to present my "Scrum" methods at DrupalCon Paris, however my title was poorly choosen. So I was pleased when another "Scrum" presentation was selected over mine... it meant that I had less to prepare and I could sit back and learn something. I learned that I have my own technique, somewhere between scrum and "Extreme Programming." (Scrum is the management process and "Extreme" is the engineering practice.)
This video helped me understand better the keys of scrum:
- Time boxed
- Each sprint results in "done", which includes testing and documentation.
- Feedback loop for client requirements
- Cross functional teams
- Small teams are better, 3-4 people are good, 8-9 at most
- The classic ham and eggs joke, only pigs are committed and get to speak in Scrum.
I also like this slide from the DrupalCon presentation, which tells me how to write a "User Story" by filling in the blanks "As [role], I want to have [functionality], because [I can achieve goal]".
I took Ken Schwaber's SCRUM certification class a few years ago where I got certified as a "SCRUM Master". I love the chicken and pig analogy. Working in a true SCRUM process requires a tremendous amount of commitment from both the team and the client.








Though I am a agile team member, I liked the video very much and instatly shared among the team members but we thought that if more information can be provided on SBL (Spring BackLog) and applications can be used for that (Ex: Excel) would be more useful.