Meetings

Date
Date

Croydon Partnership - SAP Project Phase II

Subject
SAP kick off

Product Owner Meeting Notes

Discusion
Jan & Mark sow concerns abou the projected enddate(October 2004).
The main concerns are the limited time available to develop the desired
solution and the state of the discussion within the PCT around data
protection, consent and the involved data that will be shared.

Action
Organise kick-off meeting for 1/10 (Jan, Mark,
Hubert)
Commence discussions on data issues within
PCT/S.Serviced (Jan, Mark)

HIV plans

The HIV project requires a technical proposal: how to work with eForms Contact Ian Muller to discuss technical
from tablets, using a local datastore (on the tablet) that synchronises
requirements (Hubert)
with a central store when a network connection is available.
Draw up development plan (Hubert)

Additional data load

The data that is loaded into MultiVue needs to be replaced with a most
recent set, which can also be extended with fields that were not loaed
during the first phase.
There is a request to be able to select records using a criterium
'younger then' or 'older then'

IRT

The PCT / Soc.Services have a preference for one central MultiVue

deployment that services SAP, and in the future IRT type solutions. This
is technically cmplex, as the two solutions will dictate very different and
stringent security requirements.

BizTalk 2004

Hubert raises a request to upgrade BizTalk to the latest version, as it will Investigate upgrade possibilities (Jan)
be an easier and better platform to develop against.

page 1 of 9

Include in plan and estimates (Hubert)

286797732.xls

Meetings

Croydon Partnership - SAP Project Phase II

Date
Subject
01 October 2004 Swift demo & review

Swift Care History screens

demo & review
ePex demo & review
MultiVue demo
Explicit agreements on
datafields to be shared

Product Owner Meeting Notes

Discusion
A discussion on the update frequency of data feeds from npoint
systems leads to the conclusion that feeds should be more frequent
then once a day. Swift can run updates more often, ePex needs to be
investigated.
Other notes in the handouts, and incorporated in the updates of the
data definitions.
The design is documented seperately.
General idea is to grow the available historic information by running
multiple uploads of data from Swift/ePex to MultiVue/SAP.
All notes are in the handouts, and have been incorporated in the
updates of the data defnitions.
Request to broadcast changes, e.g. death of a client.
Other remarks are in the action list.
These are recorded in the data definition tables

page 2 of 9

Action
Investigate update frequency from ePex (Jan)

Investigate solution to broadcast changes

(Campbell)

286797732.xls

Decisions

Croydon Partnership - SAP Project Phase II

286797732.xls

Product Owner Decisions

#
1

Raised
01 October 2004

Action
Data for the Care History table will be loaded from 1st of April, 2004

2
3
4
5
6
7
8
9

Page 3 of 9

Owner
Jan/Mark

Commitments

Croydon Partnership - SAP Project Phase II

286797732.xls

Product Owner Commitments

#

Raised

Action

Owner

1
2

20/9/04
20/9/04

Organise kick-off meeting for 1/10

Commence discussions on data issues within PCT/S.Services

20/9/04

4
5
6
7

20/9/04
20/9/04
20/9/04
20/9/04

8
9

1/10/04
1/10/04

Contact Ian Muller to discuss technical requirements for eForms

on a tablet PC
Draw up development plan
Investigate upgrade possibilities for BizTalk to version 2004
Include data reload in plan and estimates
Enable select records using a criterium 'younger then' or 'older
then'
Investigate update frequency from ePex
Investigate solution to broadcast changes e.g. death of a client

10

1/10/04

Search results: add gender

Campbell

Page 4 of 9

Ready by

Complete

Jan, Mark, Hubert

Jan, Mark

Ok
Ok

Hubert

Ok

Hubert
Jan
Hubert
Hubert

Ok
Ok
Close

Jan
Campbell

Ok
Close

Commitments

Croydon Partnership - SAP Project Phase II

Product Owner Commitments

Remark

No longer a requirement
Daily
Broadcast not required but show clearly in
screen

