Project Management

Session 4

20 August 2020

Trainers: Satvika & Sridhar

 AGENDA Session 4 - 20.08.2020

1 Deep Dive - Capability : Build Stage

2 Deep Dive - Capability : Test Stage

3 Quiz 04

4 Assignment - 04 Brief
 The Project Wireframe considering Hybrid Model

IDEAS &
PLANNING CAPABILITY LAUNCH CLOSURE
FEASIBILITY
Design, Built
and Test in
Iterations
The L1 Sprint Planning
Process Design Requirements Conceptual Go-Live &
Ideas Maturity gathering & BAU
Design Hypercare
Assessment Designing Sprint
3-4 weeks/
Solution Sprint Backlog Realisation &
sprint
Daily Scrum
Assessment
determines gap
and/or L1 Product
requirements are Backlog/Release Sprint Review
unclear Plan Sign-off

As-Is Sprint 0 Sprint 1 - n Hardening Go-Live Operate

✓ Business Decision based on ✓ Tool Set-Up for tracking (Like ✓ Sprint Planning ✓ UAT ✓ Plan and Test ✓ Benefit
Business Case Jira) ✓ Change Management ✓ Regression User Support Tracking
✓ Governance & Organisation ✓ Functional Specifications ✓ Design & Build Testing ✓ User Training
Set-up ✓ Cost Governance ✓ Test ✓ Cost Tracking ✓ Hypercare
✓ Vendor Decision ✓ Business approval on Specs ✓ Project Review ✓ PGLS defect
✓ DEMO Build ✓ Backlog planning tracker
✓ Test & Data Approach
3
* There would be a short hardening spring at the end of all the sprints. Generally hardening would be done as a part of each sprint
 Project Wireframe: Project Management Stage Gate
Pre-
Ideas & deployment/
Feasibility Requirement 1 Idea Strategy Prepare Charter

Gathering
PM GATE 1

Design/ Scope Definition & Plan & Start Governance Plan & Start Executing Set Up & Start
Planning Personalization 2 Requirements Sign-off
Project Kick-Off
and Progress Reviews Stage Gates Documentation Management

PM GATE 2

Build/ Monitor & Control Time, Unit/Integration/Smoke

Development 3 Build/Development
Cost & Quality
Define Test Approach Prepare for Test
Test

Capability PM GATE 3

System (Functional) System (Non Functional)

Test 4 Testing Testing
Interface Testing User Acceptance Testing

PM GATE 4

Control Testing
Launch Deployment 5 End User Training Cutover
(Validation Testing)
Release/Go-Live

PM GATE 5

PM GATE 6
Post Go-Live & Lesson’s
Closure BAU 6 Hypercare Monitor service KPIs BAU Learnt/Retrospection
Benefits Tracking
MOVE TO BAU

4
 Capability - Build/Development
To carry out all activities needed to achieve the project objective. Doing and monitoring of the actual work needed
Objectives to develop and bring to market/ implement the agreed project products.
Pre-Deployment/
Phases Design/ Personalisation
Requirement Gathering
Innovation
IDEA & FEASIBILITY
Funnel
High Level
Build/ Development
Steps
Input
• The Build activities are
implemented as planned
by the respective parties
• Build team produces
regular Status Reports on
Build that show actual
Activity progress and performance
against planned activity
and forecasts
• Development happens in
Dev and/or QA
environment
5 Output
Build/ Development Test Deployment Post Go-Live & BAU
PLANNING CAPABILITY LAUNCH CLOSURE
Monitor and Control Time, Cost and Unit/Integration/Smoke
Define Test Approach Prepare for Test
Quality Testing
• Monthly Project Plan Review/ Status
Report
• Assign resources to tasks
• Monitor the completion of these
tasks, keeping the project on track • Unit testing of
against the baseline project plan modules/components
• Define high level of
and re-planning where necessary • Integration testing of a set
• Produce regular and accurate
approach for testing • Ensure Test Readiness
of modules/components
• What testing to be included
Project Status Reports that show • Smoke testing for key
actual progress and performance functionality
against planned activity and
forecasts
• Updated Project Status Report,
Project Plan
 Build/Development
