Created
July 15, 2013 13:28
-
-
Save Dimitri-Gnidash/5999939 to your computer and use it in GitHub Desktop.
Thoughtful Team
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 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) | |
| - Shorter Planning meeting for all dev team members with presence of a product owner to understand priorities | |
| - Daily Standup | |
| - Negotiable Scope and Timelines, but not team's estimates. (CRITICAL) | |
| - Product Owner responsible for researching, analyzing what to build next. Preference for concise, but thorough specs either as user stories/epics. | |
| Treasuring the Team | |
| - Quarterly and Yearly Reviews with improvement plans | |
| - 3 conversations with new hires: 2 weeks, 1 month, 3 months | |
| - 2-3 conversations with troubled employees: 2 week intervals |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Excellent and concise summary of the ideal team & workflow. The half day bug hunt is a great idea I would even suggest making it a high priority event that the entire team can participate in.
A+