-
Notifications
You must be signed in to change notification settings - Fork 1
Agile Phase 3: construction
Matthew Hall edited this page Sep 11, 2018
·
2 revisions
Each feature needs to be visually and technical designed so that you can collect early feedback from users and adapt to their needs.
Features that will provide value to users are broken down into small user stories, coded, documented and reviewed in order to ensure that the team is delivering high quality working software.
Developed software is continuously integrated with the rest of the system using automated testing, static code analysis, and functional testing.
Features are deployed as soon as they are done to Production to get rapid user feedback. If the Product Owner doesn't want a feature to be made available to users, the code is still deployed to Production with the feature toggled off.
- Behavior Driven Development
- Low Fidelity Mockups for rapid user feedback and design
- Description of the Data, logical data model (See [Living-Documentation])
- High Fidelity Mockups to clarify the Definition of Done for a feature
- Data Model Development (Spreadsheet for logical model)
- Behavior Driven Development (BDD) Scenarios, (Tests)
- Automated Code Generation
- CRUD operations for all data objects
- API to calls on the CRUD operations
- Physical Database Models
- Custom API Specification & System Functions development
- Automated Integration Tests (ensure that APIs function)
- Functional Tests