3 ms·
I think the article could be improved by defining or giving an example of a long term plan. At the start of each year we have a plan, but it's a rough plan. We
by magicalhippo 4y ago
I think the article could be improved by defining or giving an example of a long term plan.
At the start of each year we have a plan, but it's a rough plan. We know we have certain external constraints that need to be met, for example system A is moving from sending XML files via SFTP to a REST API in June. If we already know the scope, we'll have some rough dates for when we should be ready for testing and so on, if not we have some (much) earlier dates for studying documentation to determine scope and requirements.
We also have some internal goals we would like to meet, for example making a new module for doing X. They also got some rough dates attached.
This yearly plan is then used to ground our short-term planning.
However, I didn't get the feeling that it was this sort of long term plan the article had in mind.