3 ms·

I don't really like the project grouping. A developer can work on multiple 'projects' on the same day and you don't want to have to look for them on Project A

by iamgoat 16y ago

I don't really like the project grouping. A developer can work on multiple 'projects' on the same day and you don't want to have to look for them on Project A and Project B to get their latest update. Maybe add a Team layer to the mix. A user can belong to multiple teams. You can have a Dev team and an IT team. Then an overall Tech team which includes everyone in Dev and IT. Then update the dashboard to allow you to view by Team or Project. You'd have to work out a good way of explaining/displaying this to users. Additionally, it'd be great to see the last 2 updates underneath each person. Or maybe on the team view list all updates under each person for the same day (otherwise show last 3). This it personal preference, but adding different views to the dashboard would be pretty simple and would help sell me on this for my use. Lastly, I don't know how well the pricing model works by limiting to a certain number of projects. To me, users is a more important grouping and I would do pricing based on that.

subbu 16y ago
I need to think about organising the updates teamwize. I usually go with projects because most of my projects are small. That said, I will collect more feedback and see what's the best way. Interesting view on user-based pricing. Basecamp, github, and most other sites that I use personally go by project numbers. User count comes in the second level. E.g. 20 projects and up to 50 users.
- iamgoat 16y ago
  My problem with the project model is a project could be anything. If someone didn't want to pay for the next tier they'd create less projects or have 1 generic project which is the name of the company and dump everything into it. Which is what I do with the free version of FogBugz for my personal projects. A user will always be a user. One business may need 12 projects while another may only have 1 project everyone is working on. But if both have 30 users they use up the same amount of bandwidth. And as you suggested, it really comes down to how different businesses work. Some companies work faster than others where 1 project may last 2-3 days. Someone in that company would have to be on top of closing that project and the next one. Or do they create a Generic project for the quick ones and a specific project for the more long term ones? Properly utilizing Projects (and milestones for that matter) have always been a challenge for me with the project management applications I've used (Basecamp, FogBugz, etc).

by iamgoat 16y ago

subbu 16y ago

I need to think about organising the updates teamwize. I usually go with projects because most of my projects are small. That said, I will collect more feedback and see what's the best way. Interesting view on user-based pricing. Basecamp, github, and most other sites that I use personally go by project numbers. User count comes in the second level. E.g. 20 projects and up to 50 users.

iamgoat 16y ago
My problem with the project model is a project could be anything. If someone didn't want to pay for the next tier they'd create less projects or have 1 generic project which is the name of the company and dump everything into it. Which is what I do with the free version of FogBugz for my personal projects. A user will always be a user. One business may need 12 projects while another may only have 1 project everyone is working on. But if both have 30 users they use up the same amount of bandwidth. And as you suggested, it really comes down to how different businesses work. Some companies work faster than others where 1 project may last 2-3 days. Someone in that company would have to be on top of closing that project and the next one. Or do they create a Generic project for the quick ones and a specific project for the more long term ones? Properly utilizing Projects (and milestones for that matter) have always been a challenge for me with the project management applications I've used (Basecamp, FogBugz, etc).