The document discusses how to implement agile practices in an enterprise setting. It describes using a combination of Scrum, XP techniques, lean practices, and traditional project management adapted to the enterprise context called "Adaptive". Key aspects include architectural planning, risk management, integration testing, continuous delivery, and working with complex requirements and stakeholder needs across multiple releases. The goal is to deliver working software in short iterations while managing the increased complexity of enterprise projects.
13. Project High Level Planning
Initial Plan Includes:
• Identify Project Steps (Releases)
• Identify Goals for Steps
• Set Approximate Dates
The Goal is to get from Business when they would like to see each step
17. Working with
Requirements
Product Owner:
• Writing up Features
• Verify Stories Description
• Prioritize Defects
• Work with Business
Team:
• Creates Stories
• Provide Estimation
• Groom Defects/Stories
18. Working with Requirements - Levels
Levels:
• Feature – full functionality is going to be developed
• Story – small part of Feature
• Task – low level Dev/QC work
24. Development Rules
• Everything possible need to be covered by Unit Test
• All defects need to be automated
• Main Flows should be covered by Integration Tests and Automation
• Test cases need to be written together with Requirements testing
• Development in Feature Branch
• Quality Control on merge