Document best practices for creating and estimating Epics
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	• JAufrecht
	Apr 30 2015, 11:59 PM

Description

Short description of practices for bootstrapping a Product Burnup to have a useful-sized backlog
- Estimating Sagas
- bulk estimation with relative card mapping
- storing a mix of big and small in Phab
- relation to OKRs

2) Clarify release terminology and outcome vs output
- timeboxed release
- "marketing" release (cut from this Phab task; too big for one task)

Event Timeline

• JAufrecht created this task.Apr 30 2015, 11:59 PM

• JAufrecht claimed this task.

• JAufrecht raised the priority of this task from to Needs Triage.

• JAufrecht updated the task description. (Show Details)

• JAufrecht added a project: Team-Practices.

• JAufrecht added subscribers: Aklapper, • JAufrecht, • ksmith.

• ggellerman triaged this task as High priority.May 14 2015, 9:31 PM

• ggellerman edited projects, added Team-Practices (This-Week); removed Team-Practices.

• ggellerman set Security to None.

• ggellerman moved this task from To Do to In Progress on the Team-Practices (This-Week) board.

• JAufrecht added a subscriber: nshahquinn-wmf.May 15 2015, 9:06 PM

This looks like a great tool for breaking stories smaller:

http://www.agileforall.com/2012/01/new-story-splitting-resource/

However, this Phab task is about best practices for managing Epics and Sagas, so that's a step in the other direction. Still worth bookmarking.

Initial thoughts: https://www.mediawiki.org/w/index.php?title=Team_Practices_Group/Best_Practices_Handbook

Kevin, this is ready for review. I think the next thing it needs, but I don't know enough yet to do it, is to document how to do these two techniques in Phab, which could be any of:

how to do the estimation on paper and store the results in Phab
how to do everything in Phab as it is today
how to do everything in a version of Phab that doesn't exist yet.

• JAufrecht moved this task from In Progress to Needs Review on the Team-Practices (This-Week) board.May 19 2015, 9:12 PM

• JAufrecht renamed this task from Document best practices for Epic or Saga tracking to Document best practices for creating and estimating Epics.May 21 2015, 9:22 PM

In T97738#1289316, @JAufrecht wrote:

This looks like a great tool for breaking stories smaller:

http://www.agileforall.com/2012/01/new-story-splitting-resource/

Great page! I added it to the TPG Recommended Reading list (https://www.mediawiki.org/wiki/Team_Practices_Group/Recommended_Reading)

• ksmith moved this task from Needs Review to In Progress on the Team-Practices (This-Week) board.May 22 2015, 7:35 PM

After some discussion with Joel, I added a section describing the lightweight approach that we used at my last job.

• ksmith moved this task from In Progress to Needs Review on the Team-Practices (This-Week) board.May 22 2015, 10:31 PM

I think this is back in Joel's court. Not sure if more review or more work is needed to consider it done.

• ggellerman closed this task as Resolved.May 28 2015, 9:56 PM

• ggellerman moved this task from Needs Review to Done on the Team-Practices (This-Week) board.

• JAufrecht added a project: User-JAufrecht.Nov 3 2015, 9:24 PM

• JAufrecht moved this task from Incoming to TPG on the User-JAufrecht board.Nov 3 2015, 9:46 PM

Document best practices for creating and estimating EpicsClosed, ResolvedPublicActions

Description

Event Timeline

Document best practices for creating and estimating Epics
Closed, ResolvedPublic
Actions