tsmith512/estimate-with-points-and-slices

A presentation on estimating for iteration using thin vertical slices and story points.

estimate-with-points-and-slices's Issues

Fix up the TOC page

• It hotlinks its CSS from tsmith512/intro-to-singularity
• Shorter intro
• Add some of the charts / diagrams
• OG / card info for sharing

Drop the DCCO code sprints info after the event

Swap out the Scrum image, don't know rights on it

Version Report image isn't a great example

Notes from L10-8/23

Private internal meeting wrt vertical slices and backlog building, see Notion page for "Notes from the 8/23 Solutions Level 10 Meeting" and add.

“I didn't have time to write a short letter, so I wrote a long one instead.” -- Mark Twain

Slim your slide copy

Don't forget to add the DCNA 2019 info

That picture of you holding the green pumpkin was _years_ ago

DCCO Feedback: POs don't set the sizes!

An attendee asked me about the appropriate team size for using this process (he's a freelancer) and also left with the impression that the PO/stakeholder sets the story points. Must describe an estimation process where the PO poses the problem, and the team sizes the need and solution (and options). -- Ties back to how the team needs the ownership to make the commitment.

Replace the sketches. Those were good for the video...

DCCO Feedback: Question about lining epics and story points up with dollars

Answer on the fly boiled down to comparable projects, sizing the epics bucket, using the forbidden number to translate between budget feature-level/segments and sized epics.

Jon C was talking to someone about "project comps" -- meaning comparable projects, not design comps -- and that seems to be the right language for what I was getting at