Why agile works
Posted by: on July 5th, 2011
I tried to visualise why agile works in a one pager …. WhyAgileWorks.PDF
© 2012 scruminfo.com. All Rights Reserved.
Designed by PSD to HTML Company | Powered by Wordpress
Waterfall Stop Sign
Posted by: on April 4th, 2011
Tony, a fellow agilist was travelling the other day to a client and came upon the following , it was too hard to resist, hope it can be taken with a pinch of salt by traditionalists …. but we thought it was very appropriate.
Man has forgotten the value of experimentation to learn
Posted by: on February 25th, 2011
Has man forgotting the need to experiment so that he can learn? as each week passes I am realising that he has ! perhaps this is the time for universities and colleges to create a dedicated subject for an entire semester on “Learning through experimentation.” In my current agile project (which is well into implementation)
Scrum Themes
Posted by: on November 25th, 2010
SYNOPSIS There is a lot of confusion amongst scrum practitioners on what a theme is.I have seen articles that talk about the theme for a sprint (I see a sprint theme as a goal.) I cannot say that this is incorrect as it depends on the perception of the individual. This article provides you with
A SMART way for setting goals…
Posted by: on February 21st, 2010
What is SMART? SMART is a simple technique that helps you set goals effectively, be it product, organisational, project or for sprints. This is an effective tool to include in your Scrum techniques. What does SMART stand for? Specific Measurable Agreed Realistic Timebound SPECIFIC When setting our goals we do not want them to be
SMALL THINGS TO MAKE THE DAY COUNT…
Posted by: on October 23rd, 2009
Recently I was working in an agile environment where everyday one of the employees would use the local newspaper that contained a general knowledge quiz. Everyone in the group would get together for 5 minutes while he read out questions and everyone would attempt to answer. It was such a small thing but it became
SEPARATE USER STORY ESTIMATES – A SIGN THAT SOMETHING IS WRONG
Posted by: on October 23rd, 2009
I once observed a practice where story cards were only estimated based on the development effort. This is problematic as it has one specific focus and not looking at the total work that needs to be completed for a story to be moved into done. Product development is not just about writing code.
A SHORT GUIDE TO AGILE USER STORIES …
Posted by: on October 22nd, 2009
I have written this article in the hope that it will remove a lot of confusion in our industry on what a user story is. If you are transitioning from heavyweight to agile methods you may find this useful. I have not included estimation and how we manage stories on the backlog etc and will
THE 5 WHY’s FOR ROOT CAUSE ANALYSIS:
Posted by: on October 24th, 2008
A very simple technique to find out the root cause of a problem is to use the 5 Why’s. The number 5 is just a general guideline and sometimes it may take a lot more or a lot less “why” questions to arrive at the root cause for a given problem. The beauty of this
SCRUM POEM
Posted by: on July 24th, 2008
Not sure if anyone has ever written a scrum poem so gave it a crack ….. It is a thing called scrum and this is how it is done. We talk and discuss Then we create a product backlog without fuss A backlog has many items , they call each one a story and its
USING T-SHIRT SIZES FOR USER STORY ESTIMATION
Posted by: on March 14th, 2008
There are a number of story point scales used for estimating user stories on the product backlog. An effective scale to use for your estimation is T-Shirt sizes. T-SHIRT SIZES Size Points to Allocate XS (Extra Small) 1 S (small) 2 M (medium) 4 L (Large) 8 XL (extra large) 16 XXL(extra extra large)
SCRUM KANBAN EXAMPLE – TASKBOARD
Posted by: on March 13th, 2008
GUIDELINES FOR THE SUCCESSFUL IMPLEMENTATION OF SCRUM IN AN ORGANISATION
Posted by: on March 13th, 2008
Obtain buy-in from all responsible parties. A developer that is not willing to embrace agile should not be placed on your team, even a single doomsayer can cause major negativity, disruption and resistance to change. Pick a motivated team that is keen to embrace change. A CIO who is a heavyweight fanatic is not going
THE IMPORTANCE OF FIXED LENGTH ITERATIONS THROUGH THE PRODUCT LIFECYCLE
Posted by: on March 13th, 2008
Why are fixed length sprints (iterations or timeboxes) of the same duration important? why should these sprints not exceed a 4 week timebox? WHY 4 WEEKS? Scrum recommends that iterations do not exceed 4 weeks. I have heard of some implementations using 6 weeks. I stick with durations of 4 weeks or less. 4 weeks
PYTHON SINGLETON CLASS
Posted by: on October 16th, 2007
Here is an example of a python singleton implementation, you can find it HERE …