Background And Assumptions

1

Software development project

EXAMPLE

Dr. Vita Akstinaite

2

Background & Assumptions

▪ Describe your Project Background here

▪ List your project Assumptions

3

(VA: in the next few slides please explain your project approach; the

one in the example does not necessarily means that it works for your

project!)

Overall Project Approach

4

INITIATION ANALYSIS &

DESIGN LAUNCH / RELEASE SUPPORTDELIVERY CLOSE

Example of a Project Approach

5INITIATION

Project Board

• Simon Peters (Director)

• TBC (Company/Client)

• TBC (client)

• TBC (service provider)

Technical

• Technical Lead

• Lead/Senior Developer(s)

• Developer(s)

• Consultant(s)

• Tester(s)/QA(s)

Adoption and change

• BA

Oversight

• Vita Akstinaite (Delivery)

• TBC (Technical)

Project Management

Additional resource

• BA

• Architect

• Designer

• Infrastructure

• Testing Lead

• Support

6ANALYSIS & DESIGN

▪ Explain your requirements here:

▪ Functional requirements (i.e., hardware, software)

▪ Non-functional requirements (i.e., user experience)

▪ Visual design (i.e., how the app is going to look like?)

 

 

7

Deliverables (Example)

Stage/Schedule Deliverable Acceptance criteria

Test, Deploy & Extended Support

Services

Systems Manual

The systems manual is a comprehensive document that

describes in detail the information and activities required to

ensure the system can be supported and managed on an

ongoing basis. The systems manual must include:

1. inventory of system components 2. installation instructions

3. configuration documentation 4. interface and batch jobs

5. release notes 6. backup and disaster recovery plan

Summarise here what are you going to deliver? The app itself, probably some support

for the app too? What about Help Desk? Additional services?

8DELIVERY

▪ Iterations

▪ Product backlog

▪ Reviews

▪ Testing

Analysis

Design

ImplementationTesting

Requirements

Deployment

Planning

9

Proposed timeline

▪ Example of how your plan could look like – change to what works for your plan and list all your activities

Month May’19 Jun’19 Jul’19 Aug’19 Sep’19 Oct’19 Nov’19

Initiation

Analysis and Design

Iterative development

UAT

Infrastructure

Migration

Training

Support (TBA)

Discover

Deploy

Strategy

Kick-off

Reviews

Go live sign-off

Deliver: Development Iteration Cycles

Test

MigratePrepare

Basic Advanced

Set Up

 

 

10

Billing

Activity Cost / Billing milestone

Initiation

$300,000 (to be split accordingly)

Discovery and Design

Development iterations

Testing (UAT)

Training

Support

Enhancements

Activity Cost / Billing milestone

Project kick off (payment upfront) 25 %

Deploying to UAT/Production 50 %

Project Closure 25 %

Explain here how you are going to charge your client, when and what sums

 

 

11

Monitor: Project Status

Jun July Aug Status

12. 19. 26. 02. 09. 16. 23. 02. 09. 16. 23. 30.

• Finalise documentation

• Acute flags (LTC) – confirm/customise

• Testing

Activity

• Build GP data load process for EMIS • Receive pseudonomysed EMIS data

• Hammersmith data

• Key events

Go live

Kick-off

Weekly meetings Milestones Achieved

Responsibility

Laura

• Develop LTC/QoF process (SystemOne) Matt

26.01

04.02

Matt

Matt

• EMIS/System One integration TBC

• Build referrals data

• Build A&E data feed

• Build Social Care data feed

• Costing for Primary Care & Social Care

• Amending costing algorithms for MH, CIDS, SUS data feeds

Matt

• Reporting tables

TBC

TBC

TBC

TBC

TBC

Simon

Simon

• Adding security layers for Tableau views TBC

TBC

• Environments set up (TBC) TBC

30.03

.20.03

• Deploy + Data load at SECSU Laura

TBC

Ready to go/

In progress

At

Risk

On

hold

Deploy

TBC

UAT

TBC

• Population segmentation Matt 20.02

• Load received System One data

TBC

TBC

TBC

04.02

19.02

• Build incremental load process for SystmOne

TBC TBC

TBC

TBC

06. 13. 20. 27.

Sep

24.02

• Showing Dr Tahir’s data TBC

TBC

TBC

TBC

UAT

DeployGo live

Explain how you are monitoring the progress visually!

12

Commercial control

FINANCIALS Budget Actuals To Date Forecasts

Commercial Basis Fixed price. Budget at Complete

$k

Actual Cost

$k

Percent

Complete

Estimate To

Complete

$k

Estimate At

Complete

$k

Budget

Variance $k

Forecast

Finish Date

300.00 20.0 7% 280.00 300.00 0.00 15/11/19

Explain how you are you tracking your costs.

13LAUNCH / RELEASE

▪ Explain how you are going to Launch your app? Will you provide any training or post-launch support?

14SUPPORT

▪ Do you support go-live and post go-live issues?

▪ Hosting environments?

▪ Support – 1st, 2nd, 3rd line?

▪ Operational improvements

▪ Additions to the app

15CLOSE

What will be the process of closing your project?

▪ Client sign off

▪ Handover to support (if agreed)

▪ Final reports, closure in systems

▪ Final invoicing / Finance team

16

Ensuring project success

List here your project success factors. What will make this project work? For example:

▪ Ensuring involvement and alignment from all stakeholders

▪ Timely feedback

▪ Relevant workshops / meetings / reviews

▪ Monitoring risks

▪ Process for dealing with change

17 Anything else you want to add about your project

▪