1

Being Agile – Mindset & Culture Raja Soundaramourty June 6, 2014

2

Product Development

Maintain Work Environment

Learn from Outside Sources

Develop Team Commit to Agility

Manage Risks Ensure Process Adherence

Identify and remove impediments

Ensure Internal Communication Provide Job Training Engage Stakeholders

Everyone

Environment

Develop Product Strategy

Manage Product Portfolio

Understanding Needs of the Customer

Product Strategy

Define Product Roadmap

Define Business Requirements

Establish Product Vision

Planning

Define Product Backlog

Solution Requirements

Maintain Architecture Integration Testing

Coordinate Work Achieve Customer Acceptance

Understand Requirement Establish Development Environment

Maintain Product Quality Manage Suppliers

Design and Engineer Solutions Deploy Product

Develop Product

Coordinate Launch

Support Implementation

Plan Launch

Launch Product

Support Operations

Perform Maintenance & Customizations

Support Operations

Operate & Support Product

3

Development Sprints

Independent Test

Release Planning

Plan

Code

Design Test

Team Release Planning

Product Release Planning

Team Backlog

Levelling

Delivery

Integrate

Platform Certification

Test Package

Build

Integrate Test

Shippable Release

Potentially Shippable Product

Product Planning

Product Backlog

Product Roadmap

Product Planning

Vision

4

Product Development

Maintain Work Environment

Learn from Outside Sources

Develop Team Commit to Agility

Manage Risks Ensure Process Adherence

Identify and remove impediments

Ensure Internal Communication Provide Job Training Engage Stakeholders

Everyone

Environment

Develop Product Strategy

Manage Product Portfolio

Understanding Needs of the Customer

Product Strategy

Define Product Roadmap

Define Business Requirements

Establish Product Vision

Planning

Define Product Backlog

Solution Requirements

Maintain Architecture Integration Testing

Coordinate Work Achieve Customer Acceptance

Understand Requirement Establish Development Environment

Maintain Product Quality Manage Suppliers

Design and Engineer Solutions Deploy Product

Develop Product

Coordinate Launch

Support Implementation

Plan Launch

Launch Product

Support Operations

Perform Maintenance & Customizations

Support Operations

Operate & Support Product

5

Development Sprints

Independent Test

Release Planning

Plan

Code

Design Test

Team Release Planning

Product Release Planning

Team Backlog

Levelling

Delivery

Integrate

Platform Certification

Test Package

Build

Integrate Test

Shippable Release

Potentially Shippable Product

Product Planning

Product Backlog

Product Roadmap

Product Planning

Vision

6

Potential Release

Emerging Product

Demo and Retrospective

Sprint Planning

Day 1 Day 2–9 Day 10

Sprint Execution

Daily Activities

•  Programming •  Unit Testing •  Automated Testing •  Resolve Impediments •  Refactoring •  Automated Environment Setup •  Automated Build and Deployment •  Documentation •  Bug Fix •  Burndown Chart

Daily Scrum Meeting

Co-located, Cross-functional and Self-managed team

7

Story A story is a software system requirement formulated as a few sentences in the everyday language of the user that can be completed within an Iteration. A story is "done" when: §  All code checked in §  All developer tests pass §  All acceptance tests pass §  Help text is written §  Product Owner accepted

Iteration An iteration is a theme-driven timebox of requests to be worked on and accepted within a release of a product, it is defined in an iteration planning meeting and is completed with an iteration demo and review meeting. The terms Iteration and Sprint are used synonymously. An iteraion is "done" when: §  Product backup complete §  Performance tested §  Defects fixed or postponed

Release A release is milestone representing the internal or external delivery of a working, tested version of the System. A release is "done" when: §  Stress tested §  Performance tuned §  Security validation passes §  Disaster recovery plan tested

8

End of Day completeness criteria q  No broken code checked in! (build succeeding) q  Remaining effort estimates updated q  Ouch list updated (items to talk about in Sprint retrospective) q  Ready for next day’s synchronization scrum

Ø  What I completed Ø  What I will do next / who I need to coordinate Ø  What I learned today that the team should know

Development Task completeness criteria q  Unit tests written and passing q  Checked in, build succeeds, test suite executes clean q  Design and code standards met – review(s) complete q  Database scripts updated and checked-in q  Build scripts updated q  Code documentation updated q  Design documentation updated q  Source code promoted to acceptance test q  Task status updated

Story completeness criteria q  Business Analysis review (and approval) of story acceptance test plan q  Story acceptance test cases written (and checked in CM system) q  Deployed to acceptance testing environment q  Story acceptance tests pass q  Story acceptance tests added to acceptance regression suite q  Regression tests pass q  Source code promoted to integration q  Deployment scripts tested q  Documentation updates complete q  Product Owner review completed q  Ready for Sprint review/demo q  Story status updated

9

Sprint completeness criteria

q  Source code promoted within CM repository

q  Deployed to integration testing environment

q  Integration regression tests pass

q  Documentation updates complete (Architecture, Detail Design, Backlog)

q  Release Burndown updated

q  Sprint review, includingdemo, complete

q  Release plans updated

q  Sprint retrospective complete

Release completeness criteria

q  Integration testing complete

q  Regression testing complete

q  Documentation complete (Architecture, Detail Design, Backlog)

q  Deployment (scripts) tested

q  Operations group briefing complete

q  Support group briefing complete

q  Customer notification complete

q  Customers notified

q  Deployment complete

q  Release regression test suite updated

q  Deployment regression testing complete

10

Thank you.