Member login   |   Register   |  Sign Up for Weekly TIPS

Site Map

Home

400.0 Welcome

• 401.0 The Value of Project Lifecycle Methodology

• 402.0 Writing Assumptions

• 403.0 Caveats

• 404.0 LifecycleStep Overview

• 405.0 Principles

• 406.0 Determine Project Size

• 407.0 Determine Lifecycle Model

• 408.0 Project Roles and Responsibilities

• 408.1 The Role of a Project Manager

• 408.2 The Role of an Analyst

• 408.3 The Role of the Project Sponsor

• 408.4 The Role of the SME

• 408.5 The Role of a Designer

• 408.6 The Role of the Developer

• 408.7 The Role of the Tester

• 408.8 The Role of the Database Administrator

• 408.9 The Role of a Quality Manager

• 409.0 Mapping to Other Lifecycle Models

410.0 ANALYSIS PHASE

• 410.1 What is a Requirement?

• 410.2 Use Cases

• 410.3 Asking Questions

• 410.4 Active Listening

• 411.0 Gather Requirements

  • 411.1 Elicitation

  • 411.1.1 One-on-One Interviews

  • 411.1.2 Group Interviews

  • 411.1.3 Facilitated Sessions

  • 411.1.4 JAD Sessions

  • 411.1.5 Questionnaires

  • 411.1.6 Prototyping

  • 411.1.7 Following People Around

  • 411.2 Validation

    • 411.2.1 Consolidate the Requirements

    • 411.2.2 Rationalize the Requirements

    • 411.2.3 Model the Requirements

      • 411.2.3.1 Process Models

      • 411.2.3.2 Data Models

      • 411.2.3.3 Other Models

  • 411.3 Specification

    • 411.3.1 Prioritize the Requirements

    • 411.3.2 Ensure Traceability

    • 411.3.3 Ensure Testability

    • 411.3.4 Create Business Requirements Report

  • 411.4 Verification

    • 411.4.1 Conduct Requirements Review

    • 411.4.2 Obtain Sponsor Signoff of Requirements

• 412.0 Evaluate Reuse, Buy (Rent), Build Alternatives

• 413.0 Create Requirements Management Process

• 414.0 Build Conceptual System Design

• 415.0 Define Project High-Level Strategies

• 415.1 Create Testing Strategy

• 415.2 Create Training Strategy

• 415.3 Data Conversion Strategy

• 415.4 Implementation Strategy

• 416.0 Capture Additional Client Information

  • 416.1 Develop Acceptance Criteria

  • 416.2 Develop Information Retention Criteria

  • 416.3 Create Security Risk Assessment

    • 416.3.1 Other Organizations with Security Responsibility

• 417.0 Create Test Cases

• 418.0 Re-Plan for the Remainder of the Project

• 419.0 Obtain Approval to Proceed

420.0 DESIGN PHASE

• 420.1 The Levels of Design

• 420.2 Tracing Requirements through Design

• 421.0 Ensure Architectural Foundation

  • 421.1 Development (Application) Architecture

  • 421.2 Technical Architecture

• 422.0 Validate Standards and Guidelines

• 424.0 Design the Solution

• 424.1 Online Screen Layouts

• 424.2 Report Layouts

• 424.3 Programs

• 424.5 Reusable Components

• 424.6 Security

• 424.7 Other Interfaces

• 424.8 Manual Processes

• 424.9 Design the Solution - Architecture

• 424.10 Logical Datastores

• 425.0 Build Technical Systems Design

• 426.0 Review the Technical Systems Design

• 427.0 Create Direction Setting Plans from Strategies

• 427.1 Create Testing Plan>

• 427.2 Create Training Plan

• 427.3 Create Data Conversion Plan

• 427.4 Create Implementation Plan

• 428.0 Re-Plan for Remainder of the Project

• 429.0 Obtain Approval to Proceed

430.0 CONSTRUCT PHASE

• 430.1 Source Code Management

• 430.2 Tracing Requirements through Construct

• 430.3 Get the Support Organization Involved

• 431.0 Validate Standards and Guidelines

• 433.0 Construct the Solution

  • 433.3 Program Components

    • 433.3.1 Use Caution When Downloading Components from the Web

    • 433.3.2 Overview of XML

  • 433.5 Reusable Components

  • 433.10 Physical Datastores

• 434.0 Unit Test the Components

• 435.0 Review the Components

  • 435.1 Code Reviews

• 436.0 Construct Support Documentation

  • 436.1 Create Application Maintenance Manual

  • 436.2 Create User's Manual

  • 436.3 Create Disaster Recovery Plan

  • 436.4 Create Service Level Agreement

