No

What to do?

Example/Experience

Remarks

1

Project objective is identified

• Usually is stated by client during demo whether they need or not the bank recon automation

• This applet should speed up the bank recon (mgt report) process monthly

BI  Features - BI - Feature List  

2

An appropriate response to the objective is documented  in a business case with recommended solution options

• All requirements from the demo / meet up with clients is written in Minute of Meeting (MOM) 

• MOM should be properly dated and summarised which will be referenced when doing Planning Stage

https://drive.google.com/drive/u/0/folders/1x6LbZ2AW8856jxEYa7-tbJLtJjaur6AY  

3

Investigate whether each option addresses the project objective 

• N/A 

4

Final recommended solution is determined

• It is BI

5

“Can we do the project?” is discussed

• Yes because BI is a product now

6

“Should we do the project?” is discussed

• Yes because Bank Recon Applet is a product now

• Quotation is signed from customer (acknowledged)

How to create Issues: /wiki/spaces/WPMO/pages/2177827263  

7

Major deliverables and the participating work groups are identified

• Communicate with tech lead (For BI, please liaise with MIS Head (Arri))

• Find out the resources names in the org chart and see JIRA Master List for their current targets and fit where is ‘idle’

• From quotation  -Identify these:

  • How many Author & Reader access

  • What type of report (which category)

Org Chart - https://docs.google.com/drawings/d/15UzFEoS4Jv2ry5toOC6jrwVzWxOrucfzt6PhEG9obMc/edit  

JIRA BLG Project List - https://wavelet.atlassian.net/secure/PortfolioPlanView.jspa?id=73&sid=73&vid=47#plan/backlog 

No

What to do?

Example

Remarks

1

The project’s tasks is identified

• Identify the Report category needed (in quotation will state, if no state, need to liaise with Client confirming number of reports and what is it)

• Identify the SQL query

• Identify the fields needed for such report

• Identify the BLG server access for that Client & Connect

• Open new Quicksight account for the client

• Identify  ETL job

• Permission Set - Upon giving author and reader access

• Currently we can produce Sales, Purchase, Stock Report

2

Send upfront billing instruction to Finance 

• According to Payment Plan agreed in the quotation, issue XX% of upfront payment

3

Resource requirements are identified

• If full time programmers - Do scorecard target for identified FE and BE programmer

• If part time programmers/ freelancers - Do their BRD and ask finance to raise PO

• If freelancer under EP status - Make sure they logwork

• If interns - Set targets until their internship ends day (make sure they can commit to it)

• Set meeting with programmers on above targets (involve HR)

• Request HR for their scorecard access

BRD: 

4

Outlining the activities, tasks, dependencies

• Prepare advanced JIRA roadmap 

• How to set the Front End issue? 

  • It is based on the moqup screen such as Create Detail, Edit Details, Edit Upload Stmt, Edit Manual Matching etc

• How to set the Back End issue? 

  • Need to identify which part require API

  • to identify which API, you will need to discuss with Norizan & VL first

  • a meeting will be great (together with identified Backend programmer),

  • upon meeting ended, you should be able to list down API needed and create the issue accordingly

• How to set ETL issues 

  • Stated in the link >>

BI TMT and Clicknet Plan - https://wavelet.atlassian.net/secure/PortfolioPlanView.jspa?id=159&sid=173#plan/backlog 

5

Timeframe is prepared

• Due date for technical job, get confirmation from VL/Norizan/Hassan/SB/Arri to best estimate

• For bank stmt new API - usually takes 1 week

• For cashbook new format API - usually takes 1.5 week (include development, code review, test phase)

6

List possible threats

• Interns available date 

• Staff may take sick leaves/AL

• Factor public holiday esp if there is seasonal holiday (Raya, CNY, etc)

• Code review queue 

• Programmers may be doing multiple projects at the same time 

• New programmers lack of skills
  

7

Providing quality targets

• Avoid edit due date, make sure programmers can commit to the due date

• Need FREQUENT follow up with them, they tend to not follow the due date so need to remind them WEEKLY

8

Document a quality plan

• All initial requirements and quotations is saved, captured and recorded

• If along the way, got ‘enhancement’ identified, need to make new quotation on that

  • New enhancement means things that are not within current bank recon applet yet

9

Identify control measures

• Usually set up meeting with VL to speed up programmers (VL will explain to them on how to do it and what tables to be created etc) because problem usually is coming from lack of surety on next step

No

What to do?

Example

Remarks

1

Maintain control and communicate

• Follow up every week on api progress

• Have bi-weekly meeting update

2

Progress is continuously monitored 

3

Appropriate adjustments are made recorded as variances from the original plan

• PM needs to monitor the due date, if due date is nearing but job is still haven't started, COMMUNICATE

• Identify what goes wrong and maybe need to re-adjust the due date 

4

Progress information is being reported through regular team meetings

5

Team should record variations from the original plan  and publish modifications to the plan

• Make use of JIRA tasks to the max, if pending on what and anything, get it written on the related issues

• On all issues, PM should be on watch (add yourself as watcher on all issues)

• Every week, run due date more than 7 days not update filter and follow up with programmers 

6

Keep all stakeholders well-informed on project’s status

• Through email, update them with the status (preferably every month)

• Or through monthly  meeting 

7

Project deliverable produced should be reviewed for quality

• Make sure Client can assess the Quicksight

• User can edit Dataset

• User can add new Visual (author)

• User can publish Dashboard (Author)

8

Send next billing upon UAT

• Based on functionalities done, prepared UAT script

• Get feedback from client on every testing performed and test yourself before creating bug issues and pass to FE

• Make sure client signed it, it indicates all steps are tested and passed by their end

• Instruct Finance to issue the next billing of XX%

TMT UAT Test Script - BI - Sample Test Script (UAT)  

No

What to do?

Example

Remarks

1

Handing over project documentation to the business

• Send them BI  Manuals (User journey)

BI User Guide - BI - User Manual  

BI Configuration Workflow - this page

BI Operation Workflow - BI - Workflow Operation (How to Use)  

2

Releasing project resources

3

Communicating the closure of the project to all stakeholders.

• Schedule meeting with User to run final test on staging environment

• Schedule meeting with User to run the one complete recon in Production environment

4

Conduct lessons-learned studies

5

Conduct product trainings

6

Celebration