ActiveCollab for Agile
Page: 1
Recent posts in this topic
Could someone describe here best practices of using aC for Agile development process?
Thank you!
Thank you!
Ilija Studen
on Oct 22. 2007. 8:36 am
Hi errd,
I see there is no replies to this topic. Not everyone knows what Agile is and/or how you applied it within your organization. Can you please describe your workflow in more details? That could help us have a clearer picture of your needs...
I see there is no replies to this topic. Not everyone knows what Agile is and/or how you applied it within your organization. Can you please describe your workflow in more details? That could help us have a clearer picture of your needs...
activeCollab team member | LinkedIn
thomas.sittig
on Oct 22. 2007. 9:09 am
a short answer to your question, but surely not realy helpful: we doesn't going the agile-way of life at our company. but i would realy like to read other stories about this theme in combination with ac.
but i think, after the small thing i know about agile development and scrum, ac is not the best solution for this. correct me if i'm wrong, but you need a big bag of tasks (user stories) even for a relative small project. technicaly possible, but ac doesn't do a good job to visualize this informations in this size.
i would like to see a much better integration of tasks, tickets, milestones and all the other, project-related informations to the calendar for this cause.
but i think, after the small thing i know about agile development and scrum, ac is not the best solution for this. correct me if i'm wrong, but you need a big bag of tasks (user stories) even for a relative small project. technicaly possible, but ac doesn't do a good job to visualize this informations in this size.
i would like to see a much better integration of tasks, tickets, milestones and all the other, project-related informations to the calendar for this cause.
Try Mingle for Agile Project Management from Thoughtworks: http://studios.thoughtworks.com/
We're using aC for our XP/Crystal Clear projects, and its working great.
The user stories are tickets, and we simply assign those tickets to our next milestone. As the tasks within the tickets are done, that use case is complete and our manager is able to see how the scheduled tickets are being completed.
Clearly, this could be acheived with index cards, but not all developers are in one office, so this gives visibility to all of us.
The user stories are tickets, and we simply assign those tickets to our next milestone. As the tasks within the tickets are done, that use case is complete and our manager is able to see how the scheduled tickets are being completed.
Clearly, this could be acheived with index cards, but not all developers are in one office, so this gives visibility to all of us.
We are working exclusively Agile and see AC as the perfect tool to support that.
The most significant issue to understand regarding Agile is that it's trying to avoid the military/hierarchical system a lot of companies still rely on. This tool supports the team and modular approach similar to object oriented programming in itself.
You could actually use this tool in a waterfall method as well, but waterfall (hierarchical) methods rely on hand-offs and sign offs, vs collaborative type approaches. It is (obviously) possible and sometimes needed to do both methods and mix them.
The last thing anyone should do is mindlessly "go by the Agile book" that would be counter productive in case team members are not capable of supporting the approach.
In our case the tool helped us to even break large projects into smaller team projects and allow them to come up with collaborative solutions faster and better. Team members in a sense compete against each other to achieve the best results and are free to discover the best solution as well as challenge the business requirements.
The most significant issue to understand regarding Agile is that it's trying to avoid the military/hierarchical system a lot of companies still rely on. This tool supports the team and modular approach similar to object oriented programming in itself.
You could actually use this tool in a waterfall method as well, but waterfall (hierarchical) methods rely on hand-offs and sign offs, vs collaborative type approaches. It is (obviously) possible and sometimes needed to do both methods and mix them.
The last thing anyone should do is mindlessly "go by the Agile book" that would be counter productive in case team members are not capable of supporting the approach.
In our case the tool helped us to even break large projects into smaller team projects and allow them to come up with collaborative solutions faster and better. Team members in a sense compete against each other to achieve the best results and are free to discover the best solution as well as challenge the business requirements.
www.gfxi.com
mellis@adknowledge.com
on Jul 22. 2008. 4:34 am
Using tickets for stories is cool but the other key aspect of agile project management is measurement: what's the velocity of each person? how accurate are their estimates? what confidence do we have on this sprint? etc. Would love to hear how people do this. See liquidplanner or attask for examples.
mellis@adknowledge.com:Using tickets for stories is cool but the other key aspect of agile project management is measurement: what's the velocity of each person? how accurate are their estimates? what confidence do we have on this sprint? etc. Would love to hear how people do this. See liquidplanner or attask for examples.
That sounds a bit more like Scrum, which is Agile, just a lot more metrics-oriented.
