So many folks want to flip a switch and magically become agile. They want all the benefits without any of the hard work that comes along with really transforming the organization. People think that just because they read a book… or took a few days …
If you were going to write a book using agile methodologies, what might that look like? You might be inclined to create a backlog of topics… maybe play a little planning poker to get some idea of how big your book is in story points. You’d start wr…
Earlier today we noodled on the secret sauce… maybe even THE most important value add… of implementing a Kanban system. Kanban gives us a very visual way of identifying and elevating the constraints in our system. The ONLY way to really get a tea…
Last week I did a post called “The Hard Reality”. I made the point that anything you build… any document you create… that doesn’t result in revenue for the business… is wasting time and money. Personally, unless you build software as a hobby……
We all want to be really good at what we do… we strive to get better… we want to think that we are making a contribution to the success of our organizations… we want to think that we are adding value. The hard reality… and one we NEED to reall…
Is there a difference between the value a team delivers and their velocity? Said another way… if I increase the velocity of the team… aren’t I getting more value from them over time? Like so many things we talk about here… the answer really dep…
A rejection of the idea that agile teams should use a Release Backlog in addition to the already generally accepted Product and Sprint (or Iteration) Backlogs.
A while ago I posted about why I feel you shouldn’t estimate bugs. In a nutshell, if you estimate bugs you’ve essentially ‘double-dipped’ the feature. There’s the estimate for the feature and the estimate(s) for the bug(s) introduced while the feature was being built. If you’re using Scrum defects go to the top, they don’t [...]