“'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. ”
Kelly Waters
Read Me
“"Whilst there are lots of ways you can vary the game depending on the teams you have and the learning outcomes you want, the basic flow of the game play is common to all."
Why did we make the game?
https://www.101ways.com/2018/08/16/agile-101-the-game-and-how-it-happened/
How to play the game?
https://www.101ways.com/2018/08/20/agile-101-how-to-play-the-game/”
Emma Hopkinson-Spark
Yes, I want this!User Stories are certainly an easy concept. But what makes a Good User Story? That’s a bit of an open question. I’m sure everyone has a different opinion of what good looks like. But there are certainly some common characteristics of a Good User Story. Bill Wake, author of ‘eXtreme Programming Explored’, suggests this ‘INVEST’ […]
Tell me more >Let’s face it. There is no perfect solution. No perfect solution for humans to share information accurately, consistently between multiple people, and over a prolonged period of time. Especially when you add into that equation the level of detail that’s needed to capture the requirements for a major software application. And then there’s the complexity […]
Tell me more >Here’s another PowerPoint presentation for you – ‘Introducing User Stories‘. For more agile presentations, see also: * 10 Key Principles of Agile * Implementing Scrum If you find this presentation useful, please tell people about my blog… Thanks! Kelly.
Tell me more >When putting User Stories onto a Product Backlog (or feature list), you shouldn’t feel compelled to break everything down until the features are nearing development. Further down the Product Backlog, it’s fine for items to be fairly fuzzy. It’s also fine for items further down the backlog to be whole projects – large, high-level items […]
Tell me more >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 […]
Tell me more >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 […]
Tell me more >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 […]
Tell me more >
