>
Showing posts with label Scrum. Show all posts
Showing posts with label Scrum. Show all posts

Wednesday, March 6, 2013

Release Sprint v/s Release v/s Deployment

Lets try to understand these three terms that sound so simillar - Release Sprint, Release and Deployment -

1) Release and Deployment are more or less same. Though these two may have different meanings in some cases - say in waterfall we say 'QA release' and 'Production deployment' - that are two different terms, but in this context these two are same. Once the Sprint Review is over, it 'may be' released/deployed.
At times, 'Release' can also be referred as 'Release Cycle', e.g. a large project can be proken down into mutiple Release Cycles and each may tie back with some organization/business/program objective. In my view, Release (as in Release Cycle) has same meaning in Waterfall and Agile.
2) Release Sprint is actually a special sprint that may take place if release/deployment itself is sizeable effort that is expected to span 2-4 weeks. This type of Sprint is not recommended and should be avoided, as efficient Scrum teams would always finish a functionality that meets 'Definition of Done' and always has a ROI value attached to it so can be released, hence teams are expected to use automated deployments tools to avoid need of such special Sprints.

Sunday, March 3, 2013

Theme, Epic, Story, Task, Feature

Theme, Epic, Story, and Task are Agile Scrum terms, whereas 'Feature' is a term is not so often found in Scrum handbooks (probably introduced by some eager minds).

1) Theme is logical grouping of stories
2) Epic is just a large/big story - that needs to be broken down in smaller stories
3) Story is a story (explained elsewhere), that is broken down into tasks to be worked upon by developers as per agreed 'definition of done'

In terms of size - Theme and Epic may be of different sizes, rest would always be in this order (from large to small) - Epic > Story > Task
So technically, only these two combinition are possible (just in terms of size as theme and epic are not comparable - if anyone is interested) -
1) Theme > Epic > Story > Task
2) Epic > Theme > Story > Task


Acronyms, Agile and Associations

Acronyms/Mnemonics in Agile and their associations -

Associations - 
DEEP - properties or characteristics of a good product backlog
INVEST - properties or characteristics of a good user story
3 Cs (CCC) - three critical aspects of a user story (or in 'plain english' - one of the many ways to write a user story).

Full forms -
DEEP - Detailed Appropriately, Estimated, Emerging/Emergent, Prioritized
INVEST - Independent, Negotiable, Valuable, Estimable, Small, Testable
3 Cs - Card, Confirmation, Conversation

Waterfall Manifesto

Take a break from Agile Scrum and here is what I would strongly recommend you all - the Waterfall Manifesto. I assume the authors are serious when they describe this as - "Manifesto for Realistic Software Development"

Read on what author documented in waterfall principals (and they are so practical and true.....!) -
  • Changing requirements are a pain in the ass.....and make him pay dearly for just thinking about change.
  • Business people and developers ......They both have other important activities to carry to waste their precious time in meetings. Furthermore, they do not speak the same language.
  • Build projects around solid processes because you know that individuals are even more unreliable than software
  • Project reports and billable hours are the primary measure of progress.
  • Recognition of technical excellence and good design allows developers to think that they are free creative artists
  • Complexity - the art of maximizing the amount of time needed to understand your design and code - is essential to define your value as a developer ( and to protect your job).
  • At regular intervals, the team should meet to eat pizzas and drink beer. It helps developers to forget that they are working in a bloody software development project and confirms that the management really cares about people
 Reference and credits: www.waterfallmanifesto.org

Saturday, March 2, 2013

Sprint v/s Iteration

Lets understand the difference between Sprint and Iteration in three easy steps -

1) Iteration is a generic Agile term that is used for any process thats iterative/repetative
2) An iteration in Agile Scrum is called a Sprint
3) Other Agile variants may or may not use same term to define iterative work, but these two are most common terms in use