1. What are you supposed to do?
- What is the priority of given problem?
- What is the boundary of the given problem?
2. How are you going to test it?
- Only test enough and not more. Only test what you are supposed to do.
- This test should be repeatable by team members. Serve them recipes at appropriate place if needed.
3. How are you going to implement it?
- Break the what are you supposed to do-s.
- Look at existing code and results on same or different project
- Think about steps, you already have some solutions on core problem? start implementing don't wait.
Note Things doesn't always goes linear like above. The gist is same but the details and real path may be quite different.
This page was modified on 29 Jul 2017 at 9:54 AM.
Source
1. What are you supposed to do?
* What is the **priority** of given problem?
* What is the **boundary** of the given problem?
2. How are you going to test it?
* Only test enough and **not more**. Only test what you are supposed to do.
* This test should be **repeatable by team members**. Serve them recipes at appropriate place if needed.
3. How are you going to implement it?
* Break the what are you supposed to do-s.
* Look at **existing code and results** on same or **different project**
* Think about steps, you already have some solutions on core problem? **start implementing** don't wait.
:danger:Note:: Things doesn't always goes linear like above. The gist is same but the details and real path may be quite different.