Use the right requirements tool. Save your projects

Use the right requirements tool. Save your projects. Only 30% - 40% of projects are successful! 60% Software Project Success Rates 50% 40% E Challenged Succeeded 30% E Failed 20% E 10% 2002 2003 2004 2005 2006 2007 2008 2009 Source: Standish Group The Root Cause: Poor Requirements The vast majority of industry reports point to requirements and related issues as the chief root cause of software project problems. Top 3 factors to determine if a project is: "Poor requirements gre the source of the majority of delivered defects in Successful: Challenged: Impaired: 1. User involvement 1. Lack of User Input 1. Incomplete Requirements software applications." 2. Exec Mgmt Support 3. Clear requirements 2. Incomplete Requirements 2. Lack of User Involvement 3. Changing Requirements 3. Lack of Resources Jones, C. 2008. Applied Software Measurement: Global Analysis of Productivity and Quality, 3rd Ed. Contributer #1: Outsourcing IT Outsourcing Spend - Development and Integration (In millions of $US) 100k r The incessant drive to outsource in a bid to reduce costs and rise of distributed development has made the situation worse. Outsourcing strains project communication and collaboration contributing to poor 80k requirements. 60k 2001 2002 2003 2004 2005 2006 2007 2008 Source: Gartner 2009 Contributer #2: M&A's 15k Total Mergers & Acquisitions ull. The incredible rise in M&A's during this same period has increased complexity of development. Legacy systems need to be merged & 12k reconciled between businesses which themselves are being 9k consolidated, making requirements tasks even more challenging. 6k 2002 2003 2004 2005 2006 2007 2008 2009 Source: IQ IT Spending on the Rise US IT Spending (in billions of $US) 600 In this environment of increased 500 pressure, investments in IT have risen significantly. 400 2002 2003 2004 2005 2006 2007 2008 2009 Source: Bureau of Economic Analysis Increased Attention to Requirements Project Effort Devoted to Requirements 6% 14% And it would appear the message is starting to get through. Between 2006 and 2010 the percentage of project effort spent on requirements more than doubled! 2006 2010 Source: Gartner BUT... Success Rates Continue to Fall 50% Software Project Success Rates In spite of more IT investment and increased attention to requirements, there has been no improvement in defect rates, and project success rates continue to fall. 40% 30% 20% Challenged Succeeded - Failed 2006 2007 2008 2009 Sources: Gartner and Standish Group The Missing Link Business Analysts are using the wrong tools. "Requirements tools need to be at the top of the shopping list for any firm involved in development of software applications." "54% of stakeholders are dissatisfied with the use of Microsoft Office for requirements." "Requirements tools seem to have the biggest impact on the success of a project. " Sources: voke Market Snapshot Report (The Role of the Business Analysit) Standish Group (Extreme Chaos) Learn More Visit www.blueprintsys.com/saveyourprojects/ to read in detail why Business Analysts are using the wrong tool or watch how Blueprint, a modern requirements platfrom, improves requirements. About Blueprint Blueprint is the world leader in collaborative requirements definition and management solutions for companies looking to improve the success of critical revenue-generating projects. Blueprint transforms the business-IT relationship into a visual and engaging collaboration resulting in on-time and on-budget applications. Headquartered in Toronto, Blueprint has global sales, operations and partner presence. Visit www.blueprintsys.com. Оbuеprint define better. together. Use the right requirements tool. Save your projects. Only 30% - 40% of projects are successful! 60% Software Project Success Rates 50% 40% E Challenged Succeeded 30% E Failed 20% E 10% 2002 2003 2004 2005 2006 2007 2008 2009 Source: Standish Group The Root Cause: Poor Requirements The vast majority of industry reports point to requirements and related issues as the chief root cause of software project problems. Top 3 factors to determine if a project is: "Poor requirements gre the source of the majority of delivered defects in Successful: Challenged: Impaired: 1. User involvement 1. Lack of User Input 1. Incomplete Requirements software applications." 2. Exec Mgmt Support 3. Clear requirements 2. Incomplete Requirements 2. Lack of User Involvement 3. Changing Requirements 3. Lack of Resources Jones, C. 2008. Applied Software Measurement: Global Analysis of Productivity and Quality, 3rd Ed. Contributer #1: Outsourcing IT Outsourcing Spend - Development and Integration (In millions of $US) 100k r The incessant drive to outsource in a bid to reduce costs and rise of distributed development has made the situation worse. Outsourcing strains project communication and collaboration contributing to poor 80k requirements. 60k 2001 2002 2003 2004 2005 2006 2007 2008 Source: Gartner 2009 Contributer #2: M&A's 15k Total Mergers & Acquisitions ull. The incredible rise in M&A's during this same period has increased complexity of development. Legacy systems need to be merged & 12k reconciled between businesses which themselves are being 9k consolidated, making requirements tasks even more challenging. 6k 2002 2003 2004 2005 2006 2007 2008 2009 Source: IQ IT Spending on the Rise US IT Spending (in billions of $US) 600 In this environment of increased 500 pressure, investments in IT have risen significantly. 400 2002 2003 2004 2005 2006 2007 2008 2009 Source: Bureau of Economic Analysis Increased Attention to Requirements Project Effort Devoted to Requirements 6% 14% And it would appear the message is starting to get through. Between 2006 and 2010 the percentage of project effort spent on requirements more than doubled! 2006 2010 Source: Gartner BUT... Success Rates Continue to Fall 50% Software Project Success Rates In spite of more IT investment and increased attention to requirements, there has been no improvement in defect rates, and project success rates continue to fall. 40% 30% 20% Challenged Succeeded - Failed 2006 2007 2008 2009 Sources: Gartner and Standish Group The Missing Link Business Analysts are using the wrong tools. "Requirements tools need to be at the top of the shopping list for any firm involved in development of software applications." "54% of stakeholders are dissatisfied with the use of Microsoft Office for requirements." "Requirements tools seem to have the biggest impact on the success of a project. " Sources: voke Market Snapshot Report (The Role of the Business Analysit) Standish Group (Extreme Chaos) Learn More Visit www.blueprintsys.com/saveyourprojects/ to read in detail why Business Analysts are using the wrong tool or watch how Blueprint, a modern requirements platfrom, improves requirements. About Blueprint Blueprint is the world leader in collaborative requirements definition and management solutions for companies looking to improve the success of critical revenue-generating projects. Blueprint transforms the business-IT relationship into a visual and engaging collaboration resulting in on-time and on-budget applications. Headquartered in Toronto, Blueprint has global sales, operations and partner presence. Visit www.blueprintsys.com. Оbuеprint define better. together. Use the right requirements tool. Save your projects. Only 30% - 40% of projects are successful! 60% Software Project Success Rates 50% 40% E Challenged Succeeded 30% E Failed 20% E 10% 2002 2003 2004 2005 2006 2007 2008 2009 Source: Standish Group The Root Cause: Poor Requirements The vast majority of industry reports point to requirements and related issues as the chief root cause of software project problems. Top 3 factors to determine if a project is: "Poor requirements gre the source of the majority of delivered defects in Successful: Challenged: Impaired: 1. User involvement 1. Lack of User Input 1. Incomplete Requirements software applications." 2. Exec Mgmt Support 3. Clear requirements 2. Incomplete Requirements 2. Lack of User Involvement 3. Changing Requirements 3. Lack of Resources Jones, C. 2008. Applied Software Measurement: Global Analysis of Productivity and Quality, 3rd Ed. Contributer #1: Outsourcing IT Outsourcing Spend - Development and Integration (In millions of $US) 100k r The incessant drive to outsource in a bid to reduce costs and rise of distributed development has made the situation worse. Outsourcing strains project communication and collaboration contributing to poor 80k requirements. 60k 2001 2002 2003 2004 2005 2006 2007 2008 Source: Gartner 2009 Contributer #2: M&A's 15k Total Mergers & Acquisitions ull. The incredible rise in M&A's during this same period has increased complexity of development. Legacy systems need to be merged & 12k reconciled between businesses which themselves are being 9k consolidated, making requirements tasks even more challenging. 6k 2002 2003 2004 2005 2006 2007 2008 2009 Source: IQ IT Spending on the Rise US IT Spending (in billions of $US) 600 In this environment of increased 500 pressure, investments in IT have risen significantly. 400 2002 2003 2004 2005 2006 2007 2008 2009 Source: Bureau of Economic Analysis Increased Attention to Requirements Project Effort Devoted to Requirements 6% 14% And it would appear the message is starting to get through. Between 2006 and 2010 the percentage of project effort spent on requirements more than doubled! 2006 2010 Source: Gartner BUT... Success Rates Continue to Fall 50% Software Project Success Rates In spite of more IT investment and increased attention to requirements, there has been no improvement in defect rates, and project success rates continue to fall. 40% 30% 20% Challenged Succeeded - Failed 2006 2007 2008 2009 Sources: Gartner and Standish Group The Missing Link Business Analysts are using the wrong tools. "Requirements tools need to be at the top of the shopping list for any firm involved in development of software applications." "54% of stakeholders are dissatisfied with the use of Microsoft Office for requirements." "Requirements tools seem to have the biggest impact on the success of a project. " Sources: voke Market Snapshot Report (The Role of the Business Analysit) Standish Group (Extreme Chaos) Learn More Visit www.blueprintsys.com/saveyourprojects/ to read in detail why Business Analysts are using the wrong tool or watch how Blueprint, a modern requirements platfrom, improves requirements. About Blueprint Blueprint is the world leader in collaborative requirements definition and management solutions for companies looking to improve the success of critical revenue-generating projects. Blueprint transforms the business-IT relationship into a visual and engaging collaboration resulting in on-time and on-budget applications. Headquartered in Toronto, Blueprint has global sales, operations and partner presence. Visit www.blueprintsys.com. Оbuеprint define better. together. Use the right requirements tool. Save your projects. Only 30% - 40% of projects are successful! 60% Software Project Success Rates 50% 40% E Challenged Succeeded 30% E Failed 20% E 10% 2002 2003 2004 2005 2006 2007 2008 2009 Source: Standish Group The Root Cause: Poor Requirements The vast majority of industry reports point to requirements and related issues as the chief root cause of software project problems. Top 3 factors to determine if a project is: "Poor requirements gre the source of the majority of delivered defects in Successful: Challenged: Impaired: 1. User involvement 1. Lack of User Input 1. Incomplete Requirements software applications." 2. Exec Mgmt Support 3. Clear requirements 2. Incomplete Requirements 2. Lack of User Involvement 3. Changing Requirements 3. Lack of Resources Jones, C. 2008. Applied Software Measurement: Global Analysis of Productivity and Quality, 3rd Ed. Contributer #1: Outsourcing IT Outsourcing Spend - Development and Integration (In millions of $US) 100k r The incessant drive to outsource in a bid to reduce costs and rise of distributed development has made the situation worse. Outsourcing strains project communication and collaboration contributing to poor 80k requirements. 60k 2001 2002 2003 2004 2005 2006 2007 2008 Source: Gartner 2009 Contributer #2: M&A's 15k Total Mergers & Acquisitions ull. The incredible rise in M&A's during this same period has increased complexity of development. Legacy systems need to be merged & 12k reconciled between businesses which themselves are being 9k consolidated, making requirements tasks even more challenging. 6k 2002 2003 2004 2005 2006 2007 2008 2009 Source: IQ IT Spending on the Rise US IT Spending (in billions of $US) 600 In this environment of increased 500 pressure, investments in IT have risen significantly. 400 2002 2003 2004 2005 2006 2007 2008 2009 Source: Bureau of Economic Analysis Increased Attention to Requirements Project Effort Devoted to Requirements 6% 14% And it would appear the message is starting to get through. Between 2006 and 2010 the percentage of project effort spent on requirements more than doubled! 2006 2010 Source: Gartner BUT... Success Rates Continue to Fall 50% Software Project Success Rates In spite of more IT investment and increased attention to requirements, there has been no improvement in defect rates, and project success rates continue to fall. 40% 30% 20% Challenged Succeeded - Failed 2006 2007 2008 2009 Sources: Gartner and Standish Group The Missing Link Business Analysts are using the wrong tools. "Requirements tools need to be at the top of the shopping list for any firm involved in development of software applications." "54% of stakeholders are dissatisfied with the use of Microsoft Office for requirements." "Requirements tools seem to have the biggest impact on the success of a project. " Sources: voke Market Snapshot Report (The Role of the Business Analysit) Standish Group (Extreme Chaos) Learn More Visit www.blueprintsys.com/saveyourprojects/ to read in detail why Business Analysts are using the wrong tool or watch how Blueprint, a modern requirements platfrom, improves requirements. About Blueprint Blueprint is the world leader in collaborative requirements definition and management solutions for companies looking to improve the success of critical revenue-generating projects. Blueprint transforms the business-IT relationship into a visual and engaging collaboration resulting in on-time and on-budget applications. Headquartered in Toronto, Blueprint has global sales, operations and partner presence. Visit www.blueprintsys.com. Оbuеprint define better. together. Use the right requirements tool. Save your projects. Only 30% - 40% of projects are successful! 60% Software Project Success Rates 50% 40% E Challenged Succeeded 30% E Failed 20% E 10% 2002 2003 2004 2005 2006 2007 2008 2009 Source: Standish Group The Root Cause: Poor Requirements The vast majority of industry reports point to requirements and related issues as the chief root cause of software project problems. Top 3 factors to determine if a project is: "Poor requirements gre the source of the majority of delivered defects in Successful: Challenged: Impaired: 1. User involvement 1. Lack of User Input 1. Incomplete Requirements software applications." 2. Exec Mgmt Support 3. Clear requirements 2. Incomplete Requirements 2. Lack of User Involvement 3. Changing Requirements 3. Lack of Resources Jones, C. 2008. Applied Software Measurement: Global Analysis of Productivity and Quality, 3rd Ed. Contributer #1: Outsourcing IT Outsourcing Spend - Development and Integration (In millions of $US) 100k r The incessant drive to outsource in a bid to reduce costs and rise of distributed development has made the situation worse. Outsourcing strains project communication and collaboration contributing to poor 80k requirements. 60k 2001 2002 2003 2004 2005 2006 2007 2008 Source: Gartner 2009 Contributer #2: M&A's 15k Total Mergers & Acquisitions ull. The incredible rise in M&A's during this same period has increased complexity of development. Legacy systems need to be merged & 12k reconciled between businesses which themselves are being 9k consolidated, making requirements tasks even more challenging. 6k 2002 2003 2004 2005 2006 2007 2008 2009 Source: IQ IT Spending on the Rise US IT Spending (in billions of $US) 600 In this environment of increased 500 pressure, investments in IT have risen significantly. 400 2002 2003 2004 2005 2006 2007 2008 2009 Source: Bureau of Economic Analysis Increased Attention to Requirements Project Effort Devoted to Requirements 6% 14% And it would appear the message is starting to get through. Between 2006 and 2010 the percentage of project effort spent on requirements more than doubled! 2006 2010 Source: Gartner BUT... Success Rates Continue to Fall 50% Software Project Success Rates In spite of more IT investment and increased attention to requirements, there has been no improvement in defect rates, and project success rates continue to fall. 40% 30% 20% Challenged Succeeded - Failed 2006 2007 2008 2009 Sources: Gartner and Standish Group The Missing Link Business Analysts are using the wrong tools. "Requirements tools need to be at the top of the shopping list for any firm involved in development of software applications." "54% of stakeholders are dissatisfied with the use of Microsoft Office for requirements." "Requirements tools seem to have the biggest impact on the success of a project. " Sources: voke Market Snapshot Report (The Role of the Business Analysit) Standish Group (Extreme Chaos) Learn More Visit www.blueprintsys.com/saveyourprojects/ to read in detail why Business Analysts are using the wrong tool or watch how Blueprint, a modern requirements platfrom, improves requirements. About Blueprint Blueprint is the world leader in collaborative requirements definition and management solutions for companies looking to improve the success of critical revenue-generating projects. Blueprint transforms the business-IT relationship into a visual and engaging collaboration resulting in on-time and on-budget applications. Headquartered in Toronto, Blueprint has global sales, operations and partner presence. Visit www.blueprintsys.com. Оbuеprint define better. together.