Answer the question
In order to leave comments, you need to log in
How to create a phased application development plan?
When I start doing a project, I have an idea of the result, but I don’t know what exactly needs to be done, and all this is revealed during development. From this, I just abandon projects for a couple of months, and then completely. How to make a plan and know in advance what needs to be done? Maybe there are some ready-made mindmaps for some types of software?
Answer the question
In order to leave comments, you need to log in
You divide the project (task) into component parts. You can analyze each part in more detail.
But, even if you have the most detailed TK, you will not avoid this. It's just worth spending time on solving the problem that has arisen, and not leaving the project at the first "failure".
If the whole process is divided into stages, then we can distinguish:
1. Analysis and collection of requirements
2. Design
3. Development
4. Testing and commissioning
Analysis and collection of requirements
, try to distinguish three levels of options for using your functionality:
Level 1 - project goals, for example: Selling goods through an online store, ... Level 2 - ways to achieve goals:
Placing
an order, managing a basket, Authorization, Registering a client
level 1 goals will help to focus on the result, provide the client with the expected result
level 2 goals will help highlight use cases, roles, these are usually tasks that are reflected in the TOR
of the level 3 goals are the tasks of developers that may be reflected in the technical TOR or may form a sprint
There is such a method, I call it Refactoring Driven Development. When there is no one to ask, no one knows anything and you have to work alone for the entire development and maintenance department.
Ideologically, any feature is considered as an MVP (minimal value product), fake it then make it, DDD, BDD + weekly global refactoring
Plans need to be made, but better on paper, because they do not last long, maximum 5 days. Yes, a lot of code rewritten and a lot of work thrown away, but the work is not wasted as you extract knowledge in the process.
Yes, as a method of obtaining knowledge - it is not the most productive. If you have a choice - find someone to learn from, change jobs.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question