Spend more time on software Design
Fill the gaps in Documentation
- Architecture
- Front-end
- Back-end
- Design Decisions
- Most features
Building with Confidence | |
- Investment into quality i.e. spending time improving infrastructure, refactoring code, looking for better solutions (CRITICAL) | |
- Once a week half a day bug hunt with dev team or full-time Automated QA Engineer | |
- Demanding and giving developers time to do proper testing of their own effort. | |
- Test-driven development (or BDD) and Continuous Integration | |
- Code reviews | |
- Investment into writing library-style code | |
Running Tight Ship | |
- Pre-planning meeting where the dev teams play "Planning poker" (CRITICAL) |
| Day & Time | Who is involved | What | Duration | | |
| ----------------- | ---------------- | ----- | -------- | | |
| Everyday at 9:30am | Team | Standup/Scrum meeting | 15 minutes | | |
| Friday at 12:45pm | Team | Retrospective. What was accomplished and what was not. Why? | 15 minutes | | |
| Friday at 1:00pm | Team | Bug hunt through the new functionality | 2 hours | | |
| Friday at 4:00pm | Team | Planning Poker - estimating the functionality for the next week | 1 hours | | |
| Friday at 3:00pm | Product Owner and Dev Manager | Pre-planning meeting with specing out stories in GitHub and preliminary task assignment | 1 hours | | |
| Friday at 5:00pm | Dev Manager | Update schedule for the team in GitHub & Huboard | 20 minutes | | |
| Monday at 9:00am | Dev manager | Company-wide email outlining accomplishments and tasks for the next week | 10 minutes | |