Recently I saw a brief set of questions from Nokia to assess whether or not a team is ‘agile’. And by ‘agile’, I think they meant to what extent the team was following agile practices Scrum and XP (eXtreme Programming), not whether or not they could touch their toes 🙂 I’m not sure if it was deliberately brief to emphasise
I recently described User Stories and the composition of a User Story Card – Card, Conversation and Confirmation. I’m not really sure if you would consider this user story example to be good, bad or indifferent – I guess it depends what you’re used to – but here is an example nevertheless! This is the front of the card. The
Popular author Mike Cohn has written this interesting article, Patterns of Agile Adoption… If you’ve already adopted agile development, what route did you take? What advice would you offer other people just adopting agile now? And if you had your time again, would you do the same again? Kelly.
If you’re capturing user requirements using User Stories, write them on a postcard… (a blank one of course!). A User Story Card should ideally comprise 3 parts: Card, Conversation and Confirmation… Card The heading section of the card should include the name/description of the user story, any reference numbers, estimated size, etc. Conversation Most of the front of the card
User Stories are a simple way of capturing user requirements throughout a project – an alternative to writing lengthy requirements specifications all up-front. User Stories are derived from XP (Extreme Programming), however they can just as easily be used for requirements gathering in any agile development methodology, or indeed in any home-grown development process. A User Story is a simple
I really like this one page introduction to agile methods compiled by Sanjiv Augustine. But it still leaves me wanting less. It’s a really nice, fairly concise explanation of agile methods, although is still focused on development professionals with experience and/or a keen interest in software development and project management practices. The agile manifesto also provides a similarly concise and
In my opinion, ScrumMaster Certification isn’t worth the paper it’s written on. Don’t get me wrong, I’m a big fan of Scrum. Huge fan. It’s really helped to transform the web development department I head up. And I’m not getting at the training companies that deliver Certified ScrumMaster training either. Nor the people that go on the training. But I
In agile development, it’s easy to develop bad habits! Or to have trouble kicking them. A blog post from Chris Stirling quotes some good examples… Daily stand-ups not every day Mini waterfalls in iterations Pressing too hard for increased productivity Team Leaders taking over team responsibilities I’ve certainly seen all of these bad habits in action. In fact I’ve done
In a few entries on my blog, I have referred to Velocity and only briefly explained what it is. I think it’s about time I explain properly for those not familiar with it. Velocity is terminology from the Scrum agile methodology and is basically the same concept as Earned Value in more traditional project management methods. This is how it
Some agile principles come naturally. Others you have to work at. Here are 3 agile principles I think require an extra level of care and attention. Perhaps they’d make good new year’s resolutions? 1. Work to fixed timescales The end of a Sprint is the end of a Sprint. Not near the end. The end. Meeting fixed timescales means paying
I was very interested to read this blog post by Ben Alfree, “I’m a slow starter“. In his article, Ben describes how agile development makes things slow to start off with, but pays back in the end. Actually my experience is the extreme opposite… I have a lot of experience in traditional waterfall projects as well as in agile projects.
Discussing software development metrics at my place of work, a colleague (Derek Morrison) came up with a neat concept – a way of measuring Business Value. We’re using Scrum as an agile management framework, estimating in points and measuring Velocity to help plan future Sprints. For those not familiar with Velocity, it’s the total estimated cost (in effort or points)
Search the Blog
What am I interested in?
Agile Management Made Easy!
All About Agile
By Kelly Waters
“’Agile’ is one of the biggest buzzwords of the last decade. Agile methods often come across as rather more complicated than they really are. This book is an attempt to unravel that complexity. To simplify the concepts. This book breaks the concepts into small bite-sized pieces that are easy to understand and easy to implement and delivers the message in a friendly and conversational style. Allaboutagile.com is one of the most popular blogs about agile on the web. ”
Agile 101 is available to purchase. GAME ON!