Enterprise Agile
Process – Concurrent Development Description
1)The
method evolved from the needs to support multiple projects that reused
components among like:
·
workflows
·
visual and non-visual components
·
business objects
·
transactions and
·
services
·
architectural services
2) Scrum
Practices for all concurrent projects:
(See practices for
more detail.)
·
Scrum Management Practices
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
·
BalancedAgility
Engineering Practices
o
Continuous Integration
o
Testing: Unit, Spot, Regression, Acceptance
o
Daily Builds
o
Spontaneous Pairing
o
Standards: Coding, Documentation, Database
·
Scrum Attitude and Values
o
Cooperation
o
Sharing Knowledge
3) EAP Practices for managing all projects
all-at-once
EAP Management Practices
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
o
Integration Testing across applications and reusable components
o
Shared Reusable Components Inventory
No thick documents,
expensive tools, or process definitions required!!!
|
