Effective Development Handbook
Table of contents
Introduction
An ideal process
Agile development
The checklist
Part I: Technical
Git workflow
Main branches
Feature branches
Pull requests
Reviewing pull requests
Building a release
Emergency fixes
Why we use branches
Summary
Automation
Continuous integration
Automated testing
Deployment automation
The staging system
Coverage reporting
Summary
Coding practices
Test-driven development
Types of tests
Why we test
Linting
Readme files
Inline documentation
Summary
Part II: Management
Project lifecycle
Phases of a project
Project planning
Sprints
Sprint planning
Milestones
Sprint zero
Version numbers
Release notes
The "launch" myth
Summary
Team management
Team composition
Subteams
The team leader
The stakeholders
Summary
Project tracking
Project management tools
Writing stories
Submitting bug reports
Communication
Communicating effectively
Using Slack
Sprint kickoffs
Sprint retrospectives
Summary
Miscellaneous
Documentation
Onboarding
Project management tools
Checklist
Published with GitBook
Team management
Team management
This article is a stub. You can help by expanding it.
Have a shot-caller (aka scrum master)
Work in sub-teams if possible
Ideal team size is less than 10 people
Break your product apart if needed
results matching "
"
No results matching "
"