Jesus MartheynProject Manager SR Lvl 2| GlobantMedellin, Antioquia, Colombia
Hi you all. Two weeks ago I was talking with another PM about how to implement a WBS on agile projects. It was really hard to well define the way, and we did, but we are still thinking the way we did is so embarrassing. Could you please share with me any suggestion or lessons learned about this, even more, is there somebody that use WBS in agile project management? Saving Changes...
Shweta PaiScrum master| ResMedHalifax, Nova Scotia, Canada
We use story mapping techniques at our workplace. Elaborating on what has worked for us -
1) Identify very high level features as below. Atlassian has several videos on how to do this.
2) We then logically spread out the work on a whiteboard. If your team is geographically distributed, I highly recommend buying the easy agile maps JIRA plugin. You 'd be able to create the same in JIRA.
3) We discussed what we knew and the approach of organizing the work came from the team itself.
We did this in the beginning and the map kept on evolving based on what we learnt at every phase. My 2 cents here is that while WBS was more time-driven i.e. create every task and track everything to completion, the story map keeps evolving. The team has a discussion about functionality and everyone's on the same page. We discuss strategy as a team. We decide the dates for each phase depending on what we know at the time. This wasn't the case with WBS. If Jan 2019 is your date then you 'd fit everything to be done by that date regardless of whether it was practical. :) Saving Changes...
