Forums

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Is Scrum only a framework?
Last Post 22 Jul 2013 12:45 AM by Ian Mitchell. 6 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Selçuk Alimdar
New Member
New Member
Posts:1
Selçuk Alimdar

--
17 Jul 2013 09:48 AM
    Hi,

    I got introduced to Scrum two days ago and began to read about it.
    A question: Scrum is a framework and so it is lightweight. However, isn't it also a methodology because defines events and artifacts in detail?
    thank you.

    Seljuk
    Charles Bradley
    Basic Member
    Basic Member
    Posts:411
    Charles Bradley

    --
    17 Jul 2013 12:49 PM
    Seljuk,

    A methodology is usually very prescriptive and attempts to cover every situation and every possible decision to be made. A framework literally "forces" the user to make some decisions on their own. If you've ever done any coding, think of a framework as an "abstract method", that *must* be implemented by any concrete subclasses. Methodologies are full of "concrete methods" where you'd have no flexibility of implementation -- unless you override it -- and then you're no longer using the methodology because you've modified it.

    More here:
    http://kenschwaber.wordpress.com/20...e-pattern/
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1615
    Ian Mitchell

    --
    18 Jul 2013 03:23 AM
    I suppose Scrum could be described as a methodological framework ;-)

    However, I think it's more helpful to consider it in terms of its purpose. For example, the Scrum Primer describes Scrum as a "Development Framework". I can see why, but I'm not entirely happy with that definition. I think of Scrum more as a "Delivery Framework".
    qun wan
    New Member
    New Member
    Posts:1
    qun wan

    --
    18 Jul 2013 04:17 AM
    very helpful. unfortunately, the link is not accessible. Is it valid?
    Romain Trocherie
    New Member
    New Member
    Posts:22
    Romain Trocherie

    --
    18 Jul 2013 11:52 PM
    Totally agree with Ian on this, describing Scrum as a delivery framework, getting more value produced, regardless how you defined it.
    There are so many abstraction illustrating examples to check out there, including Scrum for non-profits, non-IT, defending that idea. (Even experimenting some kind of diet programme using Scrum myself!)
    By the way, yes the link given by Charles is working fine.
    Ken Schwaber
    New Member
    New Member
    Posts:10
    Ken Schwaber

    --
    19 Jul 2013 03:55 AM
    Do not over think the subject. The description by Charles was very helpful. Scrum as a framework provides an environment within which complex work can be done. Thinking beyond that, in lean thinking, is called waste.

    Now, get on with the tough job of figuring how to do the work.

    Ken
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1615
    Ian Mitchell

    --
    22 Jul 2013 12:45 AM
    Issues such as this can become significant when agile methods are customized and/or configured, so I'm not sure our musings (in this case anyhow) are tantamount to over-thought or waste. It can be important to some people, and to some organizations at certain stages in an agile transformation.

    For example: there are teams who use Scrum in combination with XP. Kent Beck has described XP as "a lightweight methodology for small to medium-sized teams developing software in the face of vague or rapidly changing requirements". This seems reasonable, given that XP is rather more thetic than a framework, and prescribes techniques such as test-first, aggressive refactoring, and pair programming. Hence Scrum can be positioned as a framework within which a methodology like XP can be applied.

    That's a comparatively straightforward example. Once processes such as PRINCE2, DSDM, SAFe, and DAD are included in the mix (for whatever reason), the importance of defining and anchoring such distinctions can become critical.
    You are not authorized to post a reply.


    Feedback