Daily meetings are an essential communication tool within Lean-Agile, specifically for Agile Planning and Agile Project Monitoring and Control. So if you notice that people don’t show up then you could have a problem.
Continue reading
Author Archives: Steven Thomas
What is Agile Governance?
Personally I think good governance is essential for successful delivery, either within a programme or project, or part of on-going product development.
The recent publication of Governance for Agile delivery: Examples from the private sector July 2012 by the British National Audit Office suggests the UK government is also very interested in Agile and how it can be used to deliver value. But within the constraints of good governance.
However the term “governance” is rarely used along side “Agile”. As a agile programme manager I thought I’d try to answer the question “What is Agile Governance?”
Continue reading
Is the Scrum Master Protecting the Team a Bad Move?
Simon Baker (@energizr) recently tweeted “If ur a scrummaster protecting the team is a bad move. Help the team fend for itself. Shielding ppl from the big bad world creates ignorance” (04 Sep 2012). Simon might be right about creating ignorance, but the Scrum Master as a shield might also be good for delivering the project.
Continue reading
Build Less, Start Sooner, Innovate Constantly
Jim Highsmith proposed two simple strategies for successful software development: Build Less, Start Sooner.
Jim’s observation is genius, but I would add “Innovate Constantly”.
Continue reading
What do I do When Tasks in the Sprint Plan are not Finished?
This is what having a large number of tasks unfinished at end of Sprint looks like:
Not pretty.
It is best to avoid over commitment so the answer to “What do I do When Tasks in the Sprint Plan are not Finished?” is to lower your expectations next time you go into planning. Using Scrum language you should ensure the team only commit to what is achievable, and that is obviously less than they thought was possible the last time around.
You’ve also got to tidy the up the mess left by the previous Sprint. Have a look at the unfinished tasks and decide if they are necessary for your high priority user stories. If so, then schedule them into the next Sprint. If not, then forget about them.
Finally, you have to decide what credit you can give yourself, i.e. what velocity you earned in the previous Sprint. Personally I start hard line about this. You can only claim a user story if it is completed, so you can only add the story points for that user story if all the tasks have been completed. No partial credit.
Having said that:
- If you find that the unfinished tasks are actually unnecessary then you can claim credit for the whole user story.
- It is sometimes possible to split a user story into meaningful sub-parts. If one of the sub-parts has been completed then you can claim the story points of the sub-part for velocity
This post is part of my What do I do When … ? series. Please drop me a line or add a comment if you’ve got a question you’d like answered.
Continuous Delivery is Inevitable
Continuous delivery gives the capability to identify a requirement, code a solution, test it, and release it within a few hours. As I see it continuous delivery will become the norm amongst software companies. I think the trend is inevitable.
Continue reading
Opportunity Assessment – 10 Questions to Evaluate Proposed Features and Projects
You should vet proposed features of a product and, at a higher level, complete projects. A quick and light weight way of doing this is with the 10 questions of the Opportunity Assessment.
Continue reading
Software Craftsmanship should be Professionalism and a Dedication to Improvement
This is the last post in my series on software craftsmanship. I thought I’d end the series with a brief summary and recommending a (new or just different) definition for software craftsmanship.
Continue reading
Three Options When the Boss Changes Priorities Mid-Sprint
So your boss comes to you mid-sprint and demands a new oscillating-email-ingest-engine. Right now. Nothing else is higher priority.
Scrum says “Say no”. I think the discussion is more nuanced.
Continue reading
Rugby is a Better Analogy for Agile Delivery than the Scrum
This post is partly about the game of rugby and partly about the agile method called Scrum. Although I’ve a lot of experience with Agile approaches to software development, including Scrum, I must confess that my experience of rugby is limited to watching the All Blacks during the Rugby World Cup. Despite that caveat the theme of this post is that rugby is a better analogy for agility than Scrum is.
Continue reading