dewv / dewv/project-management-template

Stakeholder review of Inception phase progress

Open
#1 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

The project begins in the Inception phase. Two weeks into the project, all success-critical stakeholders should meet and try to come to agreement on the following points.

---
We agree that the work products captured in this repository ...

- [ ] ... record a complete and compatible set of win conditions for all success-critical stakeholders.
- [ ] ... give us an adequate understanding of the scope of work.
- [ ] ... show that we have the capability to build a solution that satisfies all win conditions.
- [ ] ... show that we can deliver a cost-effective solution within the window of opportunity.
- [ ] ... give us an adequate understanding of the project's risks.
---

Check the box for each item that is endorsed by all stakeholders. Then create a comment on this issue to document the outcome of the review. The comment should contain **one** of these three possible outcomes.

- All the checklist items are complete, and the Inception Phase is complete. We agree to commit a higher level of resources to work toward the Life Cycle Architecture milestone, with another review in 2 weeks.
- Some checklist items are incomplete, and the Inception Phase is not complete. We agree to invest 2 weeks of additional work toward this milestone, then hold another review.
- Some checklist items are incomplete, and we agree that no more resources should be invested in this effort.

Finally, set the due date of the active milestone (LCO or LCA) for 2 weeks in the future, when the next stakeholder review will take place.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with issue #1 and review the five stakeholder checklist items and the three allowed outcome statements. Arrange the Inception review, check only items endorsed by all stakeholders, record the selected outcome in a comment, and set the active LCO or LCA milestone due date two weeks ahead.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.