What do we need to measure for a "new" agile software project?
480216
The project velocity (or just velocity) is a measure of how much work is getting done on your project. To measure the project velocity you simply add up the estimates of the user stories that were finished during the iteration. It's just that simple. You also total up the estimates for the tasks finished during the iteration. Both of these measurements are used for iteration planning
157228
If the metrics are being produced by some-one on the project team other than the project manager - perhaps a "project controls" person, then I would accept the project manager to perform some level of audit to ensure the data he's getting is appropriate.\n\nThere could still be another level audit/review, probably by the project sponsir, if the project has a high enough risk associated with it.\n\nIf the project manager is producing their own metrics directly, then it would seem to make less sense that they would formally audit their own work, but of course they would be checking their own calculations.
529226
I am assuming primarily that you are talking about programmers. Being that I am one, I can tell you that some of the tools used to gauge productivity in companies is the good old "number of bugs versus how many lines written" method. If someone has 3 bugs in 20 lines of code, they are said to be not as productive as someone with 3 bugs in 200 lines of code. \n\nHowever, I will tell you now that in the world of programming there is a serious debate raging on about if measurements like this truly work for showing who is better or not. \n\nI rather determine worth and productivity based on if the programmer is willing to work with you, wants help on occasion, knowledgeable in general, and willing to work hard in fixing any known bugs.\n\nGeneral rule of thumb, if you find a programmer working hard, reliable, there at their desk every day willing to work with you to solve problems, they are worth their weight in gold. Even if they can't slam out 1000+ lines of code a day. Besides, what is lines of code when you can cut and paste?\n\nThis is only one of several tools, but a popular one you will hear.
242391
your end result. your project should have answered some sorta question the conclusion should be that answer.
1022319
first get a patent for a new tech .produce it give it to the testers and reanalyse it .register your product. if it is a software release a beta version and look for views then release the original version(i suppose these are logical steps)
513703
The fact that you are writing an e-voting system is not relevant to choosing a development methodology.  These factors will be better indicators for which you should choose:\n\nscope - what is the scope of the project.  If you evoting system is simply a web page with text, two voting buttons, and a back end cgi that tallys votes, then a simple waterfall would work fine since the scope is minimal.  If however, your app will render it's pages with voting options stored in a database, and track users via an account (which means you need to keep a db of users and/or tie into some other source for your user info), provide an admin interface to allow admins/users to enter new voting choices and to review current tallies, and the software will have to pass a certification process (if it's being used to vote for "official" things), then the scope of the project gets much larger, and you may have to look at a more iterative approach.\n\ndeveloper resources - related to scope.  How many resources does your project require?  What are the experience level of those resources.  If it's a team of experienced individuals, the methodology used could be quite different than a team of inexperienced developers, or one developer.\n\ntime - how much time to you have to complete the task.  Some methodologies are better for quickly cranking things out, but you wouldn't necessarily choose them if you have plenty of time to accomplish the task.\n\nTake a look at the above variables, come up with values, and that will guide your decision on which medthology might be best.
467520
WOW! Tough one.\n\nProject overruns can be caused by personalities not getting along and working together or using the wrong tool and finding it out after the fact or clients making huge changes to what they want.\n\nThe only thing you can realisticly do to help lessen software project problems is to be prepared.\n\nDo the homework on client needs.\n\nDo the compliance homework for the platform you're going to use.\n\nDo your homework to follow industry standards in design, for example, on MS the Composite UI standard.\n\nDo your DBA before hand, find flaws.\n\nDo your psuedo code run throughs before hand, find logic errors.\n\nHave a really code project manager software, with resource allocation and finiacial features, along with the charting, etc to always gain a view of how on time/bugdet the project is.  \n\nMS Project is still the best.  \n\nI tried a freebie mimicker and it was awful and that one if rated one of the best freebie project managers.
409004
If you are working for an employer, first, document your hours and what you've spent your time on. Keep track of the number of pages/lines of code you've completed -- even though this metric is totally arbitrary, it gives some indication of your work. The other thing you can do is to provide a clear indication of where you want to be, and ask how to get there in your review. Haven't had a review? Politely ask for one, then present your case -- don't ask for a raise per se, but indicate that you'd like to get further ahead in the company and present your case, gathered from above.\n\nIf you are working with clients or performing contract work, you need to develop your portfolio to make a clear case of what you are providing to your customers.
787602
it would depend on the type of application, but should include:\n- extracting statistics\n- providing user support upon request\n- operating some ticketing support system\n- provide suggestions for bugs creation and/or application\n- help with regular upgrades and new systems launch
102546
That is dependant on a lot of factors.  Including standard practice of the organization you're working with, type of project and scope of project.  Below are some links to explore.
370687
For software engineering Following testing tools are used - \n\nLoad Runner \nWin Runner\nTestDirector\nVisual Test - Specially For Visual C++\nSQA Suite \nSQA TestFoundation for PeopleSoft applications \nPureCoverage\nPurify \nTestmate \nC-Cover , ObjectCoverage - coverage tool \nBoundsChecker\nObjectTester - automatic test generation\nTestCenter\nAstra SiteTest \nITEX - Interactive TTCN Editor and Executor
410767
This is a bit difficult question cause it takes lots of factors like how many resources you have (or going to allocate for the project). Do you have a clearly defined scope of work?? System Design??? if you have answers for these then lets break to project in to phases like  feasibility study, requirement gathering, analysis, design, coding and implementation. Each phase break it in to smaller tasks like getting approvals, visiting different locations etc. \n\nNow estimate number of days your resources going to spend on each task depending on the level of experiance the resources have. Here you need consider their previous experience and keep gaps for paper work and other manual processors.\n\nOnce you arrive on total number of days, then it is easy, you calculate what is your man day cost and add your profit margin. Then multiple Man Days * charge per day, that is the price estimation and number of days is the time estimation. Make sure you have buffers in case of something goes wrong in a phase. Size of the buffer needs to justify and realistic.
591534
- Plan what your project is going to be like.\n- Estimate how much your budget cost when implementing this project(your asp.net app)\n- Choose what are the software model you want your project to implement. Is it Waterfall Approach? RUP(rational unified process)? or Extreme Programming?\n- After you have completed your project, go through your 4 phases and also designing, testing n implementation, documentation..\n- Test your functions again n again to ensure your program works well.
734911
Do you have Microsoft Works?? If so go to the task launcher they have templates and projects you can use there.
382834
There is no quick and easy way to do this. You would need to engage an agency and work with them on what/which aspects of your brand you want to measure and they will go out there to do the benchmarking for you.
720478
Its called Software Development Life Cycle [SDLC]. Begins with Requirement Planning, Documentation, Coding, Testing and Implementation.
364877
There are many different methods and programs that are used for managing project quality, Six Sigma is one that comes to mind, my company changes methods about every 18 months.\n\nstart here  http://en.wikipedia.org/wiki/Project_management\n\ngoole showed 367 million hits on the question