Click here to Skip to main content
15,891,762 members
Please Sign up or sign in to vote.
1.00/5 (2 votes)
See more:
Hi..we need one open source tool to improve our agile model.this tool must be enterprise wide.pl suggest.
Posted
Comments
ZurdoDev 8-Jan-15 11:56am    
what do you mean by improve your agile model?
Caroline91 8-Jan-15 12:15pm    
We have daily interactions with our onsite counterparts and emails play major role in our communication. Now we are looking for some tool which effectively manages our projects status, issues, timelines rather than just sending emails

You can use much any issue-tracker or bug-tracker tool[^] you can find (this[^] is also helpful). But you migh look on these[^] which are tools made especially for agile method. Agile project management is an interesting approach as agility is not in line with gnatt charts and such concepts. So actually you will need to develop your own way to use one or th eother tool to better support your process.
 
Share this answer
 
Comments
Caroline91 8-Jan-15 13:52pm    
Hi..can anyone give me some specific tool?
Sergey Alexandrovich Kryukov 8-Jan-15 14:40pm    
You don't need too specific tools too much. My own advice would be: don't get obsessed with ready-to-use methodical recipes, critically review them and use more common sense. Pay more attention for your work then for ceremony — this was one of the motives for Agile approaches.
—SA
Zoltán Zörgő 8-Jan-15 14:52pm    
Sorry, but you will need to assess the tools one by one. You know your organisation culture, your partner's culture, your internal methods and way of working. If you only want to replace email with something better for such message exchange with your partners, you better step only one step at a time: put a bug-tracker in place. Agility is just this: act and react. Please take the time at least to review the wikipedia list to filter them by feature and platform, and try 3-5 most promising..
Sergey Alexandrovich Kryukov 8-Jan-15 15:16pm    
Exactly. I also explain why specific tools can even be bad.
—SA
Sergey Alexandrovich Kryukov 8-Jan-15 15:15pm    
Please see also Solution 2.
—SA
Sravs91 asked:
Hi... can anyone give me some specific tool?
Please see my comments to Solution 1.

Now I want to post a separate answer, to explain why "specific tool" would be a bad thing, and non-specific one would be much better. By one simple reason: Agile or other methods come and leave, and your working artifact, development asserts stays with you for a long time.

In all cases, you should start from non-specific tools: revision control, issue tracking, single-click batch automatic re-build, some testing facility, the method of development and support of prototypes (it's a very common mistake, not to support prototypes when they already played their prototyping roles), development and support if test projects and facilities. I would also add: good content management system for documenting, so every one would document in the ways integrated with the code base, not just technical writers. (It's pain to see that people thing they have gone "Agile" yet documenting in Office, one of the most inappropriate tools, totally unstructured, from the point of view of software development.)

Now, I think everyone should understand that those development method literature, Agile or not, is the… pure pseudo-science. Don't get me wrong: it's very useful to read it: the authors share serious experience and give very good, often wise (and often not) ideas. It's a very, very good idea to share ideas and experience. It's a great idea to formalize development and enforce some disciplines. But those authors don't just share, they dictate. Again, I feel that they understand themselves that this would be wrong, they just fail to make it clear. Too many developers and managers have been mislead by "strict" science-like style of this literature, ignoring the fact that there is no scientific methods at all, and there is no solid, even experimental proof. Actually, agility ideas is a considerable positive step, but still there is nothing scientific; and there is not a silver bullet. Developers need to use more of their brains, common sense, understanding specifics of their goals, develop experience and critical thinking. Get sober!

—SA
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900