-
What is Scrum?
Scrum is a light-weight framework for delivering valuable product to customers by empowering cross-functional, self-organizing Teams. It is uniquely balanced to enable the business to make periodic adjustments rooted in observation, feedback and empirical data. Scrum provides a framework for organizations to transform their work environments, restore a focus on the customer and reenergize their employees. The wide variation of skills, roles and experience needed for a cross-functional team to be effective gives rise to the opportunity for everyone in the organization to contribute.
Success with the Scrum framework emerges from the interactions of thoughtful, dedicated individuals when their actions and words are congruent with the values and principles of Scrum. The combination of these values and principles uniquely identify Scrum and make it distinct from other frameworks.
The values which Scrum is based upon are:
- Respect – all participants are treated as valued, unique individuals with an important contribution to make. Each member is expected to extend this courtesy to all other individuals they encounter.
- Commitment – participants are expected to fully dedicate themselves to the Team, choosing to put the objectives of the Team before their own. At times, Team members may choose to make reasonable sacrifices for the greater good of the Team.
- Trust – participants can rely on their co-workers to perform their duties to the highest professional standards. Participants will act with positive intent and assume others are acting with positive intent as well.
- Visibility – nothing in Scrum is ever hidden from view. Every action, decision, artifact, outcome and conversation is freely made available to others for consideration and discussion.
- Courage – individuals and Teams will display strength in the face of adversity. Team members will fearlessly address issues as they arise, confident a solution can be found within their skills and abilities.
From these values, Scrum relies on these essential principles:
- Prioritization – periodic ordering of conflicting desires and needs is vital for success. Conversations about ranking will involve those who are affected by these decisions and take in consideration their desires and needs.
- Accountability – all are answerable for their decisions, words, actions and non-actions. Each person is empowered to hold one another responsible for meeting their commitments, producing quality work, following the Scrum framework and observing the Spirit of Scrum.
- Inspect-and-adapt – at regular intervals, the Team will check their progress and make adjustments. Scrum Teams use empirical data to drive their decisions.
- Rhythm – Teams will strive to develop a regular cadence to their actions. Rhythm reduces variability and increases the predictability of the Team.
- Feedback – participants accept and receive new information about their circumstances and environment. Feedback cycles are compressed as short as possible to amplify the effect of new knowledge and make corrections for the advantage of the business and the participants.
- Collaboration – beyond mere cooperation, we strive to build on top of the talents and ideas of others. Collaboration signals the shift from simply better, to astonishing business results and outcomes.
- Self-organization – Team members are the ones best suited to mobilize their efforts around their goals and to remain on target. Clear goals, boundaries and autonomy are necessary for this to occur.
- Focus – individuals will be given time and space to concentrate. Scrum strives to eliminate unnecessary interruptions so people can get things done.
Frequent Topics
Agile Agile SD Certified ScrumMaster Coaching Collaboration Communication Conferences Daily Scrum Design Excellence Design for Six Sigma Extreme Programming Games Innovation Games Lean Legacy Code Links of the Week Measures Movies Pair Programming Personal Planning PMI Practices Presentations Product Owner Quality Refactoring Retrospectives Rugby Scrum ScrumMaster SIMSOC Spain Team Test-Driven Development Testing Tools Training Transitions Travel Voice of the Customer
Calendar
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « May | ||||||
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | ||||
Recent Comments
- Kenneth van Rumste on Scrum Roles Defined
- Carlton on Scrum Roles Defined
- Kenneth van Rumste on Scrum Roles Defined
User Groups
Archives
- May 2011 (1)
- February 2011 (1)
- January 2011 (5)
- November 2010 (3)
- October 2010 (6)
- September 2010 (5)
- August 2010 (4)
- July 2010 (6)
- June 2010 (2)
- May 2010 (2)
- April 2010 (5)
- March 2010 (3)
- February 2010 (5)
- January 2010 (7)
- December 2009 (8)
- November 2009 (2)
- October 2009 (6)
- September 2009 (9)
- August 2009 (7)
- July 2009 (4)
- June 2009 (3)
- May 2009 (3)
- April 2009 (5)
- March 2009 (6)
- February 2009 (6)
- January 2009 (7)
- December 2008 (10)
- November 2008 (11)
- October 2008 (10)
- September 2008 (4)
- August 2008 (5)
- July 2008 (5)
- June 2008 (8)
- May 2008 (5)
- April 2008 (3)
