Joel Spolsky:
Realistic schedules are the key to creating good software. It forces you to do the best features first and allows you to make the right decisions about what to build. Which makes your product better, your boss happier, delights your customers, and—best of all—lets you go home at five o’clock.
CTO at
Comments
I completely agree, which is why I’m a huge proponent of Scrum / Agile Development.
More here:
http://en.wikipedia.org/wiki/Scrum_(development)
Trevor10 July 08 at 1:51 pm
Hi Trevor,
I’m using Scrum right now in my company. Even if the process is interesting it is not without flaws. Especially when you have lots of people (and teams) to synchronize for releases.
Joel don’t use Scrum.
Frederic Brunel10 July 08 at 1:55 pm
I completely agree, which is why I’m a huge proponent of Scrum / Agile Development.
More here:
http://en.wikipedia.org/wiki/Scrum_(development)
Trevor10 July 08 at 1:51 pm
Hi Trevor,
I’m using Scrum right now in my company. Even if the process is interesting it is not without flaws. Especially when you have lots of people (and teams) to synchronize for releases.
Joel don’t use Scrum.
Fred Brunel10 July 08 at 1:55 pm
Just read up on the EBS process and it sounds pretty interesting. On the surface, the process shares many similarities with Scrum. Will look into it some more.
Initially our company had a few issues with Scrum as well. We had a large dev team, some remotely, working on multiple projects which required multiple releases. However we were able to adapt the Scrum philosophy into the way we work, sometimes even breaking down the teams into smaller Scrum groups if necessary.
Thanks for the post. Always an interesting read.
Trevor10 July 08 at 2:56 pm
I have the exact same situation, multiple projects, dependencies, and people working remotely. It’s really not easy to manage.
I’d be glad to hear more about your experience with Scrum in such situation.
Frederic Brunel10 July 08 at 3:35 pm
Just read up on the EBS process and it sounds pretty interesting. On the surface, the process shares many similarities with Scrum. Will look into it some more.
Initially our company had a few issues with Scrum as well. We had a large dev team, some remotely, working on multiple projects which required multiple releases. However we were able to adapt the Scrum philosophy into the way we work, sometimes even breaking down the teams into smaller Scrum groups if necessary.
Thanks for the post. Always an interesting read.
Trevor10 July 08 at 2:56 pm
I have the exact same situation, multiple projects, dependencies, and people working remotely. It’s really not easy to manage.
I’d be glad to hear more about your experience with Scrum in such situation.
Fred Brunel10 July 08 at 3:35 pm