I'm a developer in a very small startup consisting of 6 people, and I have decided to cure our lack of organization now that we have clients.
To give a little context, here is our organization:
- 2 junior developers (myself included)
- 1 senior business specialist
- 1 junior seller
- 1 senior seller who's the boss
For the last whole year, we had absolutely no organization. Everything was complete anarchy, and we were all over-working. We often miss deadlines set a long time in advance, lack visibility over our workloads and the business specialist is nearly in nervous breakdown. :D The only thing keeping stuff in check was my huge gantt chart I had to update a lot.
So we decided to get back on what we did before:
- A scrum board. (our business specialist was fed up with the "hippie" side of Scrum and lobbied to stop all kind of meetings, discussions etc to spend more time working). But as always it's working great for the dev but the others need very clear workload view to understand how many things they have to do for the next month or so.
The problem is that I know that it can't work, as I was the one managing the Gantt chart for the last year. Fixing set tasks doesn't work when you build software, as we underestimate time too much because of pressure. Also, the gantt chart is only good at the end of the project, after 300 successive updates.
So should I try to convince everyone to go for the more frightening Scrum way of "planning" stuff, without set dates for sub-tasks completion nor visuals for the next month workload per member, etc? Or should I just accept to build yet another fake Gantt chart to reassure everyone, making them believe we can plan one year in advance the life of a software development project? Or is there another way?