Scrum Methodology
Learn the Scrum Methodology
The Scrum methodology of agile software development marks a dramatic departure from waterfall management. In fact, Scrum and other agile processes were inspired by its shortcomings. The Scrum methodology emphasizes communication and collaboration, functioning software, and the flexibility to adapt to emerging business realities — all attributes that suffer in the rigidly ordered waterfall paradigm.
24th
APR
Scrum is a Framework, Agility is a Concept
Posted by admin under Agile and Scrum, Scrum Discussion
If you’re new to Scrum and agile, or like me a long time Scrummer, there are always insights to gain from talking with experienced practitioners. I had a recent opportunity to talk with Michael James (link to his blog) of Danube Technologies. He clarified something extremely basic for me, but it cemented the relationship between Scrum and agile for me so I thought I’d share it with you all.
Our conversation started with me stating that Scrum was a process that fell under the general umbrella of processes called “agile”. He quickly stopped me right there and pointed out two subtle, but important corrections. First, Michael noted that agile is not a process (or collection of processes) at all; rather, it’s a set of principles summarized by the Agile Manifesto. Scrum, XP, and other methods embody these principles and so are described as “agile”. There is no real parent-child relationship though.
Second, Michael made clear that Scrum was not a process in the technical sense of the word. A process is a prescriptive and linear series of steps taken to repeatably generate the same output. Hmm, that doesn’t sound like Scrum at all! Since we’re constantly inspecting our work and adapting the backlog, there is no repeatability we’re striving for. Instead, Michael suggested we use the term “framework” or “method” to describe Scrum. These terms suggest that we have a skeletal framework within which things happen, but that the innovation and intelligence of the team fills in the
gaps.
These two subtle corrections really changed the way I think about Scrum. Thanks, Michael!
Comments Feed
Leave a Reply
Newsletter Sign Up:
Recent Posts
- Results of an Agile Assessment
- Introduction to Scrum Video
- Complexity and cost of change
- Technical Debt – The High Cost of Change
- Strategic Vision and Scrum
- Agile and PPM – Q&A
- Estimating Earned Business Value on Agile Projects
- Building the Product Backlog
- Intro to Agile
- The Agile Manifesto and Twelve Principles
- The Daily Scrum; It’s a Good Habit to Make
- Obstacles to Enterprise Agility
- What is Scrum?
- Can CSMs and PMPs Get Along?
- Free Scrum Webinars
Categories
- Agile and Scrum (27)
- Agile Assessment (1)
- Agile Manifesto (5)
- Agile Principles (7)
- Scrum Basics (43)
- Scrum Discussion (26)
- Scrum Transitions (16)
- Uncategorized (7)
Archives
- January 2012
- December 2011
- November 2011
- October 2011
- November 2010
- September 2010
- June 2010
- April 2010
- March 2010
- February 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
Blogroll
- Agile ALM
- Agile Methodology
- Agile Programming
- Agile Project Management
- Eric Brown
- Free Project Management Software
- IT Today
- PM Student
Danube on Twitter
- Overheard from a Twitter post by @ScottOstby
- Overheard from a Twitter post by @billportelli
- Overheard from a Twitter post by @iGuick
- Overheard from a Twitter post by @vigneshwaranr
- Overheard from a Twitter post by @ScottOstby
- Overheard from a Twitter post by @CJ_381
- Overheard from a Twitter post by @ScottOstby
- Overheard from a Twitter post by @CJ_381
- Overheard from a Twitter post by @ScottOstby
- Overheard from a Twitter post by @dwinter
