Enterprise Agile Process

 

 

 

Business Description

Development Description

Development Practices

Availability

 

EAP - Software Development Practices

EAP Management Practices for Concurrent Application Development

o        “Scrum of Scrums” Meetings

o        Global Backlog

o        Shared Backlog

 

o        Shared Resources Scrum Master

 

o        Shared Resources Team

 

o        Integration Testing across applications and reusable components

 

o        Shared Reusable Components Inventory

 

o        Release Content Announcements

 

o        Production Super Sprints

 

EAP Engineering Practices for Concurrent Application Development

o        Integration Testing across applications and reusable components

 

o        Shared Reusable Components Inventory

 

OPTIONAL Context Driven Practices

(OPTIONAL in very large organizations) "Shared Services" team after when the shared components reach critical mass that need external coordination, typically 2-3 applications. This shifts the responsibility of the release of the shared components to the Shared Services team, but not necessarily the component ownership.

Scrum Team Management Practices (Single Team)

o        Product Owner

o        Product Backlog

o        Sprint

o        Sprint Planning Meeting

o        Story Task Breakdown (also a Requirements engineering task)

o        Sprint Backlog

o        Daily Scrums

o        Sprint Review Meeting

Minimal Engineering Practices – (Single Team -- commercial or mission critical) (See: BalancedAgility)

o        Continuous Integration

o        Testing: Unit, Spot, Regression, Acceptance

o        Release Management

o        Spontaneous Cooperation and Collaboration BA

o        Standards: Coding, Documentation, Database

Scrum Attitude and Values

o        Cooperation

o        Sharing Knowledge


(OPTIONAL in Newbie Teams) -  Architect roles. Architects are required to know a basic collection of patterns, know most refactorings, help the team leader (ScrumMaster) make technical decisions, mentor developers, and perform all other developer's duties: gather requirements, design, CODE and TEST. In some cases the architect of the project is also the ScrumMaster, but that depends on individual ability.

(OPTIONAL in Organizations in Transition) weekly brown bag lunches mixing presentations and workshops on: patterns, refactoring, existing technologies in the org, new technologies, architectural vision exercises, best practices, etc.