Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
i'm interested in project management software similar to MS Project. the project is a serious rebuild of my software. we have a bug management system already but i need to track project progress.
i don't like web-based apps so much because the data is either hosted off-site or i need to set up my own server.
i like MS Project but it doesn't seem to compare estimated time with actual time and use it to pro-rate the future work estimates.
i'd like a gantt chart & calendar view.
thank you for your help!
Please give open workbench a try.
Here's the rundown from Wikipedia.
From the list that Ben Hoffstein provided, two caught my eye - eGroupWare and Project Pier. Although those two might not meet your needs, they appear to be worth looking at for my needs.
I used primavera some time back, and I think it can do the said comparison.
I remember when Joel posted about the new Fogbugz Evidence Based Scheduling. Seems like it might be what you're looking for.
It's web-based, but Jira tracks time, and can be combined with the GreenHopper plugin to give an Agile-style Planning Board and Burn-down chart. It doesn't, however, do velocity for you.
I also used the open source tool OpenProj, worked perfect for me.
since i'm a one-man project, it became clear the best solution for me was an Excel workbook that tracks time management & pro-rates remaining tasks. the Recalculate macro updates the statistics.
Try Crew! http://www.devmynd.com/crew
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I came to a successful project with 4 years old, it is already in the production.
The problem is that, the project is not documented anymore, it depends on 2 senior developers only, they know the system, they test, they handle change of requests..
I need to know what is the best practice, or what are the main steps that I have to do in order to document all the modules starting from high level design through component analysis & design, code comments, till the configuration management.
The traditional project management processes don't give me a clear idea of how to take the control back of a an old project.
Thanks.
Senior developers will easilly get bothered if you make them write docummentation all day long so you may lose them at the end.
I would hire a technical writer / junior developer if I were you and give him or her this as a first task. I would also make him or her work closelly with the senior guys, without taking too much from their time (like aggregating questions and have a one hour session dailly or something like that).
It will probably hurt in the beginning but if properly executed should prove a good choice at the end.
Note: The level of cooperation between your senior guys and the new guy that will be doing the documentation may vary depending on some internal "political" things like if the developers feel threatened by the fact that you are trying to make them less critical to the project, how overwhealming the new guy / gal is to them and so on. So answer those questions before going for it.
Once again - it is my personal opinion on the given topic and its success will definatelly depend on various factors. So you should decide if it is a good way to go or not.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
i am normally developing either alone or with 2-3 other people. i handle almost all aspects of the business and development but as of current i am becoming overwhelmed with my client base. I need some system to help me out
What i am looking for is something that i can:
Use to manage my client contacts
Per client, manage the goals of the project im working/building on
Per client, per project, manage the bugs
Per client, per project manage support/helpdesk stuff... and then
turn those into bugs
Automate the communication of tickets and monitor email for support
stuff.
I am down to hear ANY ideas/options you have no matter how radical. :)
thank you!
We have bought the Source Code licence to JitBit Helpdesk, my colleague is in the process of adding some extra fields to support our work-flow, I have been working Visual Studio and AnkhSVN integration so that we can see bugs from VS2008/VS2010.
The user interface is functional, it can be styled to our likings, the code is a bit haphazard but the database is simple enough.
I've been using Assembla -- No complaints, and it covers just about everything -- and it's free to try.
We use HEAT from FrontRange solutions for most of the things you've mentioned. They also offer other solutions, such as CRM, etc. Nicely customizable, easy to interface to, nice self-service modules, excellent monitoring tools and auto-escalations... (and no I don't work for them. I've just been very happy with them over the last 10 years.)
Have a look at Gemini & SimplyFi
Take a look at Checkvist - it may work for you for clients/goals/plans/priorities. It is general purpose outliner and task manager.
For tickets/bugs you probably need a real issue tracker, like YouTrack.
Disclaimer: I'm affiliated with both of them.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Its a common thing to see that most of the project gets lost in-between the development due to many reasons, some which can be fixed and some which cannot. Can you please share various indicators that would point to this and feel free to share your experience that may help.
Thanks in advance.
When unpaid overtime, especially weekend working, becomes Standard Operational Procedure.
One indicator is when lot of issues start coming up in the team meetings that contradict the SRS.
Another indicator is when the TL and the PM start explaining the same requirement differently... which clearly shows that the requirement has either have not been correctly understood or mis-interpretation of it
A good link is here
One of the tell-tale signs a project is heading in the wrong direction is when the project no longer becomes a project. The definition of a project is:
The project has a well defined objective
The project has specific start and end time
The project has a customer
If any of these are not present or if they change and become no longer a project then things are heading the wrong direction. This happened to me when I was the sole developer on a project. Nobody noticed that we lost our clear objective when one of our assumptions proved to be incorrect. My work shifted from development to maintenance. It was a nightmare.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
What is the best way to retire a currently active project? I've been working on this one for a while now and I think its time to let go. Without going into too much detail, there are other projects and technologies that are way ahead now and I don't see much value in investing in it any further.
What have you done to retire a project and what is the process like?
As operating systems, compilers, etc. change, it can be difficult to rebuild old projects.
Consider creating a virtual machine that is configured to build it again, in case you need to update it for some reason in the future. Archive that VM along with the source code, etc.
Personally, I've done this before, and put up on the homepage of the project
"I no longer wish to maintain this project - if you're interested in taking it over, then feel free to email me (email#address)"
And then let someone take it over.
Is this a personal, community, or commercial/professional project?
I have had a professional prject go sour due to lack of feedback form the client. Bascially they were going at a slower pace than they should have and it got to a point where the software would be more expensive to contine than to get a prebuilt alternative. In that case i just brought in the data to show the client where their saving are and recommend to abondon. Its hard to swallow, but after a while they realize it was for the best.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
Does anyone know of any software or a good way for developers to build up a knowledge base of business rules that are built in to the software for help desk to use?
We already have a helpdesk software but we are not looking to replace this.
A wiki is definitely the way to go. Processes change, sometimes frequently, and in a fast-paced environment like a help desk a tool that allows quick, easy access and management of that type of content is extremely important to allow people to do their jobs effectively.
One of the greatest benefits I've found is the heiarchical sturcture of many wikis, allowing employees to find the correct content from a number of different customer angles.
Can you be more specific?
This may fall under "policies and procedures" management software. Here are some:
http://www.softscout.com/software/Human-Resources/Policy-and-Procedures.html
I'd like to find one that's more wiki-like or easier to integrate into a a website serving as a more general company knowlege base.
I would recommend a wiki wiht a "Wiki Gardener" role- someone who cleans up the duplicate entries and sorts.
Wiki technology with a Rich Text Editor option would useful if your Support Desk are not totally technical.
Having some structure is imperative, developing something in any Wiki that makes sense to the general editing populace, and has a low threshold to get from reading to editing. You will also possibly need a migration strategy for taking hundereds of little notes into something more readable and searchable.