Scaled agile meets the ground

15 May 2015

Scaled Agile Meets the Ground

2©Alliance Global Services 2015

Agenda

Understand Agility

Business Case Implementation

Execution Strategies & Challenges

Recommendations

Q & A


UNDERSTAND AGILITY


Is it delivering code to production every 11 sec?

It is delivering code to production every hour, day, week, two weeks, months?

Is it maximize learning from real users as quickly as every day?

Is it the ability to change the software within an hour/ day for the change identified?

It depends on the amount of agility needed by business

What do we mean by Agile?


Define Agility Needs

Understand Business Context / needs

Understand the Production Roll out Frequency

Understand the Feedback Frequency Cycles

Understand the Technology Support/ Maturity

Understand the Organization Support/ Maturity

Identification of Right Agility needs is key for the success of project since the impact is high

For ex. the distribution of non value added work for a2 weeks sprint is 16%

3 weeks sprint is 12.5%


SYNOPSIS OF TEXTILE CARE PROJECT


NORTH AMERICA300 Plants EUROPE

2000 Plants

ProductOwner

ProductOwner

App 1App 2 App 3License

License

Custom Application

0License

Development Center:Hyderabad

No vendor management required

Business Objective


Project Snapshot

Real Time Application Software Data acquisition from Meters and Sensors real time for each plant Real Time Data Display in TVs and Dashboards for Plant Engineers and

Operators Consolidated Central Reporting System No of Plants: 300 in US, 2000 in Europe Team Size: 42

Product Owners Location: US & Europe

Duration: 12 Months Development Team Location: Hyderabad No of Stories: 600 No of Teams: 6No of Sprints: 45 Sprint Duration: 2 weeks to 3 weeks


Plant Overview

Conventional Washer 1



TunnelWasher

Allen Bradley Controller

Mitsubishi Controller

Local Application

Dispensers(Automated Product Injections)

Real Time Data Display (Extended TVs)Dispensers

(Automated Product Injections)


Central Overview

Consolidated Central Reporting

System

Offline Application

External System

Local Plant 1

Local Plant 2

Local Plant 3

Local Plant 4


AGILE APPROACH TAKEN FOR PROJECT



JumpStart Purpose

Understand the user roles of <the product>

Understand and further define the functionality and the recommended technical approach and architecture

Determine high-level size and effort estimates


JumpStart Purpose (continued)

This is generally one sprint worth of activities. A general guideline is for 5 – 6 months of project effort the JumpStart shouldn’t take more than 2 weeks of effort. If you are spending more time than that you are probably over analyzing. It is important to recognize that you don’t need to get all the stories defined at the granular level – just enough to get started and create high level release plan. Idea creation never ends, and it certainly doesn’t end at the time of the business vision.

Define an Implementation approach for <the product> including tools, team, and estimated timeline

Define the Pilot target and subsequent releases

Define the Project Governance


Execution Strategy - JumpStartO

ne

um

bre

lla

Conducted

JumpStart Phase

which helped us to

bring in all the

stakeholders to a

single location. Ob

ject

ive

Defined the

Product Vision,

Identification of

Unknown and Risk

areas with

Mitigation Plans,

High level product

Backlog,

Architecture/Design

Kn

ow

led

ge

Sh

arin

g

Product owners

spread across the

globe, Created a

Proxy Product

Team considering

the Distributed

location challenges.


Execution Strategy – Team Formation/Changes

Project Progress Span

Focus TeamTeam A

Cross-Function

IntegrationTeamTeam A

Team B

Team A

Team B

Team BCross-Function


Execution Strategy – Process Transformation

1 Product Team

1 Product Team

5 Scrum Teams

1 Product Team

2 Scrum Teams

1 Kanban Team


Execution Strategy – Team Collaboration

MonthlyReleaseReviewMeeting

WeeklyBacklog

Grooming

WeeklyFocus

Meetings(UI, DB, Design,Testing

ScrumCeremonies


The Challenge !!!

19

Hi… Mr Hardware !!!

Hardware

Service

Database

Software

UI


Testing Complexities Of Hardware and Software

Create “Virtual

Hardware”

Service

Software

Database

Hurray !!!Application

Tested Hardware

&Virtual Hardware

meets !!!


Understand the signal pattern and frequency sent from the hardware

21

• Virtual hardware needs to understand that pattern.

Actual hardware

• Every hardware have a particular signal pattern and frequency

Virtual Hardware


PLC Simulator Tool (Virtual Hardware for Washer)

Write Data to PLC• This tool will be sending data to PLC that

would be the replica of signals sent by actual Washer

Create multiple virtual hardware in the test

module

• The tool must have provision for creating multiple simulators for multiple washers

Configure the virtual hardware

• Provide options to configure the virtual hardware to effectively create test scenarios

Multi tasking of each washer

• This tool must be able to simulate PLC for multiple washers at a time (multithreading)


Result

• MVP as business needed

• Delivered 40 Successful Sprints

• High satisfaction from end users, product sponsor/owners

• High satisfaction from team and internal stakeholders


Recommendations

• Before hitting the ground understand your agility needs

• Define the agile approach to be followed

• Agility needs of project can vary during the project life cycle, change of course correction as needed


Thank YouKrishna Mohan TunuguntlaSr. Project [email protected]://www.allianceglobalservices.com

mailto:[email protected]

Leadership & Management

Scaled agile meets the ground