You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm hoping someone can help advise on possible approaches to this problem I am facing. I have a project that spans multiple business units from marketing to legal and technology to compliance. My technology team would like to use story points for estimation however my compliance and legal team work on tasks that are extremely sequential in nature hence they want to use man days. For example: .... we make an application with with a government then they respond with x days then we do the next step.... so it kind of goes against the entire agile mindset. Am I trying to achieve the impossible here by combining the two different approaches?
Any ideas on how I can accommodate both approaches but integrate into a single portfolio/plan?
The answer is - sort of.
Portfolio needs one type of estimation per plan to work - but you can do one of two things to populate issues without an estimate of the type chosen. I'm not sure which version of Portfolio you're using, but the steps are pretty similar.
Using the latter, you could set the number of days each task will take using Target Start / Target End dates - when set to this these items are scheduled to last the duration of their assigned sprint, release or those specific dates.
This means you can convert time to a number of story points, baselining effort and complexity. I wouldn't say this is ideal when story points are not meant to represent a specific timebox, but it would allow you to get a rough idea of effort and timeline.
These are some options - let us know what you think.