Software Planner is an award winning application lifecycle management (ALM) tool that helps Information Technology (IT) departments manage all components of software development including managing customer requirements, project deliverables, test cases, defects, and support tickets.

Coupled with collaborative tools like document sharing, team calendars, interactive dashboards, knowledge bases and threaded discussions, teams begin communicating more effectively and begin delivering solutions quickly and with high quality.

Used by over 70,000 users in 24 countries, Software Planner helps great companies like Acer Computers and Procter and Gamble manage their software projects with maximum effectiveness. 

Defect Tracking

Most software projects fail to deliver on-time and on-budget.  To reduce the risk of failure, project managers should implement defect tracking measurements as well as project management measurements, allowing them to more accurately estimate projects and to enhance the quality of releases.

The key to efficient defect tracking measurement and project management measurements is to first determine what goals you are trying to accomplish and what problems you are attacking.  Many organizations waste time and money by measuring more things than are necessary.  Before beginning a measurement strategy, determine the goals for your measurement.  Here are some common reasons for not delivering on-time and on-budget:

• Software coding efforts are not properly estimated
• Testing efforts are not properly estimated
• Software quality is poor, therefore the testing duration is longer than need be
• Customer changes impact the software project, thereby extending the project dates

Attacking the Common Problems

Software Coding Efforts are Not Properly Estimated
This problem normally arises due these issues:

• Customer Requirements - To properly estimate coding effort, you must create solid customer requirements.  The requirements must contain adequate detail to allow the programmers to create detailed designs.  From a measurement perspective, you should track the amount of time it takes to develop each customer requirement. Track both estimated and actual hours so that you can use this information to improve future estimates.
• Detailed Designs - It is impossible to estimate coding effort without creating a detailed design.  The detailed design allows the developer to think through all the tasks that must be done to deliver each requirement. From a measurement perspective, you should track the amount of time it takes to develop each detailed design. Track both estimated and actual hours so that you can use this information to improve future estimates.

Testing Efforts are Not Properly Estimated
This problem normally arises due these issues:

• Test Plans - Once the customer requirement and detailed design is created and estimated, the test leader should create a detailed test plan that estimates the testing effort.  This is done by thinking through the test cases that will be created based on the requirement and design. From a measurement perspective, you should track the amount of time it takes to develop each test plan. Track both estimated and actual hours so that you can use this information to improve future estimates.

Software Quality is Poor
This problem normally arises due these issues:

• No Code Reviews - If regular code reviews are not done, there is a much higher chance of delivering software with poor quality.  For large projects, these problems are compounded over time, so it is best to do code reviews early and often (at least weekly). From a measurement perspective, you should track the amount of rework time required due to failed code reviews.  This can aid you in planning for rework on future projects.
• Failed Smoke Tests - By running weekly smoke tests, you can shorten the testing phase as issues are caught early in the coding and testing cycle.  From a measurement perspective, track the number of test cases passed and failed during smoke tests, week by week.  The goal is to reduce the number of failed test cases as the project progresses.
• Defect Tracking - As testing commences, track the number of open defects vs. total defects to help predict project release dates.  Track the number of defects found during code reviews vs. test case execution.  This will help track and improve estimation accuracy.  Track the percentage of total defects before product release, as this will help assess product quality.

Customer Changes Impact the Software Project
This problem normally arises due these issues:

• Missing Change Control Processes - As a project progresses, clients sometimes ask for features to be changed or for features to be added or removed.  Before making any changes to the project, each request should be thoroughly investigated and a risk assessment should be done for each request.  If changes are necessary and agreed upon by the client, project timelines are adjusted.  From a measurement perspective, track the number of change requests, how many were approved vs. rejected, and the effort for estimating reviewing and assessing each change request.  This information can be used in future projects to predict the number number of change requests that are approved and estimated as to build time into your projects to mitigate that risk.

Consider using a web-based Solution to Manage the Software Lifecycle
When choosing a solution, look for one that is web-based and manages all phases of the software lifecycle, including customer requirements, test cases and defect, bugs and issues.  Document sharing and integrated discussion forums are a plus.

How is Software Planner different from other ALM products?

Single tool - Software Planner provides features for managing all phases of the software development lifecycle within a single integrated tool. Most ALM vendors require you to purchase separate products (or suites) that require separate licensing, which can be very costly.

Project Methodology Independent – Software Planner works well with any project methodology including Agile, Waterfall, Iterative, and Spiral. It does not force you into a specific methodology; it embraces your chosen methodology.

Feature Based Pricing – Some teams need to manage all phases of the lifecycle, while others just need to manage specific areas (like defects, test cases, customer specifications, etc). Software Planner allows you to purchase its features ala cart so that you pay for only the features you need.

Concurrent Licenses – Most ALM vendors offer only NAMED user licenses, requiring you to purchase a license for every person that uses the software. Software Planner provides concurrent licenses; you purchase only the number of users you wish to simultaneously connect to the software. Concurrent user licenses allow you to setup an unlimited number of users and normally require about 1/3 the licenses as the traditional named user license.

No Hassle Pricing – Software Planner’s competitive pricing is published on our website and does not change from one client to another. We offer consistent discounts based on long term commitments and volume purchases.

Future Product Versions at no Cost – Our Software-as-a-Service (SaaS) clients receive future products at no additional cost. Our Enterprise clients in good standing (paid annual support) also receive major and minor versions at no additional cost.

Backed by Outstanding Support – Pragmatic Software’s support enjoys a 92% customer satisfaction rating. Our core competencies are built around providing excellent support. By providing searchable knowledge bases and an easy-to-use support ticket system, you can expect to receive a support follow-up with 1 to 2 hours during business hours. Our support engineers are polite, professional, and quick to react to any questions or issues you raise.