Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,299,230
Community Members
 
Community Events
165
Community Groups

How to Implement a 1 Team Member Works on 1 User Story Policy in Portfolio?

Hi,

I am doing my first test plan (improved interface):

  • I have 3 epics x 2 issues each, all with 2d estimation.
  • I have a team with 2 members each with 40 hours per week capacity equaling 5 days per week.

Portfolio squeezes all issues to just one day implementation, implicating (I guess) that both team members work together on all issues and thus are able to finish them off in just one day.

Is there any configuration magic to avoid this? Especially in software development it is completely unrealistic to put two developers on the same task.

 

Thanks and regards,

Anton

1 answer

0 votes
Thomas Deiler Community Leader Jul 18, 2019

Dear @Anton Maleev 

Especially in software development it is completely unrealistic to put two developers on the same task.

This is not the whole truth: https://en.wikipedia.org/wiki/Pair_programming

So long

Thomas

Thanks @Thomas Deiler ,

good point, I take the "completely unrealistic" back :)

Follow up:

https://confluence.atlassian.com/jiraportfolioserver/auto-scheduling-issues-967895245.html

(quote - table transposed)

Technical details: Maximum people assigned per story
Live plans (versions 2.0 to 2.27): You can configure how many people can be assigned to a story.
Plans with the improved interface: Only one (1) person can be assigned to a story.

Puzzling, because I was working with an "improved" plan. Anyway, I switched several times between "live" and "improved" and it suddenly started working as I expected. Worrying that I didn't understand why, though.

Suggestion to Atlassian:
Could be a good idea to expose as much as possible of the governing parameters as configuration options. It would even help to see read-only stuff, just in order to know, how the engine takes its decisions.

Best regards,
Anton

Second Follow-up:

I just found out that the configuration for "live" plans is much more verbose than that of the "improved" plans.

It appears to me the "improved" plans are still "work in progress". I am also missing completely the "capacity" information on the plan there.

We will stick to the "live" plans until the "improved" ones are ... improved :)

We are running 3.6.1 and will keep updating.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

An update on Confluence Cloud customer feedback – June 2022

Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...

260 views 2 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you