Engaging with apc.au
From apc.au wiki
Over the years at apc.au, we've found that there are certain conditions and processes that help ensure we work on a successful project:
- Clearly identify the sponsor - this is the single point of ownership for a project - the buck stops with this person (or committee). They have the final say and the power required to resolve issues between stakeholders.
- A project must have clearly identified the following areas and captured them in a document that is maintained throughout the life of the project:
- Stakeholders (critical and otherwise)
- Success criteria (how will you know it's been done correctly?)
- Restrictions & constraints (what limits are put on this project?)
- Assumptions
- Related Projects (what other work impacts this project or will this project impact?)
- Scope & objectives (what are we doing, what aren't we doing, why?)
- Quality definition (what defines quality for this project and how important is it?)
- Risk assessment (what are the risks associated with this project and how are we mitigating them?)
- Never in a rush - if it's rushed, the odds are it will be done poorly. If we're too close to the deadline to do a good job, it's best to not disrupt everyone's schedules to rush through something that probably won't look good or reflect our best efforts.
- All parties to agree to changes - when collaborating on a document, it is essential that the document does not get released as a final version without all parties agreeing to all changes (no making last changes then publishing it without checking those changes, no matter how small).
