-
Notifications
You must be signed in to change notification settings - Fork 0
Development notes conclusions
#1 Spend a decent time for the PLANNING and USE CASES
This approach allows foreseeing all nuisance that would take much more time when finding out later in the development or testing stage.
#2 Always use ISSUES
- It makes the process transparent.
- Improved documentation - commits and code-comments link to the specific issue. Sometimes it explains why things are implemented in that specific manner.
#3 MVP-first
Better done, than perfect. Focus on basic needs first, then on extras if there's spare time. This approach allows for delivering a stable solution than feature-rich and non-working.
#4 INCREMENTAL updates on separate branches
Allows implementing updates in an isolated environment.
#4 Organize tasks in MILESTONES and keep them SMALL
This allows us to set estimates and have a better view of each moving part. The smaller the milestone the easier will it be to manage, estimate and prioritize it.
#4 Set ESTIMATES. Better unrealistic than none
Estimates inform about the plan and forces to have a more focused view on it. Wrong estimates are good because there they reveal that estimates need to be improved. After some times estimates will improve.
4-Extra milestone is the best example. Better have an extra buffer time. It's better to upset with long estimates and deliver on time, rather than with shorts and be late. Keep in mind, that estimates on projects at home and ones at work, should be based on different conditions.