All projects are governed by a Process Bible, which is part of the Project Initiation Document (PID).
This documents forms the backbone which provides the project management framework for structure, process and documentation relating to each project.
A typical Process Bible will address the following issues and more as needed.
Description of the Project
- Services
- Phases
- Deliverables
- Team Structure
- Acceptance Criteria
- Release Approval Process
- Release Dates
- Not in Scope
- Approach
- Software Design Methodology
- Software Development Methodology
- Permissible exclusion
- Templates / Samples
- Daily/Periodic Builds
- Umbrella Activities
- Work Estimation
- Project Tracking & Control
- Project Review Meetings , levels and frequency of Software Quality Assurance
- Software Testing Methodology
- Special/Critical Requirements (if any)
- Software Configuration Management
- Configuration Items
- VSS Hierarchy
- Releases & Builds
- Risk Management
- Formal Technical Reviews
- Code Review
- Design/Architecture Review
- Measurement
- Feedback and Frequency
- Other Project Management Activities
- Change Management
- Issues Tracking
- Communication & Reporting
- Tools Used
- Standards
- Other Resources Used in the Project
- Client Property Used in the Project
Further explanation of some areas is given below:
Typical Services Content:
- Application Definition and Requirements Specifications
- Design Technical and Data Architecture
- Document Program Specification
- UI Design / Prototyping
- Development
- Testing (Unit, Functional, System, Stress, Performance etc)
- UAT Support
- Stubs for Help
- Initial Data Upload (i.e. migration)
- Release Documents (including deployment instructions)
Phases may include:
- Design Phase.
- Development/Implementation Phase.
- Testing Phase.
Project Plan:
A Master project plan is created. Typically as $/Projects/Category/Planning/Client Development Plan.mpp
Releases & Builds:
- Two different types of builds are prepared:
- Internal builds - are prepared for testing by the QA people of the team.
- External builds - are sent to the client after a complete testing cycle has been executed by the QA team.
- External builds and releases are specifically marked in the VSS so that support to an older version can be provided if requested by the client.
Deliverables:
A complete detailed report is agreed upon and followed strictly.
|