Page 5 of 9

286797732.xls

Risks

Croydon Partnership - SAP Project Phase II

286797732.xls

Risk Log
#

1
2

Raised

Description

Impact

21/10/04 Dependency on third party for completion of Delay of go-live date

network configuration.
10/11/04 Planning of training and go-live is unclear.
Poor user preparation for
use of the system,
impacting on the use of
the system and the
success of the go-live.
10/11/04 Insufficient availability of product owners
due to work pressures.

Delay in decisions,
preparations and
ultimately go-live.

Page 6 of 9

Severity

High
High

Action

Continuous
monitoring
Early
planning and
Preparation

Medium Continuous
monitoring

Owner

Complete

Hubert

No

Mark

Yes

Hubert

No

Project: Project X phase I

IT Team Tasks

27/09 04/10 11/10 18/10 25/10 01/11 08/11 15/11 22/11 29/11 06/12 13/12 20/12 03/01 10/01 17/01 24/01 31/01 07/02 14/02 21/02 28/02 07/03 14/03 21/03 28/03 04/04
days remaining

Number of consultants:
Task description
Requirements
Component
Used for drop
down list
Project
Gathering
box in Requirements
column 'Status'
Formal Requirements Documentation
MultiVue Configuration Component
Append Additional Demographics
SAP Component
Design SAP Database
Creation of the SAP Database
Create stored procedures on SAP database
Creation of SAP .NET Component
Creation of SAP Web Application
Creation of Security Administration Site
Secure Messenging
Security Integration
SAP system testing
SAP System Verification
Bug Fixing / Cosmetic Changes
Install in Live Environment
Go Live Support
General Project Component
Project Management
System Documentation
User Documentation
BizTalk
Component
Used2004
for drop
down
Extend
Adaptor
listboxePEX-3
in column
Extend
Swift Adaptor
'responsible'
Extend Upstream Schemas
Create AIC schema
Create Mappings
Create SAP AIC
Unit Testing
Integration Documentation

1.5

Responsible
Status
7 days
In progress
Campbell
In progress
This number is used to
Campbell calculate the 'ideal
In progress
line'
2 days
started
in the burndownNot
chart.
Campbell
Completed
60 days
In progress
Campbell
Completed
Campbell
Completed
Campbell
Completed
Campbell
Completed
Campbell
Completed
Campbell
Completed
Campbell
Completed
Campbell
Completed
Campbell
Completed
Campbell
In progress
Campbell
In progress
Campbell
In progress
Campbell
Not started
25 days
In progress
Hubert
In progress
Campbell
Not started
Campbell
Not started
31 days
Not started
Campbell
In progress
Campbell
Completed
Campbell
Completed
Campbell
Completed
Campbell
In progress
Campbell
Completed
Campbell
Completed
Campbell
Not started

05/04

125

116

107

97

89

87

81

75

73

71

69

62

60

44

44

42

42

36

30

11

16

21

26

31

36

41

46

51

56

61

68

73

78

83

90

97

104

111

118

125

132

139

146

153

154

125.0 117.5 110.0 102.5

95.0

87.5

80.0

72.5

65.0

57.5

50.0

42.5

35.0

24.5

17.0

9.5

2.0

-8.5

-19.0

-29.5

-40.0

-50.5

-61.0

-71.5

-82.0

1000

928

852

776

708

696

644

596

584

564

552

492

480

352

348

336

332

288

240

32
24

24
24

24
24

24
24

24
24

24
24

24
24

24
24

16
16

16
16

16
16

16
16

8
16

8
8

8
8

8
8

8
8

8
8

8
8

16

16

16

16

16

16

16

16

16
24
40
104
64
40
40
24
40
16
40
16
16

16
24
40
64
64
32
32
16
40
16
40
16
16

