Lets start true content with a set of posts about Scrum. Scrum is one of the most popular agile software development frameworks. What is an agile framework and its differences between other classical development processes will be subject of a different post sequence. Lets go!
At the beginning of this month I achieved the Professional Scrum Master I certification, to prepare it, I read the Scrum Guide, maintained by Ken Schwaber and Jeff Sutherland, creators of Scrum, and made my own summaries and schemes. In this post set, I will share with you my resumes based on its content. I hope they can help you if you are preparing yourself for the certification or to bring you closer to it. The topics to be discussed will be:
- Overview
- Common standards, the definition of “Done”
- The Scrum Team
- Scrum Events
- Scrum Artifacts
Scrum Overview
Scrum is a framework within which complex products in complex environments are development. It makes clear the relative efficacy of your product management and development practices so you can improve them.
The Scrum framework consists of one or more Scrum Teams, each Scrum Team is formed by a set of Roles, Events and Artifacts, binded together by rules.
Scrum is founded on empiricism, the knowledge comes from experience and decisions are made based on what is known.
Scrum employs an iterative, incremental approach. Each increment, called Sprint, has a maximal duration of a month, which optimizes predictability and controls risks.
The framework is bases on three pilars: transparency, inspection and adaptation.
Transparency
Significant aspects of the process must be visible to those responsible of the outcome. It requires common standards, like a common language and a common definition of “Done”.
Inspection
It is essential to inspect the artifacts frequently and progress toward a goal, this will help us to detect deviations. The inspection should be not so frequent that it gets in the way of the job and it is recommended to be done by expert people.
Adaptation
If there are deviations we must adjust the process as soon as possible to avoid further deviations. Scrum prescribes four opportunities for inspection and adaptation, called Sprint Planning Meeting, Daily Scrum, Sprint Review and Sprint Retrospective, which are also known as the Scrum Events.
The next entry will be a short clarification of transparency and the definition of done, see you there!
Source: Scrum Guide and my summaries about it.