Conference proposal

1. New Age leadership behaviours promoting
empiricism
(supported by case study of tool driven governance)
Sheba Annie John

2. EMBRACE CHANGE

3. Empiricism
“Empiricism is at the heart of agility”

4. Challenges in sustainable business delivery
• Decision Latency
• Direct competition
• Working culture incompatibilities
• Unsynchronized priorities
• Dependency management
• Stakeholder engagement
• Communication overheads
CHALLENGES

5. Process
Oriented
Leadership
Cop to Coach
Transform to New Age Leadership Style
People
Oriented
Leadership
• Eroding leadership style
• Top down decision making
• Avoid transparency, command and
control, micro-management
• One-size fits all approach
• Enduring / Emerging leadership style,
with trust and integrity
• Decentralized decision making with more
autonomy
• Clear vision, focus on performance,
customer centric, risk takers
• Is purpose driven, nurtures passion, data-
driven decisions, demonstrate
authenticity, empathy and humility
M
I
N
D
S
E
T

6. Improved stakeholder collaboration through trust
Trusted
Person
Trusted
Partner
Trusted
Consultant
Building
Trust
‘Credibility’
+
‘Reliability
Interactions
Formal, but friendly
Also Open, Informal,
Candid conversations
Build One Team Spirit
Transparency is Key; Avoid miscommunication
Be Open & Honest across Vendors
Increase Enthusiasm and Sentiment
Break the boundaries
Stop referring Parent Org.
Be as ONE team

7. Sustainable performance with virtual teams
Shared vision
Innovation
Outcome
Focused
Competency
development
One Team
Mindset
 Culture and Mindset
transformation
 Psychological safety
 Informal connects
 Shared purpose
 IKIGAI Philosophy
 Transparency
through tools
 Focus on outcomes, not output
 People oriented leadership style
 Autonomy
 Skill gap matrix
 Functional, Technical,
Behavioral enablement
 Innovation Opportunities
 Promote creativity
 Continuous Improvements
High Performing
Teams

8. …. Leading to Desired Outcomes & Success Measures
New Age Leadership
Behavior
Trust and Credibility
Influence techniques
Sustainable
Performance
Inclusive Virtual
Collaboration
Productivity
Attrition
Team Happiness Index
Business
value delivery
Business OKR’s
Customer Satisfaction
NPS
Cost reduction
“ It is the ability to bring the best in others that makes you a leader. “ - Sadguru

9. Tool driven governance – Case study

10. Fixed Bid program
with tight timeline
of 12 months
Waterfall Model
proposal, but
execution in Agile as
per customer request
250+ members –
geographically
dispersed due to
niche skills availability
Combination of third party
product vendors, multiple
service lines and client
stakeholders
Project execution
mode change into
Product engineering
A Fortune 500 Insurance company providing protection to 50+ million people through its subsidiaries in U.S. and Japan.
“Development of a market leading Digital platform and Portal ecosystem for D2C and strengthen agent channels.”
A new logo and first of its kind Greenfield end to end product engineering program in Insurance.
Cutting edge tools and
technology expectations

11. Enabling continuous delivery with right outcomes
POD Based engagement
• Dual track POD based team structure for better requirement management
• Enablement sessions for every member of the POD – role based, process based and tool based
• POD structure based on the skills and functionality, instead of individuals or locations
• Robust agile playbook for consistency
KPI driven governance
• Tightly coupled governance structure with vendors, customers and other stakeholders
• JIRA Tool based reporting and tracking, enabling single source of truth and single view across the board
• Guidelines and protocols to ensure security and at the same time enable productive utilization of hours
Transparent communication
• Communication and collaboration through Jira, Confluence Wiki, MS Teams
• Confluence Wiki as the collaboration platform and knowledge repository
• Structured, time bound and outcome driven events during established overlap hours
• Customized Jira workflows and backlog structure to drive communication & transparency

12. Transparency through tool – Jira Backlog structure
BA Sprint
DevSprint
Ready for Delivery
Closed
Ready for
Development
Final Customer
Review

13. Built-in quality gates – Customized Jira Workflow

