Enterprise agile Process

57 %
43 %
Information about Enterprise agile Process
Technology

Published on February 7, 2009

Author: ravindra2109

Source: slideshare.net

Description

A "balancing act" to achieve Agile Reusability an standardize application development for the enterprise.
A collection of agile practices that support the Agile Manifesto
Manage several applications simultaneously
Encourage the creation and use of reusable components at all levels of scale

Business improvement by Enterprise Agile Process

(About Ravindra) Electronics and communication engineer from Rajasthan university Pursuing MBA (IT) from symbiosis international university Did project on SAP practice operations management from fujitsu consulting india private limited 06/07/09 Ravindra EAP

Electronics and communication engineer from Rajasthan university

Pursuing MBA (IT) from symbiosis international university

Did project on SAP practice operations management from fujitsu consulting india private limited

06/07/09



Ravindra EAP

EAP 06/07/09 Ravindra EAP

06/07/09



Ravindra EAP

What is EAP? A "balancing act" to achieve Agile Reusability an standardize application development for the enterprise. A collection of agile practices that support the Agile Manifesto Manage several applications simultaneously Encourage the creation and use of reusable components at all levels of scale 06/07/09 Ravindra EAP

A "balancing act" to achieve Agile Reusability an standardize application development for the enterprise.

A collection of agile practices that support the Agile Manifesto

Manage several applications simultaneously

Encourage the creation and use of reusable components at all levels of scale

06/07/09



Ravindra EAP

06/07/09 Ravindra EAP

06/07/09



Ravindra EAP

Roles Application Developers Coaches/Architects (only when technical guidance and agile practice guidance is needed, otherwise NOT required) Team leaders/Scrum masters Support: Systems, CM, testing, etc. Shared Resources team Shared Resources developers 06/07/09 Ravindra EAP

Application Developers

Coaches/Architects (only when technical guidance and agile practice guidance is needed, otherwise NOT required)

Team leaders/Scrum masters

Support: Systems, CM, testing, etc.

Shared Resources team

Shared Resources developers

06/07/09



Ravindra EAP

(continued) Enterprise Architect (needed only if Shared Resources team developers cannot articulate a vision) Shared Resources team leader Project/Application Sponsors Clients: business process owners, external clients 06/07/09 Ravindra EAP

Enterprise Architect (needed only if Shared Resources team developers cannot articulate a vision)

Shared Resources team leader

Project/Application Sponsors

Clients: business process owners, external clients

06/07/09



Ravindra EAP

Project Management Break Multi-Application Project In Sprints == 1-3 month Iterations. Break the lifecycle of each individual project into 1 month Sprints (Iterations). Use the All-At-Once Model to develop software: Analysis, Design, Implementation, Testing and finish with an executable release Master Product Backlog – Manage everything there is to do through a master prioritized list. This list includes: features, upgrades, release management, configuration management, adopting new tools, etc. 06/07/09 Ravindra EAP

Break Multi-Application Project In Sprints == 1-3 month Iterations.

Break the lifecycle of each individual project into 1 month Sprints (Iterations). Use the All-At-Once Model to develop software: Analysis, Design, Implementation, Testing and finish with an executable release

Master Product Backlog – Manage everything there is to do through a master prioritized list. This list includes: features, upgrades, release management, configuration management, adopting new tools, etc.

06/07/09



Ravindra EAP

(continued) Application Product Backlog - Each application contributes to the overall Product Backlog Shared Product Backlog - In addition shared Product Backlog contributes to the overall product backlog Do daily internal releases to integration boxes Test each System through banks of unit tests per application Release the product to external customers after a few internal iterations 06/07/09 Ravindra EAP

Application Product Backlog - Each application contributes to the overall Product Backlog

Shared Product Backlog - In addition shared Product Backlog contributes to the overall product backlog

Do daily internal releases to integration boxes

Test each System through banks of unit tests per application

Release the product to external customers after a few internal iterations

06/07/09



Ravindra EAP

(continued) Sprint Planning Meeting: At the beginning of an iteration, get everyone together in one room, prioritize the features of the project and decide which features go into that Sprint == Iteration System and Application Spring Planning Meeting Sprint Backlog. Break Product Backlog chosen for Sprint into 2-4 hr tasks. Evaluate timelines with these estimates. Recalculate timelines every day after getting the status of completion from the Daily Scrums. 06/07/09 Ravindra EAP

