Worrying interpretations of Scrum

Misconceptions about Scrum. Why don’t you read and understand the Scrum guide?

Ullizee

At an Agile event I attended recently the speaker surveyed the audience about the 9 elements that form Scrum. My suspicion was immediately raised with mentioning of “9”. It only got worse when the speaker came up with:

Definition of Scrum (9)

It got me wondering how many misconceptions of Scrum can be expressed in no more than two minutes:

Definition of Scrum (9?)

I was hoping that by now (2016), and certainly given the availability of the Scrum Guide (since 2010), the basic understanding of Scrum was better.

What worries me the most however is not the formality of the wrong and missing elements, but how this reflects an ineffective use of the Scrum framework, a limitation to how Scrum supports teams in creating great software products:

  • Accountability over the self-organized creation of Increments belongs to the Development Team as a whole. Synergy is key, not individualism.
  • Transparency is optimized when Product Backlog holds all types of work and requirements for…

View original post 227 more words

The Future Present of Scrum (Are we Done yet?)

Ullizee

Scrum turns 21. Thank YOU!

Scrum was for the first time publicly presented and described in the paper “Scrum Development Process” in 1995. Scrum is turning 21 years old.

It starts and ends with people.

Scrum can only last and prosper -across the globe, across industries- because thousands and thousands of people, organized in teams, departments, organizations, employ Scrum to deal with complexity, to tackle difficult challenges, to create valuable product. Day in, day out. (Depending on the source, 70-90% of all Agile teams worldwide say they use Scrum.)

Regardless of region, organization, culture, or background, every individual has the intrinsic capability to self-organize and thrive by working in the context that Scrum creates. Through people those benefits can be unlocked to wider ecosystems.

Are we Done with Scrum?

Verheyen, Gunther - Scrum - A Pocket Guide (A Smart Travel Companion)In my book “Scrum –  A Pocket Guide” I present 2 major challenges, that will help define the future state of Scrum:

1/ The Power of the Possible Product

From…

View original post 567 more words

Essential Agile

The essentials of Agile software (product) development:

Accept that you start not knowing the solution. Understanding is emergent.

Take the following approach:

  1. Find out where you are
  2. Take a small step towards your goal (and if there are multiple choices here, take the path of least regret, or the one that makes future change easier)
  3. Adjust your understanding based on what you learned
  4. Repeat

(Yes, that’s it).

by Pragmatic Dave

Iterative Vs Incremental approach

EmbracingAgility

 Iteration is to beautify what increment is to expansion.

Lot of times we hear these terms as iterative development or the incremental development. So whats these are or what is the basic difference in between these two?

Iterative development is the revising and improving on the things. We prepare the basic framework  or the skeleton and  then start beautifying on it. Output of an iteration is the analyzed for further refinement.

Whereas Incremental approach is start from zero and scaling it.Its just like the expansion and integrating things. Different parts are developed and integrated.Output of an increment is used as input for next increment.

 

 http://www.infoq.com/resource/news/2008/01/iterating-and-incrementing/en/resources/Patton_Incremental_Iterative_MnaLisa.jpg

 

View original post