Jeff Patton recently reminded me of two simple strategies for software development that I’ve talked about from time to time—Build Less Software and Start Sooner. I thought I’d follow up on Jeff’s blog and revisit these simple, but powerful strategies. First, managers and executives complain a lot about not delivering software (or any other product […]
I led a discussion at the Ottawa Agile and Scrum groups last week.
I asked the group to come up with some reasons to do Release Planning. In essence, they represent the meta ‘purposes’ of release planning. Purposes that one’s approac…
One thing people are learning is that you can’t plan uncertainty away. Plans are good for things we know, or things that we may have some control over. However uncertainty—and its close cousin’s ambiguity and velocity—defy planning. When I originally introduced my Adaptive Life Cycle in Adaptive Software Development, the three high-level phases were Speculate, […]
I want to show a real easy way to put user stories in a spreadsheet-based product backlog. I wrote this after seeing someone tweet a screen capture of a product backlog I made 9 years ago and thought to myself, “Yikes, that’s out of date for how I do it today…” As you probably know […]
Agile Math The basic math of team based agile is pretty simple. You can slice it several ways, but at the end of the day, one of these three basic formulas has to hold true. It’s all about time, cost, and scope… you get to decide which two constraints you want to lock, but then […]
The weather turned nice about two weeks ago, which meant it was time for spring cleaning about the Cohn home, affectionately known as the Cohnderosa (which will only mean something if you’re old enough to remember “Bonanza”). While washing the windows around the outside of the house I had plenty of time to think about […]
The concept is simple: there are six levels of planning in an organization, often represented as layers of a metaphorical onion. In the agile planning onion, strategy is the outermost layer. This is meant to indicate that it is the driver of all the planning in the inner layers, which have shorter time horizons, down […]
For many of you, there will be instances where Scrum or Agile is something a company is trying but does not really buy into or understand yet. I would like to start by saying. There is hope! The following story is about implementing Planning Poker in Priority Meetings at the senior management level using the […]
I think I’ve been pretty successful in my career. But if I was better at planning, I wouldn’t have achieved half the things I’ve achieved in my career! In fact, I wouldn’t even have started some of them… In reality, there are some things you can plan, and some things you can’t. The trouble is, in most organisations we’ve come
Planning Poker is an estimating technique used by many agile software development teams. Like many agile development techniques, Planning Poker is very simple. Simple, but effective. First of all, agile teams should ideally estimate together. As a team. If the team is big, and people are working on different products, it’s okay to split the team into smaller groups. But
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. ”
Kelly Waters
Emma Hopkinson-Spark
“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.”
Emma Hopkinson-Spark
If you would like to get in touch with one of the team at 101 Ways, then please fill out the form below or email us at contact-us@101ways.com.