Forecasting timelines for Stakeholders

There has been a lot of great movement towards agile software development over the last decade or so. However, there are still a few struggles or gaps you’ll find in most organization today that claim to be agile. That is with the dilemma of how to forecast updated timelines to the customer and or stakeholders.

Product t-shirt sizing chunks of work, or forecasting based on a well-groomed backlog ?

If you ask a typical agile dev team member how they would handle providing timelines of work to be completed, you might be surprised by the answer. They might just not care about what we may or might not do six months to a year from now but more about continuously delivering what the customer wants now:

Project Plan Gantt charts and Product Roadmaps with far out timelines and Roadmaps are the old way of doing things. A constant feedback loop with the customer is the new way to do things in the agile software development world.

Continue reading “Forecasting timelines for Stakeholders”

Advertisements

People > Process

In the past, one of my dev teams had some disagreements on how product was interacting with them during sprint sessions and day-to-day as well there were some frustrations around who was owning the tools we were using for tracking teams epics, user stories, in preparation for backlog grooming, etc. Several people in a network connected by arrows

After many retrospectives and after pulling both parties aside to help guide and coach them in the right direction, myself and the dev team manager got in a room and discussed what could be done to move forward in the right direction with both product and dev on the same page.

After racking our brains, I remembered something very fundamental, it’s more about people over process which is called out in the Agile Manifesto.   Continue reading “People > Process”