I was asked to scope a project for a VP-level prioritization meeting for a product release. The scoping work was nothing special. But I added one new section in the resulting estimates for those VPs on which I got great feedback. As I was about to sign off, I thought to myself that these execs wouldn’t want to dig into low-level estimates for individual features unless they wanted to discuss what needs to be cut to the timeline. So I prepared an overview table showing the aggregated scope for each product area and the total (see below).
Young Reacts #241
Young Reacts #241
Young Reacts #241
I was asked to scope a project for a VP-level prioritization meeting for a product release. The scoping work was nothing special. But I added one new section in the resulting estimates for those VPs on which I got great feedback. As I was about to sign off, I thought to myself that these execs wouldn’t want to dig into low-level estimates for individual features unless they wanted to discuss what needs to be cut to the timeline. So I prepared an overview table showing the aggregated scope for each product area and the total (see below).