Nick Small, Shawn Boughey, Karolina Latkoska

SPQM / SEP

1

Nick Small, Shawn Boughey, Karolina Latkoska

What?

Project Planning

• Project Charter

• Project Management Plan

• Risk Mgt Plan

• Change Mgt Plan

• Project Quality Plan

• Communication Plan

• Configuration Plan

• Project Closure Document

Requirements Analysis

• Use Case Diagram

• Use Case Narratives

• SSDs

• DFDs

• Domain Diagram

Design• Functional

Specifications

• System Architecture

• Database Design Specification

• Data Migration Strategy

• GUI Specification

2

Complete

In Progress

Legend

Nick Small, Shawn Boughey, Karolina Latkoska

When?

3

Nick Small, Shawn Boughey, Karolina Latkoska

Risks

• Limited time

• Unclear requirements

• Inability to convey requirements

• Reduced team

Changes

• Reduced team

Issues

• Reduced team

4

Nick Small, Shawn Boughey, Karolina Latkoska

What are we doing about it?Option 1 (1)

5

• Revisit project tasks and schedule• Reassign deliverables across the team

Nick Small, Shawn Boughey, Karolina Latkoska

Option 1 (2)

6

Project Planning

• Project Charter

• Project Management Plan

• Risk Mgt Plan

• Change Mgt Plan

• Project Quality Plan

• Communication Plan

• Configuration Plan

• Project Closure Document

Requirements Analysis

• Use Case Diagram

• Use Case Narratives

• SSDs

• DFDs

• Domain Diagram

Design• Functional

Specifications

• System Architecture

• Database Design Specification

• Data Migration Strategy

• GUI Specification

Karolina

NickShawn

Karolina

Nick

Shawn

Nick Small, Shawn Boughey, Karolina Latkoska

Option 1 (3)

7

Planning, Requirements,

and Design

KarolinaPMP

Quality PlanChange PlanConfig PlanDB Design

NickRisk Plan

UML ModelsIssues RegisterData Migration

ShawnRequirements

ModellingSystem

RequirementsFunctional Specs

ArchitectureGUI

Nick Small, Shawn Boughey, Karolina Latkoska

Option 1 (4)

8

Face to Face •~3 hr/pp/pw•Client questions, discussion and clarification, of issues, action items, task allocation, presenting to client

Online •~2 hr/pp/pw•Monitoring changes, team communications, client questions

Individual •~8 hr/pp/pw•Writing deliverable documents, reviewing documents from team members

Nick Small, Shawn Boughey, Karolina Latkoska

What are we doing about it?Option 2

9

• Reduce scope

Nick Small, Shawn Boughey, Karolina Latkoska

Data Migration

10

•Consult on importance of database fields•Characterise, quantify data problems•Examine feasibility of correcting data problemsAnalysis

•Develop and agree on migration acceptance criteria and tests•Agree on new platform architecture•Develop code for data extraction and testing•Develop plan for freezing data structures during migrationDesign•Freeze data structures•Migrate data to new platform•Run quality and acceptance testing•Activate interfaces on new database otherwise rollback

Deployment

http://wikibon.org/?c=wiki&m=v&title=Data_migration_strategies

Nick Small, Shawn Boughey, Karolina Latkoska

Data Migration - analysis

11

Field Importance Reliability

Business Significance Characteristics Issues

Address Medium Low Useful for postal correspondence (e.g. reminders, promotions)

Almost all rows have valuesMix of upper and lower case Unicode charactersNumbersSome superscript charactersA number of special characters

4 empty rowsMost rows appear to contain foreign addresses

Phone High Low Needed for contacting customers to advise on progress with workUseful for contacting clients for inspection reminders

Almost all rows have valuesAll values are numbers, hyphens, full-stops or parenthesesNo letters

Some empty rowsMixed formatting in the form of use of hyphens, full-stops and parenthesesWhat appear to be ISD country codes do not correspond reliably to values in Address, City, Region or NewPCode