Project Management Challenges

Scope refinement

• Scope must be defined upfront prior to kicking off a project. Lack of a defined scope leads to misalignment and inefficient use of resources.
• Follow the Project Request document with a Charter or Project Definition Document with details including your Definition of Done.
• Ensure the Sponsor and initial team review and approve the Scope Definition (Charter, Project Definition Document).

Requirements

• Waterfall project define requirements in the Plan phase allocating time for Requirements Analysis.
• Requirements are based on the scope and define the Functional and Non-Functional work items the project will deliver.

A solid Scope Definition allows the project to flow forward in a logical way.

Scope documents include background information as an overview of the reason the project is necessary, the challenge the project will solve, scope of the project, out of scope items - the project will not deliver, definition of done, high level resource list.

Development

Following the requirements a high level design will be created illustrating the architecture and design planned. At times the Architecture Review Board will formally review and approve any new development plans.

Test and Quality Assurance

Quality Assurance ensures the introduction of new features and functions work properly in the Production environment.

Deployment

Following the requirements a high level design will be created illustrating the architecture and design planned. At times the Architecture Review Board will formally review and approve any new development plans.

Closure

Lessons Learned and retrospective are important to gain insights into quality improvements. Retrospective allows the team to inspect and adapt at each iteration. Sullivan Technology Associates can provide depth and insight into all SDLC phases - Waterfall or Agile.