• 437.0 Construct Miscellaneous Elements of the Solution

  • 437.1 Construct Testing Environment and Data

  • 437.2 Construct Training Content

  • 437.3 Construct Data Conversion Elements

  • 437.4 Construct Implementation Components

• 438.0 Re-Plan for the Remainder of the Project

• 439.0 Obtain Approval to Proceed

440.0 TEST PHASE

• 440.1 Resolving Bugs

• 440.2 Creating Testing Metrics

• 440.3 Managing the Test Environment

• 440.4 Regression Testing

• 440.5 Automated Testing

• 440.6 Managing Test Cases

• 441.0 Validate Test Coverage

• 442.0 Integration Testing

• 443.0 System Testing

  • 443.1 Performance Testing

  • 443.2 Stress Testing

  • 443.3 Security Testing

  • 443.4 Requirements Testing

  • 443.5 Usability Testing

  • 443.6 Documentation Testing

  • 443.7 Training Testing

  • 443.8 Interface Testing

  • 443.9 Disaster Recovery Testing

  • 443.10 Multiple Site Testing

  • 443.11 Installation Testing

• 444.0 User Acceptance Testing

• 448.0 Re-Plan for the Remainder of the Project

• 449.0 Obtain Approval to Proceed

450.0 IMPLEMENT PHASE

• 451.0 Prepare for Implementation

• 452.0 Perform Training

• 453.0 Convert Data

• 454.0 Implement the Solution

  • 454.1 Pilot Test the Solution

• 455.0 Monitor the Solution

• 456.0 Turnover to Support

• 457.0 Obtain Final Approval

• 459.0 Terminate the Project

460.0 Other Project Lifecycles

• 461.0 Waterfall Lifecycle

• 462.0 Iterative Development Lifecycle

• 463.0 Agile Lifecycle

• 463.0.1 Characteristics of an Agile Project 

• 463.0.2 The Size of an Agile Project

• 463.0.3 Length of the Sprint

• 463.0.4 Estimating Total Duration and Budget

• 463.0.5 Agile Tools

• 463.0.6 Role of the Client

• 463.0.7 Agile Teams

  • 463.0.7.1 Team Rooms

  • 463.0.7.2 Team Roles

• 463.0.8 Build for Today

• 463.1 Sprint 0 - Setup

  • 463.1.1 Gather Initial Requirements Backlog

  • 463.1.2 Establish Initial Technical Architecture

  • 463.1.3 Establish Testing Environment

  • 463.1.4 Establish Production Environment

  • 463.1.5 Conduct Sprint Reflection

• 463.2 Sprint 1 – N

  • 463.2.1 Modify Requirements Backlog

  • 463.2.2 Conduct the Planning Game

  • 463.2.3 Uncover Detailed Requirements

  • 463.2.4 Create Simple Models

  • 463.2.5 Create Initial Test Cases for Each Use Case

  • 463.2.6 Update Architecture and Design

  • 463.2.7 Create / Update Databases

  • 463.2.8 Construct Solution

    • 463.2.8.1 Pair Programming

    • 463.2.8.2 Refactoring

  • 463.2.9 Perform Code Reviews

  • 463.2.10 Perform Unit Tests

  • 463.2.11 Conduct Sprint Testing

    • 463.2.11.1 The Role of a Testing Team

  • 463.2.12 Perform User Training

  • 463.2.13 Move Solution in Production Environment

  • 463.2.14 Conduct Sprint Reflection

• 463.3 Special Work for the Later Sprints

  • 463.3.1 (Sprint N – 2) Integration and Cross Training with Support

  • 463.3.2 (Sprint N) The Planning Game – Final Requirements and Bug Fixes

  • 463.3.3 (Sprint N) Final Data Conversion

  • 463.3.4 (Sprint N) Turnover Solution to Operations and Support

  • 463.3.5 (Post N) Monitor the Solution  

• 463.8 Agile Project Management 

• 463.9 Agile Glossary

• 464.0 Enhancement Lifecycle

• 465.0 Package Selection and Implementation

• 466.0 Customer Relationship Management (CRM)

• 467.0 Software Releases

• 468.0 Research and Development

480.0 Establishing a Reuse Environment

Glossary

Site Map

LifecycleStep Libraries

• Template Library

• Schedule Library

• LifecycleStep eBook

• Flowchart Library

Licenses

• Company Licenses

• Individual Licenses

Terms and Conditions of Use

Product info: project management, project lifecycle, analysis phase, , design phase, lifecycle design, construct phase, test phase, implementation phase, project lifecycle consulting, project lifecycle methodology, Agile