Difference between revisions of "Proposal Effort Evaluation"
Jump to navigation
Jump to search
(Created page with "As part of the Profile Proposal Process, the Technical Committee estimates the effort required (in terms of TC Bandwidth) to develop each of the proposals. The effort est...") |
|||
| Line 2: | Line 2: | ||
The TC in each domain chooses how it estimates. This page reflects some ideas being tried out in the [[Radiology|IHE Radiology]] domain. The idea is to expand on the Breakdown of Tasks section in the [[Brief Proposal Template]] by estimating "effort points" for each task. Turns out Agile methodology already thought of this, so the material below borrows from [https://www.mountaingoatsoftware.com/blog/what-are-story-points Story Points]. | The TC in each domain chooses how it estimates. This page reflects some ideas being tried out in the [[Radiology|IHE Radiology]] domain. The idea is to expand on the Breakdown of Tasks section in the [[Brief Proposal Template]] by estimating "effort points" for each task. Turns out Agile methodology already thought of this, so the material below borrows from [https://www.mountaingoatsoftware.com/blog/what-are-story-points Story Points]. | ||
| + | |||
| + | ==Method== | ||
===Proposer Homework=== | ===Proposer Homework=== | ||
Revision as of 17:16, 30 August 2018
As part of the Profile Proposal Process, the Technical Committee estimates the effort required (in terms of TC Bandwidth) to develop each of the proposals. The effort estimate is considered by the Planning Committee when they prioritize and select which Profiles will be developed this cycle.
The TC in each domain chooses how it estimates. This page reflects some ideas being tried out in the IHE Radiology domain. The idea is to expand on the Breakdown of Tasks section in the Brief Proposal Template by estimating "effort points" for each task. Turns out Agile methodology already thought of this, so the material below borrows from Story Points.