BUILD PROCESS COMPONENTS Two Types of Build Process
✓ Fetching the code from the source control
repository A full build performs a build from scratch. It treats all resources
✓ Compile the code and check the in a project as if they have never been seen by the build

FULL BUILD
dependencies/modules server/tool
✓ Run the automated unit tests A full build always starts from empty work area; it is taking a full
✓ Link the libraries, code, files, etc accordingly. project as an input, figures out the dependencies, compiles all
✓ Once successfully passed, Build the artefacts and the source files in the project and builds all the parts in order
store them and archive the build logs accordingly, and then assembles them into the build artifact as a
final output
An incremental build which uses a “last build state,” maintained

INCREMENTAL BUILD
internally by the build server/tool, to do an optimized build based
on the changes in the project since the last build.
An incremental build checks and compares every source file, as
well as anything else that depends on the target, if any
dependency has been modified after the target was last built, the
target will be rebuilt, otherwise the file from the previous build
would be reused.
Since incremental builds only rebuild what needs to be, they are
usually much faster than full builds and use fewer resources
6
 Build/Development – Project Types

Project Type Out of the box Configuration Customization Interfaces New Infra

New Application Development No No Yes Maybe Yes

ERP/SaaS Application Yes Yes Maybe Maybe Maybe

Upgrades in existing application Yes No No Maybe Yes

Improvement in existing application No Yes Maybe Maybe No

Application moving to cloud or changing

No No No No Yes
cloud

Integrating applications No No Maybe Yes No

7
 ERP/SaaS/Cloud Hosted Application - Build
During Build, Project Manager should ensure that all below items are discussed and should keep a
track of all of them

Application Data

▪ Master Data - Templates, Receipt, Feedback,

▪ Detailed Workflow discussions - all workflows,
approvals & documents
▪ Interim Demos - to ensure things are coming up as
expected
▪ Configuration/Customization – identify early and
early
▪ UI/UX discussions - start early
▪ Interface Integration - identify systems to
integrate and start discussions early
▪ Reporting capabilities of the application
Signoff
▪ Historical Data - # of years, data sets, fields
▪ Data Upload - all data cleaning, transformation
and upload
▪ List of Users - user list and access controls
Infrastructure
▪ Instance Creation - to start working on the build
▪ Servers, databases, SSO, architecture etc.
▪ Licenses

8
 Testing Theme

Logging and tracking the defects to

closure during the testing ensures
that there are no surprises at a later
point in time. Effective defect
management system is essential to
make testing a success. Some of the
defects might be converted to
Change Requests (CRs) which also
need to be monitored closely

9
 Define Test Strategy & Approach

Detailed PLANNING Seamless EXECUTION Robust GOVERNANCE

▪ Identify nature of ▪ Infra Readiness ▪ Business-IT

testing required ▪ App Readiness Collaboration
▪ Consolidated test Checklist ▪ Governance
cases/scenarios ▪ Communication to Continuous ▪ Periodic review
Comprehensive ▪ Day level planning Ensure Test relevant stakeholders meetings
Engagement
Testing Plan ▪ Gate criteria Readiness ▪ Training the users ▪ Checkpoint calls

▪ Plan trainings ▪ Test Results and ▪ Publish Metrics

▪ Training calendar - observations ▪ Testing Progress
user & trainer invites ▪ Errors/Defect ▪ Scenario Level
▪ Training modes Management Tracking
Training ▪ SOPs for Manual Error/Failure ▪ Go/No go meeting Tracking & ▪ Debottlenecking
Processes Management Reporting
Calendar

10
 Prepare for Test

App Readiness Checklist Test Infra/Environment Test Cases/Scenarios

▪ Build Ready
▪ Test Conditions ▪ Business Scenarios/Test Cases
▪ Unit Testing & SIT Done
▪ Test Devices & Infra ▪ Detailed Test Scrips
▪ Hosted and Configured
▪ Test Environment ▪ Expected Outcome
▪ Data for Testing Ready

