How software process can be improved?

I will go for identifying the right mix,as the first step in approaching a software process improvement initiative in order to realize the greatest outcome is to identify the right mix which includes :-

• quality principle,
• operational method, and
• improvement technique.

Identify, define suitable measures for every phase of life cycle of SW development, collect the data, base line the measures, reviw of the projects through Quantitative project management.

I will go for evaluation of the  success of the project after completion and always avoid repeation of the problems which came across during execution of the project, which will help to improve the software development process.

           As a lead, only monitoring the resources, you wont's get expected output, you should be work as a team and should provide suggestion, advise as and when needed.

           If the lead concentrates only on monitoring... it will result in against  as well (sometimes). the leader should understand that everyone is a leader in themselves and as a leader he/she needs to provide a proper guidance to resources  to get proper work done out of the resource.

          The ideal leader should be strong in decision taking and polite in speak (Not Khadus), the one is having the said combination can become a very good leader.

As defined above it is a set of activities, methods, practices, and transformations. Most of the answers give us efficiency, not improvement as asked in the debate.

Improvement is altering the process altogether to make things better. Efficiency is to increase the output with the same input. Though these two are an overlap, careful analysis reveals a distinction between the two.

So to improve the development process, it is essential to question periodically the necessity of each of the activities, methods, practices and transformations etc.

MOst importantly, as we gain more and more experience in developing software, we must be able to define the so called common components - small blocks of code that can be re-used. It should be similar to the nuts, bolts, washers, geared wheels etc that we keep re-using them in a mechanical machine or a civil enineering construction. In software projects also, we need to continuously keep identifying these small units of codes with a specific purpose and keep using them.

It is nothing new, a very old concept, but most of the time no one makes an effort to re-use or develop keeping re-usability in mind.

Always follow Agile methodology and keep enough room for last minute changes.

Discipline in Requirement Gathering and Analysis, Coding, Testing, Design, Architecture combined with right Skill, the process improves continuously.

According to me there should be adoption of loose processes, which can provide maximum flexibility. In the era of internet it is increasingly becoming “the” environment & the global marketplace in which competition takes place.(e.g., software for the Internet, multimedia software, and more generally software for the mass market). One should adopt a lightweight process support, manages process deviations, supports geographically distributed workgroups, and handles nomadic users. It increases system flexibility by allowing developers to explicitly deviate form the modeled process, still continuing to control that the most relevant constraint regarding the overall process are verified.

In my opinion select any process improvement methodology to meet the goals. But process to follow\meet the goal should be flexible or can tailored as per project need.

 Its also stated in CMMI V1.2, that specific practices should be seen to achieve a goal, not as a derived path to reach specific goal.

We all say we should do this and that and many more other things. But actually that's the formality. I feel proper Project Management will lead to successful and quality full product.

Software development has become a bunch of jargons.  Instead of serving real world solve its problems, these jargons add to them.  Customer deciding to get computerisation is first confused and then guided to a new destination in a different vehicle!  An improvement required is that virtual solutions should really solve real problems and prove the idea of computerisation is worth taking a ride!

Project management which basically just tracks the project's progress has to be coupled with the ongoing Quality results and has some provision to capture the lessons learned from last time.

This is to make sure that the progress as well as the quality will be taken care of.

Analysis Completely And Do Proper Paper Work. Analysis All Need Of Customer And Try To Find Out Cleary What The Actual He Want. Ask Questions That Are Realted With Future Enhanchments Designing And Developing Explain Process To Client. Start Or Choose Single Project At A Time and Complete It... Manage Your Human Resource Better.Analysis Completely Each And Every Need And The Shortest Way To Reach It...

We can go ahead and write pages on quality/processes can be improved, but it will remain on paper, if it doesn't reach to the grass root level, it definitely will fail. SO training them would be the first point.

the second point I feel is getting the right people to decide on what kind of process should a particular project should follow. All projects are different. and different projects should have the liberty to folow whichever method they seem appropriate for their development.

whenever a activity is going to be start ,entry and exit criteria must be known of that activity.

entry criteria means the input to that activity .example before the testing phase test cases must be there.

Building a quality process is about laying your process..and fine tuning it.

I have been appointed as an MR for my current company and i have implimented the quality management system ISO 9001-2008.During the implimentation the major factors i learned was Audting your companies each and every component for continual improvement and building a system for Corrective and preventive actions.

Management always plays a vital role in QMS.

Building a quality process is about laying your process..and fine tuning it.

I have been appointed as an MR for my current company and i have implimented the quality management system ISO 9001-2008.During the implimentation the major factors i learned was Audting your companies each and every component for continual improvement and building a system for Corrective and preventive actions.

Management always plays a vital role in QMS.

The best way to improve processes is on Integrated Multidimensional Analytical platforms that allow services such as SAP and othe ERP systems to dump their data for analysis. SAP type systems have architectural limitations. Use of Integrated Analytical systems that merge with SAP and other ERP's will improve processes