Ever felt like this before?
"It's 7pm. Everyone else has gone home for the night...
...but we're burning the midnight oil again. The new requirements keep piling up, but the deadline doesn't move.
I can't get a decent set of requirements, but I'm supposed to estimate how long it's going to take to build the thing that my bosses can't even describe on paper. People don't seem to know what they want, only what they don't want.
We're not big enough to have an MIS department, which makes me the MIS department. The mail server just went down and I had to spend all day fixing it. I got no coding done today.
How am I supposed to estimate how long it takes to build something when we've never built it before? Every new feature is, by definition, new.
I know deep down there's no way we're going to make our schedule, but if I speak up, I'm a complainer.
My bosses schedule my time without checking with each other, so I either please one and not the other, or please neither. My input into scheduling is that once a week, I get a schedule print-out dropped on my desk.
I have this sinking feeling that we're just not going to make it."
The truth is, your project manager does want you involved in scheduling. Unfortunately, conventional scheduling tools make that difficult, if not impossible. It's hard enough for one person to move tasks around without breaking dependencies, let alone pass the file around to the whole team. Current tools make it extremely difficult for a project manager to get the team involved, other than with paper Gantts and weekly meetings.
We know that having the whole team involved in planning and scheduling makes for a stronger, more realistic plan. That's why we built Devshop for the whole team, not just the project manager. But don't worry, we're not adding more work to your already full plate. Devshop gives you an open window to contribute to the schedule, without adding more demands on your time.
You know and we know that the things that can take you away from your project obligations aren't under your control. The fact is, you have to put down what you're doing to go fix them anyway. That's part of being a team. But at least we've figured out a way to make that visible to everyone and part of the planning process, so you don't have to be the bearer of bad news.
Devshop watches the trend of distractions in the past to help you predict the likely trend in the future, and schedule around it.
By accessing this site, or by using any of its features or services, you confirm your agreement with and acceptance of the Terms of Service for this web site.