Managing Business Analytics Projects

Workshop Day 3
Workshop Instructions:

1. Submission deadline: 11:59pm 15 Apr 2023. Late submissions will not be graded.
2. All documents submitted must be in MS Office or PDF format.
3. Clearly list your Breakout Room (BOR) Number followed by your registered full name.
4. The following naming convention must be used for your submission:
“T[X] MBAP Day 3”
5. This doc is for your use only, do not circulate this in any way or form.

Team Name
Group 6
Team Members
Deston Chung Eng Kea (A0166940Y)
Leong Keng Whye (A0269738H)
Mao Yu Qi (A0172700R)
Sun Jiahui (A0091667U)

Zhong Yonghui (A0091647X)

MBAP Workshop Day 3 V3.14 Page 1 of

© NUS-ISS. All rights reserved.
 Table of Contents

A. Managing Risk for the Customer Analytics System......................................................................3

B. Determine the Launch Date of the Customer Analytics System..................................................4
C. Tracking the Project Progress of the Customer Analytics System................................................6
APPENDIX A.........................................................................................................................................10

MBAP Workshop Day 3 V3.14 Page 2 of

© NUS-ISS. All rights reserved.
A. Managing Risk for the Customer Analytics System
1) Indicate the scale used for measuring the “Impact” and the “Probability”
2) Use the Risk Exposure method to assess & prioritize the top three (3) risk items for the CAS.
3) Develop the appropriate mitigation actions for each of the identified risk item.

Impact Probability
Risk - Short (1 to 3, 1 is (1 to 3, 1 is Risk
Risk ID Risk Description Mitigation
Name low, 3 is low, 3 is Exposure
high) high)

RSK001 Fit with CAS cannot serve its intended
existing purpose if it cannot be integrated
architecture with SEPL’s existing systems (i.e.
email, ecommerce web engine,
customer history system,
inventory system)
3 2
6 Conduct proper discussion with the IT
team to ensure the chosen solution can
be integrated with all existing systems,
and if possible also with foreseeable
systems that customer data would be
analyzed with in the future.

RSK002 Short Project Based on feasibility report, 4 1 3 3 Perform prioritization of project scope to
Timeline months to complete whole deliver MVP (with most critical features)
project is risky without any buffer within 4 months, and put 5th month as
continuous improvement

Regular review the progress with key

stacker holders and keep time to market

RSK003 Budget The budget is set at $500k. 1 3 3 The budget needs to be planned and
However, based on the past controlled properly and monitored

MBAP Workshop Day 3 V3.14 Page 3 of 14

© NUS-ISS. All rights reserved.
 overrun projects, there may be some consistently, but we need to be prepared
overspend. in case there is a budget overrun by
preparing a contingency plan. Confirm
project requirements and prioritize the
most critical features that need to be
and can be built within the $500k
budget.

MBAP Workshop Day 3 V3.14 Page 4 of 14

© NUS-ISS. All rights reserved.
B. Determine the Launch Date of the Customer Analytics
System

Please use the following project information to answer Question B.

You are the Project Manager of the SEPL Customer Analytics System (CAS). The official start
date of this project is 1 Feb 2022.

You had estimated that your team could deliver an average velocity of 19 story points per
iteration. Each iteration has a duration of two (2) calendar weeks.
An additional pre-launch iteration should be included to perform system “hardening” and
launch preparation.
Table 1 is the product backlog. It can be found in Appendix A. It provides the list of the user
stories and their associated story points required to launch the CAS.

Based on the above considerations, you are to:

1) Develop a planned burn down chart for this project.
2) Determine the total duration required (in terms of weeks) in order to launch the CAS.
3) Determine the CAS launch date.
Please indicate all calculations and assumptions on the solution page.
Sample Solution Template

MBAP Workshop Day 3 V3.14 Page 5 of

© NUS-ISS. All rights reserved.
The Solution Page for:

(B) Determine the Launch Date of the CAS, draw your planned burn down
chart here and show all calculations & assumptions.

Total duration required (weeks): 22 weeks from 01-Feb-2022

