Below are 40+ questions to ask about software product history, current product releases, future software products and future software direction.

SOFTWARE PRODUCT HISTORY

What is the software product history? How has it got to where it is today? When was the software originally developed / first released? Has the software product been developed solely internally? Or has it been developed by acquisition or integration with other software? If so, which software, and when? Is the integration process complete? Or are there outstanding issues or faults to resolve? Has the product been completely re-written at any stage? What software and database was it originally developed in? What other software/database combinations has it been migrated to? What software/database is currently used for product development? Which software/database combination receives upgrades first? Which is the safest software/database combination in terms of fewest problems, bugs, most stable environment? What were the key stages of the product development? How many times has the software product been upgraded / revised? And what were the dates and key items included within each release?

CURRENT PRODUCT RELEASES

What is the current version number? When was it released? What was included within the upgrade? Can you have a schedule of changes included in the last release? When is the next release due? What’s in this release? How many releases are issued per annum? How do customers obtain releases? How straightforward is it for customers to implement? Would the customers say the same as the vendor? How does the vendor decide what to include in each new release? Who decides what should be in each new release? Who provides input into this process? Is it internal within the vendor or are customers, user groups involved? What are the time scales for new releases (and the stages within the release)? How do the vendors test the new release, before it is issued? Can you see the testing evidence and results eg test scripts, unit testing, usability testing? What is their product development methodology? Can you see the vendor’s fault list? How many faults or bugs are outstanding for each release?

FUTURE SOFTWARE PRODUCTS

Where is it going? What is the direction of the product? What new functionality will be added? What functionality gaps will be plugged? Do the vendors have a product development ‘road map’ for the next 3 years? And can you see it? Does the vendor have a ‘vision statement’ for the software product?

FUTURE SOFTWARE PRODUCT DIRECTION

Where is the vendor heading to from a technology point of view? What new products is the vendor planning to introduce? What new markets is the vendor planning to move into? What products is the vendor planning to discontinue, dispose of or no longer support in the future? And what are the time scales? For more due diligence checklists and questions, visit: Software vendor support, Implementation support, Reference site visit checklist, Vendor accounts, Vendor personnel, Vendor software product development, Software payment terms, Final software decision, Software agreement checklist

Due Diligence - Vendor Product Development

For learning more about a software vendor’s product history, development and future

Axia Consulting

© 2020 Axia Consulting Ltd. All rights reserved.
17 New Road Avenue, Chatham, Kent ME5 9RL, United Kingdom Contact Us
Below are 40+ questions to ask about software product history, current product releases, future software products and future software direction.

SOFTWARE PRODUCT HISTORY

What is the software product history? How has it got to where it is today? When was the software originally developed / first released? Has the software product been developed solely internally? Or has it been developed by acquisition or integration with other software? If so, which software, and when? Is the integration process complete? Or are there outstanding issues or faults to resolve? Has the product been completely re-written at any stage? What software and database was it originally developed in? What other software/database combinations has it been migrated to? What software/database is currently used for product development? Which software/database combination receives upgrades first? Which is the safest software/database combination in terms of fewest problems, bugs, most stable environment? What were the key stages of the product development? How many times has the software product been upgraded / revised? And what were the dates and key items included within each release?

CURRENT PRODUCT RELEASES

What is the current version number? When was it released? What was included within the upgrade? Can you have a schedule of changes included in the last release? When is the next release due? What’s in this release? How many releases are issued per annum? How do customers obtain releases? How straightforward is it for customers to implement? Would the customers say the same as the vendor? How does the vendor decide what to include in each new release? Who decides what should be in each new release? Who provides input into this process? Is it internal within the vendor or are customers, user groups involved? What are the time scales for new releases (and the stages within the release)? How do the vendors test the new release, before it is issued? Can you see the testing evidence and results eg test scripts, unit testing, usability testing? What is their product development methodology? Can you see the vendor’s fault list? How many faults or bugs are outstanding for each release?

FUTURE SOFTWARE PRODUCTS

Where is it going? What is the direction of the product? What new functionality will be added? What functionality gaps will be plugged? Do the vendors have a product development ‘road map’ for the next 3 years? And can you see it? Does the vendor have a ‘vision statement’ for the software product?

FUTURE SOFTWARE PRODUCT

DIRECTION

Where is the vendor heading to from a technology point of view? What new products is the vendor planning to introduce? What new markets is the vendor planning to move into? What products is the vendor planning to discontinue, dispose of or no longer support in the future? And what are the time scales? For more due diligence checklists and questions, visit: Software vendor support, Implementation support, Reference site visit checklist, Vendor accounts, Vendor personnel, Vendor software product development, Software payment terms, Final software decision, Software agreement checklist
Due Diligence - Vendor Product Development For learning more about a software vendor’s product history, development and future
© 2020 Axia Consulting Ltd
All rights reserved. Contact Us

Axia Consulting