14. Well-defined DoR and DoD for Delivery Excellence
Functional Area Criteria Additional Information Evidences
Business Analysis Requirements are completed
Feature description to be added
Epic to be linked
BA Sprints to be assigned
L0, L1, L2 value streams to be filled
L2 Work Points to be updated
Wiki link to be added
- Acceptance Criteria (at least 2 or 3 to start with)
- Assumptions
- Out of Scope
- Dependencies identified
- Non Functional requirements (If any)
- Risks and Issues(If Any)
- Wireframes (if applicable)
- Field definitions (if applicable)
- Mandatory fields (in red) are to be present in the JIRA
Feature
- Review tasks for Development, QA, BA and Customer
are created and their status is Passed, Approved or
Closed.
Business Analysis
- Validation criteria are created / Adding detailed
acceptance criteria based on which test cases would be
created
- Splitting of Feature's might be required if the size of
Feature is more than a sprint - exceptions need to be
discussed with Lead PO's
More acceptance criteria to be added from the initial
one
All the below would be must have if applicable :
- Assumptions
- Out of Scope
- Dependencies identified
- Non Functional requirements (If any)
- Risks and Issues(If Any)
- Wireframes (if applicable)
- Field definitions (if applicable)
- Validation criteria are created in Wiki and linked with
the New Feature.
- Post this state only few addition or modification should
be done to the Feature
- If required, update the L2 workpoints
Product Council
Program Board view check
Program Backlog Health check of all tracks
Dependency identification and callout
Getting commitment for all respective tracks for a
milestone
Progress check on how we are moving towards the
commitment
-Review Program Board and n, n+1 sprint plan
-Ensure most of the dependent stories are aligned in
the same sprint
- Dependencies across the sprint should also be tracked
-High level Feature description and work point
estimation to be updated
- Alignment to SOW milestones for value stream
completion
- Bring into consideration EIS milestones wherever
applicable
- Call out the risks that we see from the program
progress or backlog burn up/down standpoint
Program Board continuously updated
BA and Dev Sprint numbers assigned to all New features
in the program board
Functional Area Criteria Additional Information Evidences
Development Coding is completed
- All user story scenarios covered
- All exceptional cases covered
- Code compiled
- Code is merged to the Central source code
repository
The code is in the Source control tool: Jira tickets
should have references to the
appropriate commits on the source control tab
This must be done against Oracle DB or MSSQL
as defined in the project.
"NF Development" subtask in Jira (can be part of
integration tests)
In the Jira tickets there should be a references to
the appropriate commits on the source control
tab
Unit tests are written. Sonar, unit test coverage is above the threshold
All java logic must be tested. In Unit tests
mock can be used for DTO, Enitites, DAO. Thresholds for projects are defined on [DevProc] Sonar
DAO technically is untestable due unit test must
not use IO operations. DAO must be covered
by integration testsonly.
Development
Sonar violations are analyzed locally The number of critical and blocker violations
should be decreased up to 0
Development
Manual test cases are executed by developer and
passed
Developers execute the limited number of test
cases which is called Critical Development Test
Cases.
Critical DEV TCs Execution task in Jira is closed
Development Code review is completed Code review is performed Code review task in Jira is passed and closed
Architecture Design documents are updated
Delivery management Release notes are provided
Delivery management New Feature is in Closed status
Delivery management All Jira tickets related to appropriate New Feature
are in either Resolved or Closed status
Delivery management
The backlog item is considered to be ready
for delivery
The New Feature is closed in Jira, all subtasks are
closed in Jira
Development
Database schema migration scripts implemented
and tested
Development
Unit tests and integration tests are created and
passed
Functional Area Criteria Additional Information Evidences
In Sprint Testing Test design is completed
Test Design to be done as per the acceptance
scenarios in the New Features
Functional test cases have been written and peer-
reviewed
Test design tasks in Jira are closed, Test cases
in Jira are linked to New Feature
In Sprint Testing Functional automated tests passed
Mostly these are the test for other parts of
system's functionality which are run to make sure
that they are not affected mistakenly.
Automated test report
In Sprint Testing
Manual test cases are executed and passed or
conditionally passed (if minor defects are not
fixed)
100% Functional tests have been executed, and
passed
Test case status in Jira is passed, manual test
execution tasks are closed
In Sprint Testing Test automation is planned
Tasks for test automation are created in Jira and
linked to the New Feature
In Sprint Testing No Major+ active defects exist 100% of critical/high defects are closed, Medium
and Low defects are tracked
Defect status in JIRA
Integration Testing
Integration test cases have been written and peer-
reviewed
Test design tasks in Jira are closed, Test cases
in Jira are linked to New Feature
Integration Testing
100% Integration tests have been executed and >
90% passed
100% of critical/high defects are closed, Medium
and Low defects are tracked
Defect status in JIRA
DoR DoD Dev
DoD QA

15. Effective Change Management process through Jira
PO

16. Jira Dashboards for Inspect & Adapt
Dashboards & Reports act as information radiators and drive teams towards continuous improvement
Development
Total WP's
planned -
program
Cumulative
(UP to S7)
Current Sprint
(S8) week 1
S9 S10 Completion % Dev Readiness- Current Sprint
Progress
Status (as of
S8 W1)
Planned 175 83 111 297
Actual 175 16
WIP 67
Dev Ready 54
Planned 433 182 308 312
Actual 374 0
WIP 182
Dev Ready 158
Planned 1058 227 95 0
Actual 1055 13
WIP 213
Dev Ready 223
Planned 368 68 124 37
Actual 335 0
WIP 68
Dev Ready 44
Planned 622 103 53 0
Actual 622 0
WIP 94
Dev Ready NA
Planned 2655 661 690 647
Actuals 2561 29
WIP 623
Dev Ready 479
96%
Overall 6683 72% 43%
21%
Integrations 100% 65%
896
Portals 86% 87% 25%
Platform 100% 99% 49%
2124
2162
SmartComm 91% 65% 56%
System Team 100% NA 69%
597
903

17. Collaboration with Confluence
 Retrospectives
 File Sharing
 Requirement
repository
 JIRA dashboards
 Risk report tracking
 Sprint demo plan
 Calendars
 Blogs

18. Stepping stones to success
 Proper team on-boarding
 Right Agile framework identification
 Defined Cadence for Collaboration
 Product Mindset and Healthy Backlog
 Well Defined KPI driven Governance
Model
 Diligent tool usage for transparency
 Culture of empowerment
 Engineering Practices Adoption
 Continuous Feedback and
Improvements
One Team Mindset
Optimal team capacity
and throughput
Streamlined
impediment resolution
Proactive risk
mitigation
Quality Delivery
“Success is nothing more than a few simple disciplines , practiced everyday” – Jim Rohn
Learning culture