STwitter project implementation plan, Roadmap
- Oleksandr Yefymov

- Feb 5, 2019
- 2 min read
Updated: Feb 8, 2019
Previous article: intro
Table of content:
Why do we need plan
The Plan ( Roadmap)
Video:
Why do we need plan

Project planning, like planning of any life area, is necessary to get visibility into the project, to get a particular target. If the people don’t have a map, in some unknown area, they will get lost and not know where to go.
So, we are going to spend small period of time, for making high level plan or roadmap, with project goals. That will allow us to keep them on track and tracking how we performing according to that goals.
Lets decompose our project to step-by-step plan for being able to make overlook at all parts of what should be done for achieving our goals, for getting working project and learning new topics.
The Plan ( Roadmap)
So, our plan / Roadmap is next:
build product backlog for our project
- list high level functional features
- prioritize high level features
- list non-functional requirements
decompose high level features (with top priority) to tasks, subtasks
- create dashboard with such tasks
- estimate decomposed tasks
- briefly review Kanban methodology
- configure dashboard for going with Agile. Start 1 sprint.
architecture design
- microservices overview. What are microservices
Scala web frameworks comparing, selecting the most appropriate and widespread one
Scala `hello world`. Scala based web framework `hello world`
Implementation of tasks from 1 sprint.
- CI/CD tools comparing, selecting one
- Cloud providers investigation, comparing, selecting one
- configuring of CI/CD for deployment to Cloud
Implementation of other sprints tasks.
project implemented(mostly it is MVP with some defined scope)
- results overview. Comparing of used technology stack to Spring Boot(with Spring Cloud)
- best practises and pitfalls overview. Resolving if present such
- additional features gathering and planning. Involving of another programming languages(Go, Dark, Kotlin...) and frameworks(Vert.x, Spark, Grails...) for implementation new microservices.

That is high level overview of what should be done for implementation of project like ours, according to modern tendencies and methodologies.
That list could be fulfilled during going according to it, but it is out main skeleton.
Lets go!






Comments