Karon shared a video to help us think about the Complexity model we are trying to develop (decision matrix): Agile vs Waterfall
Review of draft Task List/Complexity Model.
INITIATE
[aka Define, Analysis, Business Justification, Assessment, Scoping. Put project structure together, identify the problem, draw up a charter, identify the CTQ/KPIs, etc.]
GATHER REQUIREMENTS
[aka Discover, Measure, Analysis. Document the requirements, identify the “what”, perform process mapping, etc.]
*PARTNER
[secure external resources (optional)]
DESIGN
[aka Analysis. Document the functional specifications, come up with the “how”, perform conceptual and data modelling, etc.]
DEVELOP
[aka Build, Improve. Code and test, CIT, SIT, etc.]
TEST
[aka QA. UAT, disaster recovery, business continuity, etc.]
DEPLOY
[aka Launch, Implementation.]
MAINTAIN
[aka Control, Support. Perform ongoing maintenance of the system until it is sunsetted.]
Agreements:
- take out ownership for Phase I - focus on tasks and phases
- Phase II would be to add purpose of tasks, risks and roles
- Phase III would be to collapse some of the columns - consider whether complexity model should be S, M, L for starters
- table presentation of material (tool we will use) until after decision matrix (complexity model) is complete and task lists in more final form
- want the ability to look at just one size project or just one phase as opposed to everything at once
Notes from today's meeting: PMBAMtgNotes011111.docx
Next steps:
- members review the task list and focus on what tasks are missing and should be incorporated
- email the group with enhancements and additions
- group will pick this up again for February 1, 2011 meeting
Next Week:
- review of draft tool inventory: Draft Inventory of Current Available Tools