number
16 calculated
16
16
16 of
worked days in the
sprint
12
12
8
4
0
24
12
12
12
8
32
20
20
20
12
40
32
8
8
0
Calculated
64
52 number
52
48
24
ofwork
days
24
16 left0 in the
sprint. Used to draw the
24 line'
16
0
'ideal
8
0
0
40
40
40
40
40
16
16
16
16
16
40
40
40
40
40
16
16
16
16
16
16
16
16
16
16

8
0

32
16
40
16
16

32
32
40
16
16

My burndown sheet
updates became a
weekly exercise. The
chart now shows spikes.
For customer
presentation purposes I
hide empty columns in
24
24
24 that24
this worksheet,
32
32
32
makes32
the graph
smooth.
32
24
24
24
16
16
16
16
16
16
16
16

16
16
16
16
16

16
16
16
16
16

16
16
16
16
16

16
16
16
16
16

8
16
16
8
16

0
8
16
4
16

144
24
32

144
24
32

128
24
32

120
24
32

112
24
32

108
24
32

104
24
32

100
24
32

96
24
32

92
24
32

88
24
32

84
24
32

80
24
32

72
24
32

68
24
32

64
16
32

60
16
32

56
16
32

52
16
32

40
40
8
8
24
64
40
24

40
40
8
8
24
64
40
24

40
40
8
8
24
64
40
24

40
40
8
8
24
64
40
24

40
40
8
8
24
64
40
24

40
40
8
8
24
64
40
24

40
40
8
8
24
64
40
24

40
40
8
8
24
64
40
24

40
40
8
8
24
64
40
24

40
40
8
8
24
64
40
24

40
40
8
8
24
64
40
24

32
40
8
8
16
24
40
24

32
40
8
8
16
24
40
24

16
0
8
0
8
16
40
40

16
0
8
0
8
16
40
40

16

16

16

8
16
40
40

8
16
40
40

8
8
32
40

16

8
0
24
40

-92.5 -103.0 -104.5

0

Product Owner Tasks

Task description
Design tasks
Data mapping: Swift to SAP
Data mapping: ePex to SAP
Data mapping: Care History to SAP
Training preparation
Agree scheduling with Project Board
Prepare trainer materials
Prepare handouts

27/09 04/10 11/10 18/10 25/10 01/11 08/11 15/11 22/11 29/11 06/12 13/12 20/12 03/01 10/01 17/01 24/01 31/01 07/02 14/02 21/02 28/02 07/03 14/03 21/03 28/03 04/04
Responsible
Mark
Jan
Jan/Mark

Status
In progress
Completed
Completed
Completed

Jan/Mark

In progress
In progress

Jan/Mark
Jan/Mark

In progress
In progress
In progress

Mark

In progress
In progress

Prepare exercises
Prepare training data
Run trial training
Appoint trainers
Complete training schedule
Schedule dates early to avoid clashes
Determine group size
Determine format and duration of hands-on session
Network Configuration
Design network structure
Order components
Issue installation requests to service providers
Monitor completion of installation
Test network components
Test end-to-end services
Test SAP application over the network
Go-live preparation
Agree dates with Project Board
Design vetting process
Distribute user authorisations
Add input of user secrets to training
Train and prepare support staff
Update existing support processes
User acceptance testing
Data loadng

Mark

Mon

Mon

Mon

Mon

Mon

Mon

This customer didn't

track work left for the
product owners. It
would require a second
burndown chart.

Mon

Mon

Mon

Mon

Mon

Mon

Mon

Mon

Mon

Mon

Mon

Mon

Mon

Mon

Mon

Mon

Mon

Mon

Mon

Mon

Mon

05/04
Tue

Remaining work (days) for project X phase Y

140

This is the difference

between 'ideal' velocity
and
the actual velocity.
In this example the work
came to a halt in
November and January,
causing the delay.

120

Working days

100

80

60

40

20

0
27/09 04/10 11/10 18/10 25/10 01/11 08/11 15/11 22/11 29/11 06/12 13/12 20/12 27/12 03/01 10/01 17/01 24/01
Date