Total duration required (iterations): 11 (including pre-production iteration)

Launch Date: 05-Jul-2022

Link to doc for more calculations and workings: Link

MBAP Workshop Day 3 V3.14 Page 6 of

© NUS-ISS. All rights reserved.
C. Tracking the Project Progress of the Customer Analytics
System
Your team is responsible to develop and launch the CAS. It includes the following analytical
models and implementation scenarios:

1. Digitize the manual and paper-based Customer History Purchase Program.

2. Identification of micro-segments based on customer demographics & psychographics.
3. Recommendation of products based on the identified customer microsegments.
4. Implementation Scenarios include integrate the outcomes from the Recommendation
Engine with the:
4a) Email system to send electronic direct mailers to the customer
4b) On-line ecommerce website engine
4c-1) Manual report to allow the store manager to confirm the availability of the
product against the physical in-store inventory
4c-2) In-store inventory of next closest physical store that the choice of product
available that could be reserved, purchased and delivered directly to the
customer’s home address
4c-3) In-store inventory system (pending separate budget and implementation)
5. Build an interface and integrate the outcomes of the Recommendation Engine to filter
product titles based on the special promotion campaigns (by micro-segments) in order
for the store manager to make specific recommendations to the identified customer.
After 3 iterations, the performance of your team is reflected in Table 1 – Product Backlog.
It shows that your average team velocity is lower when compared with the original
estimated team velocity of 19.

The management of SEPL accepted the launch date of the CAS determined earlier by you
and your team (Question B). This launch date is final and cannot be changed.

Please answer the following:

1) Draw your planned Burn Down Chart. (Hint: Reproduce from Question B.)
2) To-date, you have completed three (3) iterations. Use the inputs from Table 1 – Product
Backlog to map the progress of your project (up to 3 iterations) on this Burn Down Chart
3) From this point (after the end of the 3rd iteration), determine how many extra iterations
will be required to deliver the CAS.
4) Draw the new forecast (planned) burn down line and clearly indicate the required
number of extra iterations on your Burn Down Chart.
5) Determine the specific user stories and their associated story points you will remove
from the Product Backlog. Provide your justifications for their removal.
6) With the reduced number of story points, updated your forecast (planned) Burn Down
line in your chart to reflect that you will be able to meet the launch date.

MBAP Workshop Day 3 V3.14 Page 7 of

© NUS-ISS. All rights reserved.
 Solution Template:

MBAP Workshop Day 3 V3.14 Page 8 of

© NUS-ISS. All rights reserved.
The Solution Page for:

(C) Tracking the Project Progress of the CAS, provide your justifications
here.

Average Velocity: 10
Number of Extra Iterations: 9
Total Iterations: 20 (inclusive of 3 completed iteration and pre-production iteration)
Total Iterations to be reduced: 9
Duration of Each iteration: 2 elapsed weeks (Velocity of 10 story points per iteration)
Original Planned Launched date: 5 July 2022

5. Stories to be dropped

We need to drop 90 story points. We will shortlist from the stories that have not started
development in the first 3 iterations, i.e. S/N 3.2 to 6.0.

Will be keeping S/N 1.0 to 4.1.

Reasons:

1. 1.0 to 3.1 has already begun development

2. 3.2 is related to the scoring engine for the recommendation system. This is
important to keep because it directly affects the order that recommendations are
presented to customers, and thus is directly related with the recommendations
relevancy and effectiveness.
3. 4.0 and 4.1 is important to keep because it is directly related to SEPL’s online
presence. 4.0 involves integrating recommendations with the email system, which
can increase SEPL’s online reach and help boost sales. 4.1 involves integrating the
recommendations with SEPL’s ecommerce engine. This is important because it will

MBAP Workshop Day 3 V3.14 Page 9 of

© NUS-ISS. All rights reserved.
 make customer’s online experience better by showing relevant products and also
