Any idea, story feature, method or module we set out to put action go through a journey across 4 stages each
stage having it’s own status.
Basic breakdown of any story.
Discover .
look at the story from all angle, gather resources, create a poc if needed.
design. design the solution, could be a rough chart, user flow in sheets or a rough story line.
develop. sit down and code aka develop. Keep testing and searching for edge Cases.
deploy. test, benchmark, build, verify, deploy.
Process.process refers to a collection of formula / function /module.
divide the story into 3 parts :
1. Input : How will user input, what will they input, is there any other data to be referenced || pulled on the basis of input, do we need to do any process over it. Any Edge Cases.
2. Process : What all process do we need to perform on the input data.
3. output : whats the output ( view to be generated), if any extra process to be applied.
Schedule them in your calendar.
have fun changing those stages and status.
No external library’s
follow coding standards
pure vanilla javascript else mentioned.
get a clarity on what needs to be done, before jumping on it.
pro - tip to get clarity, write down all the possible, who , why , what, when, where and write the answer. Start coding only when you the answer to all.
be proud of your work and maintain it with proper documentation.
Each story update has to be pushed to the working in process ( wip ) repo for that particular project.
A small description, along with a readme doc or in file comments, answer few questions and showcase some use cases. Do write down edge cases and test cases.
