0 Software Project Maintenance

Thursday, October 8, 2015 Labels: , , ,
After completing a software project/product, its maintenance becomes very tricky if it's not properly taken care of.

Following is the high-level check list to consult to:

1. Thinking about maintaining the software for the future from the early stage is very important and also define some basic procedures.

2. Technical skills needed for the maintenance work is crucial but knowing the business side is important too. Any gap between the two is the disaster recipe. 

3. Unit testing, proper release management and continuous integration are some of the necessities to make software operational for the longer period of time with less hassle. One can also maintain the software without any of these fancy techniques by following the industry's basic practices and personal experience. Though automated testing is reduces the risk of software crashes also.

4. Technology and infrastructure enhancement with the passage of time for the software product is also very important. If it's neglected software would be a story from the past.

5. Employee retention and training mechanism (making dependable) for the new comers is very important for the success and keeping the product for the longer period of time.

 6. Learning and training for employee with the passage of time is also important so that they can understand and adopt new trends as per the requirement.
Read more

0 Software project planning and management pitfalls

Friday, May 1, 2015 Labels: , ,

When it comes to software delivery on time, many different factors come to action. Some of them are as follows:

1. Bidding on a project by committing to client's timeline
In this case a timeline is committed before analyzing the requirements completely. In this case after getting the project plan is devised to complete the project within that time frame. Now technicall resources are arranged, research and development is made part of this timeline as if its going to be smooth ride and developrs will overcome everything in allocated eight hours and are sole responsible for timely delivery of project. Often raw requirements are taken as project plan and accordingly deliverables are scheduled.
This approach is not going to meet the time frame already committed.


Read more
Waqas Sadiq © 2014