boost sales.
a. These two were kept because it is directly related to SEPL’s online presence
and competitive advantage.
4. Items from 4.2 onwards are related to automating reports, physical stores and also
the in-store inventory system.
a. Items related to integration with in-store inventory can be deprioritized for
now because the inventory system is still pending a separate budget and
implementation.
b. For items relating to the integration with physical stores, this was chosen to
be dropped because the priority currently is SEPL’s online presence,
especially since we are facing fierce competition in the online space and also
the industry landscape has changed to a greater focus on internal and digital
distribution.
c. For automated reports, this was also chosen to be dropped because this is
more of a quality of life requirement, but there are still slower manual
alternatives that can be done until the next release.

Dropped Item from 4.2 onwards comprise of 90 story points.

MBAP Workshop Day 3 V3.14 Page 10 of

© NUS-ISS. All rights reserved.
 APPENDIX A

MBAP Workshop Day 3 V3.14 Page 11 of

© NUS-ISS. All rights reserved.
TABLE 1 – PRODUCT BACKLOG

Iterations
Story
S/N User Story
Points
1 2 3 … … 20

1.0 As the Implementation Developer, 20 15 12 5

I must develop a user interface to
allow the data entry user to key in
data of Customer History Purchase
System into an online repository.

2.0 As the data scientist, I can develop 8 7 7 5

the model for the Micro-
segmentation model using a
maximum of 10 raw and 10 derived
variables (use existing datasets).

2.1 As the ETL developer, I have to 15 14 13 13

create the derived variables based
on the Micro-segmentation model
provided.

2.2 As the Implementation developer, I 2 2 1 1

have to develop the scoring engine
based on the Micro-segmentation
model provided.

3.0 As the data scientist, I can develop 8 7 7 6

the model for the
Recommendation model using a
maximum of 10 raw and 10 derived
variables (use existing datasets)

3.1 As the ETL developer, I have to 15 14 10 8

create the derived variables based
on the Recommendation model.

3.2 As the Implementation developer, I 2 2 2 2

have to develop the scoring engine
based on the Recommendation
model provided.

4.0 Implementation Scenario 4a): 10 10 10 10

As the Implementation Developer,
I have to develop an interface to
the Email system to integrate and

MBAP Workshop Day 3 V3.14 Page 12 of

© NUS-ISS. All rights reserved.
 automate the sending of the
Recommendation Engine outcomes
via electronic direct mailers to the
identified customers.

4.1 Implementation Scenario 4b): 20 20 20 20

As the Implementation Developer,
I have to develop an interface to
integrate the Recommendation
Engine outcomes with the
ecommerce website engine for the
identified on-line customer.

4.2 Implementation Scenario 4c-1): 8 8 8 8

As the Implementation Developer,
I have to develop an report to
allow the store manager to check
the Recommendation outcomes
with the physical in-store inventory
to enable the identified customer
is to reserve and purchase the
product of choice in the store.

4.3 Implementation Scenario 4c-2): 15 15 15 15

As the Implementation Developer,
I have to develop an interface to
integrate the Recommendation
outcomes with the in-store
inventory of next physical store
that has the product of choice
available to enable the identified
customer to reserve, purchase and
have the product delivered directly
to the customer’s home address.

4.4 Implementation Scenario 4c-3): 20 20 20 20

As the Implementation Developer,
I have to develop an interface to
integrate the Recommendation
outcomes with the automated in-
store inventory system (pending
implementation).

5.0 As the Report Developer, I have to 18 18 18 18

build 6 pre-defined or system
generated reports for the following

MBAP Workshop Day 3 V3.14 Page 13 of

© NUS-ISS. All rights reserved.
 product backlog: #2.2; #3.2; #4.0;
#4.1; #4.2 and #4.3

5.1 As the Report Developer, I have to 9 9 9 9

build 3 ad-hoc reports using 10 raw
variables and 10 derived variables.

6.0 As the Implementation Developer, 20 20 20 20

I have to build an interface and
integrate the outcomes of the
Recommendation Engine to filter
product titles based on the special
promotion campaigns (by micro-
segments) in order for the store
manager to make specific
recommendations to the identified
customer.

Total: 190 181 172 160

MBAP Workshop Day 3 V3.14 Page 14 of

© NUS-ISS. All rights reserved.