jump to navigation

Solution Delivery Methodologies September 7, 2005

Posted by Coolguy in Service Delivery.

Methodology A:

  • Phase based, milestone-driven and iterative mode
  • Adoption of this methodology will streamline the delivery of the solution and reduce schedule and budget risks to the project.
  • Every release of the application should go through a project lifecycle, a process that includes all activities in the development cycle that take place up to the release.
  • The main function of a lifecycle model is to establish the order in which a
    project specifies, implements, tests, and performs its activities.
  • This will help streamline the project and help ensure that each step moves the customer closer toward the goal.


  • Envisioning is the initial phase of a project life cycle.
  • It implies the beginning steps required to identify, launch, and manage a new technology engagement.
  • The concepts presented in this phase are the first steps necessary to producing a successful project.
  • Envisioning is fundamental to the success because it sets the base upon which team members will build a shared vision.
  • The purpose of envisioning is to get an early understanding of the project goals and constraints.
  • The envisioning phase will answer feasibility questions, gain approval from the customer’s stakeholders, and acquire a common set of expectations from everyone involved.
  • The outcome of envisioning sets the stage for the more detailed planning effort that will come later by beginning to define the scope of the project or each release.
  • Envisioning Phase Deliverables
    • Business Requirements Document
    • Scope Document
    • Risk Mitigation Plan
    • Project Plan
    • Project Work Plan
    • Project Quality Plan
  • Tasks /Activities
    • Identify User Requirements
    • Integrate Performance Support Requirements
    • Recover Current Application Design
    • Identify Quality Requirements
  • Milestones
    • Major
    • Scope approved
    • Interim
    • Core team formed
    • Scope document written
    • Risk mitigation plan written
    • Project plan created

Solution Planning

  • The work in the Solution Planning Phase begins with the definition of functional and technical requirements and performance targets that lead to activities that address the design and integration of the elements defined in the Scope document.
  • The overall design process is iterative; teams will continuously revisit
    their designs in order to resolve integration issues and tune the overall capability to meet all business, functional, and technical requirements.
  • The information gathered during this phase focuses on building out the detailed requirements and design as defined by the business requirements outlined in the Scope document created during the Envisioning Phase.
  • Tasks /Activities
    • Update Scope document (as needed)
    • Update Risk Mitigation plan with any new risks
    • Update Project Plan for those activities that will take place during the
    Developing Phase
  • Deliverables
    • Functional Specification
    • Design Specification
    • Updated Scope Document
    • Updated Risk Mitigation Plan
    • Updated Project Plan
    • Project Work Plan
    • Project Quality Plan
    • Development Architecture
  • Tasks /Activities
    • Design Development Architecture
    • Design Operations Architecture
    • Design Run-Time Architecture
    • Design User Interface
    • Design Application Architecture
    • Design Application Interfaces
    • Design Database
  • Milestones
    • Major
    • Design Complete
    • Interim
    • Logical Design Complete
    • Physical Design Complete


  • An approved functional specification and associated project plan provide the baseline for focused development to begin.
  • The development team sets a number of interim delivery milestones, each of which involves a full test/debug/fix cycle.
  • Deliverables
    • Updated Functional Specification
    • Updated Risk Mitigation Plan
    • Source Code and Executables
    • Test Plans – Unit Testing, Integration Testing, System Testing, And
    Acceptance Testing
    • Unit and Integration Test Cases, Conditions, and Results
    • Updated Project Plan
  • Tasks /Activities
    • Develop and Unit Test User Interfaces
    • Develop and Unit Test Application
    • Develop and Unit Test Interfaces
    • Create System and Acceptance Test Plans
    • Develop Database
    • Perform Integration Testing of Application and Interfaces


  • Testing activities are performed concurrently with code development.
  • During the stabilizing phase these activities take center stage, as bug finding and fixing become the primary focus.
  • Here the focus of testing shifts from coverage testing (which measures
    whether individual pieces or features of the application work) to usage testing (which measures whether the application as a whole woks as intended).
  • Deliverables
    • System Test and Acceptance Test Conditions, Cases, and Results
    • Project Documentation
  • Tasks /Activities
    • Perform System Testing
    • Perform Acceptance Testing
    • Deploy Application
  • Milestones
    • Major
    • Release
    • Interim
    • Core Technology Deployed
    • Deployment Complete


No comments yet — be the first.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: