Posted by tac_admin, December 29, 2011

Project Lifecycles

Sticking my theme for this month in getting back to the basics, this post explains what work gets done in each phase of the project lifecycle.

Phase Name


Plan the project This phase of the cycle involves discovery of and documenting the need and assigning resources:

  • Market research deriving need from larger project
  • Managing and assigning available resources
  • Alignment with corporate standards  and strategic objectives
Scope the project During this phase the objectives of the project and the scope are defined:

  • Clarify purpose and objectives
  • Identify organizational units involved with the project
  • Identify people/systems interfacing with the project
  • Determine business process included in, and executed from, the project
  • Identify project assumptions and risks
  • Establish a system for organizing information
Elicit, analyze, and document requirements The most important task of the BA is to elicit, analyze, and document detailed requirements:

  • Determine where to find requirements
  • Define an approach for eliciting requirements
  • Identify and prioritize requirements
  • Document the requirements
Design a solution
  • Communicate the requirements
  • Recommend the solution and/or solution alternatives
Build or buy the solution
  • Write new or modify new software
  • Install any vendor or purchased software
  • Write new procedures and/or assist with organizational changes
Test the solution The most important task of the software tester is to test based on the requirements and then move out of the box to test what isn’t in the requirements:

  • Verify the software meets the requirements
  • Verify the application looks, feels, and acts according to the expectations of the business
  • Get user acceptance
Implement the solution
  • Field roll-out/implementation
  • End-user training delivery
  • Warranty period completed
Conduct post-implementation review
  • Assess the solution
  • Elicit information for enhancements

One response to “Project Lifecycles”

  1. […] overstated. Per the BABOK® Guide, stakeholder analysis is performed as soon as a business need is identified and will usually be an ongoing activity as long as business analysis […]

Leave a Reply

Your email address will not be published. Required fields are marked *

Get in touch today

Speak directly with The Analyst Coach
and get pointed in the right direction.

Preferred Contact EmailPhone

Subscribe to receive our free white paper on how weak requirements effect strong companies


Sign up to get your FREE Business Analyst Survival Guide

Don't worry, we hate spam too. We will never share your information to third parties.