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. 

Software Change Management

Software product development incurs change.  For solid change management, it is best to have a Change Control Board.  The Change Control Board normally consists of the project manager, client manager, development (programming) manager, quality assurance manager, user documentation manager, and support manager. 

As new changes are requested, the Change Control Board analyzes the risks and rewards of the proposed change.  They analyze how the change affects the overall schedule, costs, and feature set. 

Below are some guidelines for the Change Control Board and details on how to best apply change management:

1. OK to say "No" - If the project team has done a good job of collecting requirements and managing the software life cycle, many features have already been reviewed and prioritized before coding begins.  If the new requirement is not worth the time of analyzing it, then it is not worth the time to implement it, therefore, it should be rejected immediately.  Normally, a good Change Control Board will say "No" more times that it says "Yes", as to ensure that only critical changes are implemented.
2. Changes should be Bundled - A large number of small changes, when done independently, can greatly affect the project timeline because each one affects many areas of the system (analysis, coding, testing, user documentation, support, etc).  To gain economies of scale and effective use of personnel, it is wise to document a set of changes at one time and include them into a bundled release.  By doing this, you eliminate a lot of the convergence needed with implementing each feature separately.
3. Eliminate Bureaucracy - Some Change Control Boards are tainted by individuals that just like to say "No" for the sake being in charge.  This can bring ill-will to a project, when it seems as if the Change Control Board is not making decisions that are in the best interest of the project.  To eliminate this problem, educate all members of the Change Control Board before the project begins. Ensure they understand that there will be frivolous changes that will be submitted as well as legitimate changes necessary for the product to be marketable and to meet the needs of the business.  So as each new change is suggested, have a risk/rewards discussion that documents the business reasons for the change and the risk associated with the change.  Documenting and publishing your findings for each change request provides understanding and buy-in from members that requested the change.
4. Document Changes - Document each change by first assigning the change request a unique tracking number.  Then have your team do an analysis of the risk/rewards for the change and document that.  It is wise to use an on-line change management solution that allows you to track the changes and manage the workflow of it (reviewing, approving and rejecting changes). 

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.