Update 'Tech to do list'
parent
b15d209fd2
commit
ff82c802eb
|
@ -1,31 +1,40 @@
|
||||||
# Development proccess
|
# Tech TODO
|
||||||
|
|
||||||
1. Choose a well maintaqined open source wiki to be the base of the functionality
|
## Requirements
|
||||||
2. Find a team who are skilled in the languages, data storgae and frameworks used to build the chosen wiki (recute from the maintenainers initaly if posible)
|
|
||||||
3. Do story mapping excersise to define feaures and scope and user life cycles
|
**[Can we list what the key behaviours of the system should be. In part I want to be certain that a wiki is the most suitable candidate]**
|
||||||
4. Prioritise the stories to highlight MVP features
|
|
||||||
5. design inital wireframes
|
- ...
|
||||||
6. Define/design the tempaltes and wiki page structure needed to support the project
|
|
||||||
|
## Development Process
|
||||||
|
|
||||||
|
1. Choose a **well maintained, open source wiki** to be the base of the functionality
|
||||||
|
2. Find a team who are skilled in the language(s), data storage and frameworks used to build the chosen wiki (recruit from the maintenainers initially if possible)
|
||||||
|
3. Do story mapping exercise to define the features and scope and user life cycles
|
||||||
|
4. Prioritise the stories to highlight MVP features
|
||||||
|
5. Design initial wireframes
|
||||||
|
6. Define/design the templates and wiki page structure needed to support the project
|
||||||
7. Define the roles required to support the user features
|
7. Define the roles required to support the user features
|
||||||
8. Link the roles to the page tempaltes (who can edit what)
|
8. Link the roles to the page templates (who can edit what)
|
||||||
9. Simplify the UI to lock down the templates from careless modifications
|
9. Simplify the UI to lock down the templates from careless modifications
|
||||||
10. defind the new voting module
|
11. Define the new voting module
|
||||||
11. define the automated actions on voting, flagging, and elapsed time
|
12. Define the automated actions on voting, flagging, and elapsed time
|
||||||
12. define the sortation feature
|
13. Define the sortition feature
|
||||||
13. define the sortation actions and timings
|
14. Define the sortition actions and timings
|
||||||
14. define the activity pub output feed
|
15. Define the activity pub output feed
|
||||||
15. define the user classification feature (eg use their email address or post code to clasify them)
|
16. Define the user classification feature (e.g. use their email address or post code to classify them)
|
||||||
16. Define non-functional requirements
|
17. Define non-functional requirements
|
||||||
17. define automated testing requirments
|
18. Define automated testing requirments
|
||||||
18. Define git flow process
|
19. Define git flow process
|
||||||
19. Define peer code review process
|
20. Define peer code review process
|
||||||
20. finalise wireframes
|
21. Finalise wireframes
|
||||||
21. designing simple accessable UI/UX and demonstarate on key hero pages for deveopers
|
22. Design simple, accessible UI/UX and demonstarate key "hero" pages for developers
|
||||||
22. Build MVP using scrum process
|
- [**Q.** Can someone define hero pages, please?]
|
||||||
23. deploy, use, and get feedback
|
24. Build MVP using scrum process
|
||||||
24. Define Version 1 to meet key feedback
|
26. Deploy, use, and get feedback
|
||||||
25. Duild
|
27. Define Version 1 to meet key feedback
|
||||||
26. deploy and itterate from 23.
|
28. Build
|
||||||
|
29. Deploy and iterate from 23.
|
||||||
|
|
||||||
|
|
||||||
## List of candidate Wikis
|
## List of candidate Wikis
|
||||||
|
|
Loading…
Reference in New Issue