Sprint Planning Meeting: At the beginning of an iteration, get everyone together in one room, prioritize the features of the project and decide which features go into that Sprint == Iteration

System and Application Spring Planning Meeting

Sprint Backlog. Break Product Backlog chosen for Sprint into 2-4 hr tasks. Evaluate timelines with these estimates. Recalculate timelines every day after getting the status of completion from the Daily Scrums.

06/07/09



Ravindra EAP

(continued) Sprint Review Meeting. Give a Demo to the customer after each Sprint. Get customer feedback and reintroduce the feedback into the Product Backlog Scrum of Scrums - frequent meetings, once or twice a week, at the same time and place, where team leaders share information about the status of their applications Daily Scrums - Daily 15 min. meeting, at the same time and place, where resources report 3 things: 1) what they worked on for the last 24 hrs. 2) what issue they have 3) what they will be working for the next 24 hrs. 06/07/09 Ravindra EAP

Sprint Review Meeting. Give a Demo to the customer after each Sprint. Get customer feedback and reintroduce the feedback into the Product Backlog

Scrum of Scrums - frequent meetings, once or twice a week, at the same time and place, where team leaders share information about the status of their applications

Daily Scrums - Daily 15 min. meeting, at the same time and place, where resources report 3 things:

1) what they worked on for the last 24 hrs.

2) what issue they have

3) what they will be working for the next 24 hrs.

06/07/09



Ravindra EAP

(continued) Visible Status - keep a visible chart with the stories and their completion status. Hang it on the wall! (document) Sustainable Pace - Practice long-term sustainable development. (In most cases this means don’t exceed 40 hr. of work in the US or 35 in Europe) Pair Programming. Use pairs for mentoring, collaboration, and the creation of X-functional team Collective Ownership - every developer is responsible for the deliverable and must be able to change, upon coordination, any component of the system 06/07/09 Ravindra EAP

Visible Status - keep a visible chart with the stories and their completion status. Hang it on the wall! (document)

Sustainable Pace - Practice long-term sustainable development. (In most cases this means don’t exceed 40 hr. of work in the US or 35 in Europe)

Pair Programming. Use pairs for mentoring, collaboration, and the creation of X-functional team

Collective Ownership - every developer is responsible for the deliverable and must be able to change, upon coordination, any component of the system

06/07/09



Ravindra EAP

Analysis CRC Stories - short UCs on CRC (5’’ by 3’’) cards for all Use Cases … then play cards with the customer to decide which features will be implemented! (document) Use Case docs only for more complicated behavior (document) On-Site Customer - Developers don’t know business rules and business needs…… An on-site customer, or at least an Available Customer is a key priority 06/07/09 Ravindra EAP

CRC Stories - short UCs on CRC (5’’ by 3’’) cards for all Use Cases … then play cards with the customer to decide which features will be implemented! (document)

Use Case docs only for more complicated behavior (document)

On-Site Customer - Developers don’t know business rules and business needs…… An on-site customer, or at least an Available Customer is a key priority

06/07/09



Ravindra EAP

Testing Test first – Write the a unit test for the functionality you are developing before you write the component and maintain the test while you do development. Unit Test - Create and maintain a Unit Test for every major component of the system Application Regression Testing - base Regression Testing on Unit Tests. Any other way to do it will duplicate resources and knowledge requirements. Multi-application/system regression tests. 06/07/09 Ravindra EAP

Test first – Write the a unit test for the functionality you are developing before you write the component and maintain the test while you do development.

Unit Test - Create and maintain a Unit Test for every major component of the system

Application Regression Testing - base Regression Testing on Unit Tests. Any other way to do it will duplicate resources and knowledge requirements.

Multi-application/system regression tests.

06/07/09



Ravindra EAP

Architecture Metaphor - Simple story of how the whole system works (document) Simple Design - Don’t add features you are not needing now (YAGNI) Layered Architecture through Patterns Strong architectural Style, preferably enforced with/through Frameworks Refactoring - Redesign without changing the behavior. Refactoring can provide great efficiency gains. Coding Standards - all code must look as if it was developed by the same developer 06/07/09 Ravindra EAP

