Inscrivez-vous ou connectez-vous pour rejoindre votre communauté professionnelle.
The best answer would be "You and Your Team", Plans are put by people and adapted by people. When a plan isn't getting you to the purpose of goal then you change it. and who changes a plan? It's the people.
How to make plans in an environment of constant changes? Our experience tells one thing – be flexible. Quickly adapting to the new situation and letting go of old plans is the key. You shouldn’t make very specific long-term plans.
Agile, scrum, Trello, sprints – these and many other keywords mark today’s approach to planning. It’s all about the constant revision of tasks at hand and updating the plans accordingly. You’ve got to launch your product as quickly as possible, get customers on board, and then smooth it out on the go.
In planning, flexibility means that everybody knows exactly what the goal they are trying to achieve is, but also that the path to it is not carved into the stone. Especially when it comes to software development. There are too many variables that can not be predicted – development can take longer than expected, user feedback can turn everything upside-down, core ideas themselves can change during the process. I’m sure you’ve seen it happen.
Business plans formed the core of every starting enterprise some years ago. It wasn’t about your 30 second pitch. It was all about the length and depth of your Excel sheet – how many employees are you going to have in 3 years? What do you mean you don’t know? Are you prepared at all?!
Don’t get me wrong, a well thought out business plan is still a good tool, but not for proving a concept, and not for a basis for planning. It’s great for flexing your brain and for going through different scenarios and business models. It’s great when it helps you realise that a new BMW after the first year in business might not be such a good idea. But you shouldn’t invest too much time in predicting the future. Better start building the future step-by-step.
What is the reasonable period to make plans for? For us, it’s three months. And we’re not shy about preaching it. That’s why the Teamweek timeline zoom-levels are divided into week’s, month’s and 3-month’s views. Our own 8-year experience in developing Toggl (and more recently, with Teamweek) shows that these three are the most useful and relevant periods, for which planning is reasonable – and realistic.
Here are our suggestions on how to approach flexible planning:
These are the things that influence the development (and the whole concept) of Teamweek.
1- Draft the plan after deep study on it.
2- Since changes are constant, keep the way open to change at anytime as per market trend.
3- Review plans frequently for better change.
4- Review case studies on similar subject.
Able to change in any time as per any changes happen