Users & Access Provision Training Test Users Communication & Governance

▪ Test Users
▪ Train Test Users Pre-UAT ▪ Publish Results Regularly
▪ Provision Access
▪ Demos ▪ Defects Mgmt. defined
▪ Controls

11
 Testing Progress Summary

A+B+C A B+C B C D E
Module/Process Test Cases Total
Retested & Retesting In
Stream Ready Cases Completed Passed Failed In Progress Pending
Passed Progress

Module 1 Yes 153 45 38 7 3 4 50 58

Module 2 Yes 15

Total 168

Module/Process Defect
Test Case ID Defect ID Defect Summary Defect Status Details of Resolution
Stream Category

Module 1 Minor Issue Closed

Module 2 Major Change CR

12
 What can avoid this?

Performing the requisite

testing as and when required
right from build stage to
launch stage

User Testing becomes really

User Testing
important becomes
especially really
in scenarios
important especially
where most in scenarios
of the user
where
requirements mostasofout
come theofuser
box in
requirements come as out of box in
an ERP or SaaS application with
an configuration/customization
minimal ERP or SaaS application with
minimal configuration/customization

13
 Testing Pyramid

Control Testing Launch

User Acceptance Testing Black Box

Testing
Interfaces Testing • Other testing such
(except non as Sanity testing,
Capability - Test functional) Regression testing,
System (Non Functional) Testing
are also done on
System (Functional) Testing Functionality need basis

Smoke Testing

Integration Testing Capability - Build White Box

Testing
Unit Testing Code

14 Most Important for Program Manager Keep an eye - for Program Manager
 Example with all levels of testing pyramid

Build 1

Unit Testing External

System 1
Build 2 Interfaces
User
Control
Acceptance
Testing Testing
Integration Testing Testing
External
System 2
Build 3

Smoke Testing

System (Functional) Testing

System (Non Functional) Testing

15
 Levels of testing pyramid

Build 1
External
Unit Testing System 1

Unit Testing
Build 2 System Integration Testing

Integration Testing
External
System 2
Build 3

Smoke Testing User

Interfaces Control
Acceptance
System (Functional) Testing Testing Testing
Testing

System (Non Functional) Testing

16
 Use Case for Testing
S1P - ECC (SAP R3) SAP Business
APO
Warehouse (BW)
Master Data Demand Sales History
Planning
Material

Interface (CIF)
Plant

BOM Business Warehouse

Production Planning & for reporting and
Supply Network
Routing Detailed Scheduling data Management
Planning
(PP/DS)
Transaction Data

Sales Orders Reports

Production Orders Distribution Orders
Purchase Orders
Inventory Demand Sensing
Production Orders A Non SAP System connected to APO used as Demand
Terra Adjustment tool (For DP) and Inventory calculator (For SNP)
Inventory
17 Arrows represent the flow of data
 Experience Card - 01

Suggestions for a new Thoucian in terms of how to manage client expectations?

That depends with role if PM role like therefore, understand your own role and
responsibility clearly and clarify if in doubt.

High Quality and detailed

Ways of working Upskilling
documentation

Share softer aspects in

Understand his KPIs Change in expectations
addition to PM rigour

Understand who the client is and what their expectations are

18
 Experience Card - 02

How have you dealt with difficult stakeholders and what do you do about it ?

Every stakeholder is unique and needs to be dealt with flexibility but try not to
offend them

Be firm but allow room for

Assess, realise and adapt Demonstrate confidence
discussion

Increase level of comfort

Deliveries reviewed and
with transparency and Over communicate
quality assured
communication

19
Do a stellar job of stakeholder landing
 Experience Card - 03

Can you share a few leadership skills that are imperative for a project Manager to have?

Communication Influencer Empathy

what, how and to whom Manage conflicts, motivate Keep calm with risks, conflicts
team, stakeholder management and issues, Team building

Decision making Problem solving

Involve key team members, Guide the team at ground level

positive attitude to motivate them

20