Community
Participate
Working Groups
This items was reported by Jim Ruehlin as a result of the 11/8 OpenUP/Basic PM alignment review: Risk List • Revise the headers to match the format of other checklists Headers should be categories that hold questions, rather than questions themselves. • Have all potential risks been identified? This topic is too general. There should be a number of questions here that help the user determine if all risks have been identified. E.g. one bullet item for each risk type (technical, resource, business, ...), and questions such as "Can any team member or stakeholder identify a risk that's not listed?", "Can anything happen that will slow down development?", "Is it possible that competitors will release competing functionality before the team does?" etc. • Are risks described without ambiguity? This is a good question for the checklist, but a full explanation should be in the corresponding Concept. • Impact, Priority, and Mitigation Strategy This could be one item, or they could all be under the same heading, since it's just a check that each risk is complete. It doesn't help identify more risks. • This checklist is only accessed from the Artifact: Risk - it should also be referenced from appropriate tasks and guidances • Task: Plan Project • Task: Plan Iteration • Guideline: Risk
Comment from Brian Lyons on bug 163876, related to this bug: Is this notion of attaching the checklist to every place the Risk List is updated appropriate? If someone was to create a process with a checklist per artifact, I wonder if it would be overkill to point to the checklist in each task that talks about the artifact. Other changes to the checklist are definitely appropriate. With respect to needing checklists for all the other artifacts, I would like for us to discuss the notion of a checklist for each artifact as a rule of thumb.
Resolved... please review I didn't change the headers because "At the Nov. 28 Architecture review telecon we agreed that check items should be in the form of a question. Checklist to be updated accordingly." I didn't made any changes on the last topic because I agree with Brian Lyons on comment #1 I also replaced mitigation strategy for risk response strategy (mitigation is just one of the possible responses to a risk), like described in the reviewed concept Risk Ana
Bug verified - closed.
