22
33## Planning/Prioritisation
44
5- a. What are the user and data needs
6- b. What about the other work streams - what impact on our planning/prioritisation. Are there any dependencies or crossovers?
7- c. What task can we pick up that adds the most value or has the most urgent dependencies - scoring
8- d. Add to project board Trello/Clickup/Jira - This is how we share what we are doing and our progress (specific to development).
9- e. What are our dependencies?
10- i. Do we have what we need ie - common APIs
11- ii. If no API is there a specification (Swagger doc) we can use to stub until it is available?
5+ 1 . What are the user and data needs
6+ 2 . What about the other work streams - what impact on our planning/prioritisation. Are there any dependencies or crossovers?
7+ 3 . What task can we pick up that adds the most value or has the most urgent dependencies - scoring
8+ 4 . Add to project board Trello/Clickup/Jira - This is how we share what we are doing and our progress (specific to development).
9+ 5 . What are our dependencies?
10+ 1 . Do we have what we need ie - common APIs
11+ 2 . If no API is there a specification (Swagger doc) we can use to stub until it is available?
12+
1213![ API] ( ./img/ways1.png )
1314
1415## Weekly task allocation/review
@@ -19,11 +20,11 @@ e. What are our dependencies?
1920
2021## Development process
2122
22- Branching strategy based off the API playbook - https://playbook.hackney.gov.uk/API-Playbook/branching_strategies/#gitflow
23+ We use the [ GitHub Flow branching strategy ] ( https://playbook.hackney.gov.uk/API-Playbook/branching_strategies/#gitflow ) -
2324![ API] ( ./img/ways2.png )
2425
25261 . Daily stand-ups (5 - 10 minutes) - What is everyone doing, is anyone blocked?
26- 2 . TDD - Git Branch -> Test -> Code
27+ 2 . TDD - Git Branch ➡ Test ➡ Code
27283 . Pull request/Peer Review - Frequent
28294 . Release
29305 . Rinse and repeat - start process on next task
0 commit comments