jamespaden
Joined 16 years ago
Joined 16 years ago
More seriously though, thanks for the feedback. We're not sure what the best pricing is yet. $10/user/mo is in line with similar products and is a small price to pay for getting rid of unnecessary overhead and management. It might be too high though.
https://www.expectedbehavior.com/building-burndown/keep-the-...
https://www.expectedbehavior.com/building-burndown/schedule-...
https://www.expectedbehavior.com/building-burndown/many-hand...
https://www.expectedbehavior.com/building-burndown/where-tas...
https://www.expectedbehavior.com/building-burndown/you-can-o...
This is just v0.1 of the tool, so we haven't solved/built all the above yet, but maybe it shows some of our thinking process.
Some companies seem to have project managers assign daily tasks to each developer. The PMs then spend a lot of time defining the tasks and moving the schedule around. They have weekly/daily meetings with other PMs to do cross-project planning.
On the other hand, Basecamp's Shape Up (https://basecamp.com/shapeup) process defines a desired outcome with some clear parameters and a six-week deadline and simply lets the team figure out the rest. There's not a lot of project management happening on a week-by-week basis.
So my question is, what do teams in the middle of those two extremes do? How do teams spend less time on minutia of planning projects and tasks and more time doing?
Does the PM ever bother you to get the status of something, or is it always clear from the kanban board? I've seen the "bug the developer for a status update" move a lot in the past.
Agreeing on the API contract seems like a fantastic way to streamline the process!
Disclaimer: I work for DocRaptor
Mostly lurking. Primary development language/framework is Ruby on Rails.