NF’s Technology Project Management SOP - noolahamfoundation/guiding-documents GitHub Wiki
Title | NF’s Technology Project Management SOP |
Document Type | Standard Operating Procedure |
Security Classification | Technology, RB |
Department | NF Technology |
Author (s) | Natkeeran L. Kanthan |
Approval | |
Version | Version 1 - Feb 2015 |
The purpose of this document is to outline the project management workflow for primarily technical projects.
This document is intended for RB, Management and the Technology Team.
- Noolaham’s Project Life Cycle
Any software development
Anything that needs significant input from the Technology Department
multiple steps
Establishing the Business Requirement (Needs to be Approved by RB)
- Business Requirements Document
- Background
- High Level Use Cases
- Background
- Problem Description and Scope
- Noolaham Objectives addressed by this project
- Stakeholders
- Designated User Communities
- Project Sponsors (Internal or External)
- Project Manager - External to Technical Team
- Technical resources
- Budget (Has a budget been allocated or requested for this project? What is a maximum amount that can be *allocated to this project)
- Scheduling (When do we need this project completed by?)
- Resource Allocation
- Technical resources
- Management / staff resources
- Equipment and devices
- Facility if any required
- User Acceptance Testing
- Software Requirements Specifications Document
- Functional Requirements
- Overview
- Major Features
- Design Goals
- Use Cases / Scenarios
- Non Goals
- Storyboard / Flow Chart
- Screen by Screen Specifications
- Open Issues
- Non Functional Requirements (Operational, Deployment, Build)
- Maintenance
- Functional Requirements
Design (Needs to be Approved by Technology)
- Design Options
- Design
- Package design
- Class design?
Testing (Needs to be Approved by Technology)
Deployment (Needs to be RB)
Maintenance
Documentation
- Technical
- User
https://docs.google.com/document/d/1k5PGqbjZ4_XaU2I0U9AUPf5AvXC4wNKCSDwqwBFv4Eo/edit?usp=sharing