Metaphor - Simple story of how the whole system works (document)

Simple Design - Don’t add features you are not needing now (YAGNI)

Layered Architecture through Patterns

Strong architectural Style, preferably enforced with/through Frameworks

Refactoring - Redesign without changing the behavior. Refactoring can provide great efficiency gains.

Coding Standards - all code must look as if it was developed by the same developer

06/07/09



Ravindra EAP

Layered Architecture Enterprise Agent Network (servlet-based PAC/MVC framework) applications workflows visual components services transactions business objects architectural services 06/07/09 Ravindra EAP

Enterprise Agent Network (servlet-based PAC/MVC framework)

applications

workflows

visual components

services

transactions

business objects

architectural services

06/07/09



Ravindra EAP

Release Management Continuous Integration - Integrate and build the system many times a day. Release architectural layers in inverted order Use versions to use and simultaneous develop multiple new code bases 06/07/09 Ravindra EAP

Continuous Integration - Integrate and build the system many times a day.

Release architectural layers in inverted order

Use versions to use and simultaneous develop multiple new code bases

06/07/09



Ravindra EAP

Values and Beliefs Commitment - Care for the project Focus - Concentrate on the task at hand Openness - Problems, status and plans Respect - for other team members and customers Courage - Admit faults, request necessary things, talk about things as they are Share Knowledge - technical and non-technical 06/07/09 Ravindra EAP

Commitment - Care for the project

Focus - Concentrate on the task at hand

Openness - Problems, status and plans

Respect - for other team members and customers

Courage - Admit faults, request necessary things, talk about things as they are

Share Knowledge - technical and non-technical

06/07/09



Ravindra EAP

Examples William Mercer, 3 applications in production Nike Securities, 5 application in production Caremark, 15 applications in production 06/07/09 Ravindra EAP

William Mercer, 3 applications in production

Nike Securities, 5 application in production

Caremark, 15 applications in production

06/07/09



Ravindra EAP

Conclusions Agile Development is a paradigm shift for software development EAP is easy and cheap to implement EAP can save millions of dollars through reusable components 06/07/09 Ravindra EAP

Agile Development is a paradigm shift for software development

EAP is easy and cheap to implement

EAP can save millions of dollars through reusable components

06/07/09



Ravindra EAP

References – Agile Software EAP: http://www.enterpriseagileprocess.com Extreme Programming Explained - Kent Beck, Addison and Wesley 06/07/09 Ravindra EAP

EAP: http://www.enterpriseagileprocess.com

Extreme Programming Explained - Kent Beck, Addison and Wesley

06/07/09



Ravindra EAP

Add a comment

Related presentations

Related pages

Understanding Enterprise Agile -LeadingAgile

Understanding Enterprise Agile ... or they represent a small piece of the end-to-end process, you really just have one or more instances of small team agile.
Read more

Enterprise Transition Framework - agile42 | The Agile ...

agile42 has created the Enterprise Transition Framework that leads and support an organisation through the process of becoming more Agile
Read more

Enterprise Unified Process (EUP): Strategies for ...

Enterprise Unified Process (EUP): Strategies for Enterprise Agile. Home; ... The Lifecycle for the Enterprise Unified Process (EUP): 2013. EUP Resources:
Read more

Agile Software Requirements: Lean Requirements Practices ...

Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise (Agile Software Development) (Englisch) Gebundene Ausgabe ...
Read more

Enterprise Agile - Emergn

Whenever I discuss the term “Enterprise Agile” with someone, the conversation forms into three short questions; “How do you increase value throughout ...
Read more

Scaling agile in the enterprise with SAFe and JIRA Agile ...

This guest post from Sander Brienen, senior engineer and Atlassian Expert at Avisi, is part of our Do Agile Right mini-series about about scaling agile.
Read more

Agile Software Requirements - amazon.com

Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise (Agile Software Development Series) 1st Edition
Read more

Enterprise Agile: Process Adoption

Material posted on this site has evolved, often greatly, from The Enterprise Unified Process: Extending the Rational Unified Process by Scott W. Ambler and ...
Read more