Software Development Readiness

From MIKE2 Methodology

Contents 1 Activity: Software Development Readiness 1.1 Objective 1.2 Major Deliverables 1.3 Tasks 1.3.1 Establish or Upgrade Development Environment as Necessary 1.3.2 Establish Configuration Management Baseline 1.3.3 Send Staff to Vendor Training Classes 1.4 Core Supporting Assets 1.5 Yellow Flags 1.6 Key Resource Requirements

Activity: Software Development Readiness

Objective

The Software Development Readiness activity ensures that the environment is suitable for this increment of the project implementation. This activity includes three tasks - one which is completed relatively quickly, and two of which are ongoing. In the first task, the configuration management environment is set up, so that code and other artefacts can be checked in when they are completed. The second, ongoing task involves making sure that the developers have a workable development environment. The third task is to guarantee that developers are trained in the tools that will be used to build the system. To some extent, this activity may have been addressed at an earlier point in the project because some of the necessary architecture may have already existed, including software. Procurement processes may be associated with this task.

Major Deliverables

• Upgraded Development Environment
• Configuration Management Baseline
• Staff is sent to vendor training courses

Tasks

Establish or Upgrade Development Environment as Necessary

Objective:

This task consists of completing the implementation of hardware and software needed by the developers that began in Phase 2. This is an ongoing infrastructure task. Once the development platforms are in place, this task will reactivate as necessary, usually at the beginning of a development cycle.

Input:

• SDLC Procedures
• Testing Strategy
• Development and Testing Environment
• Infrastructure Dependencies
• Design Dependencies

Output:

• Upgraded Development Environment

Establish Configuration Management Baseline

Objective:

The baseline for configuration management includes ensuring the development team has the correct versions of source code, vendor products, files for compilation and linkage, procedures for check-in, check-out and the capability to conduct development in a fashion that won’t impact others. Some training may be necessary.

Input:

• Testing Strategy
• SDLC Procedures
• Upgraded Development Environment

Output:

• Configuration Management Baseline

Send Staff to Vendor Training Classes

Objective:

The purpose of training is to save time and money (over the long-term) whilst mitigating risk and improving quality. In order for it to achieve this purpose, it must be focused and timely. Focus is achieved through consultation with each individual developer and timeliness is achieved through planning. Individual developer training plans may need to be constructed as an output to the skill set review conducted in Phase 1.

Input:

• Findings on People, Organisation and its Capabilities
• Technical Risks & Constraints
• Risk Management Plan
• Detailed Project Plan

Output:

• Individual Training Plans
• Schedule for Group Classes

Core Supporting Assets

Yellow Flags

• Staff receiving training will need to go through stepwise changes in skills development, i.e. most staff haven’t worked with similar technologies on previous projects

Key Resource Requirements

• Infrastructure Manager
• Infrastructure Developer
• Test Manager