TechValidate Research on Blueprint

Introduction

This case study of MetLife is based on an August 2017 survey of Blueprint customers by TechValidate, a 3rd-party research service.

Objectives

The business challenges that led the profiled company to evaluate and ultimately select Blueprint:

Purchased Blueprint to:

• Improve the success of product and application launches
• Increase maturity and agility of planning and requirements processes
• Manage changes required by the business

Challenges Solved

Blueprint solved the following challenges created by using JIRA alone:

• A lack of intuitive, understandable view of products to be delivered that can be reviewed with business stakeholders and large development teams
• A lack of complete documentation of what has been delivered
• Overall time and effort required to manually write and coordinate user stories and test cases

Results

The surveyed company achieved the following result with Blueprint:

• Complete requirements / user stories of an average project with 11-20% less effort since using Blueprint.

Introduction

This case study of a Global 500 banking company is based on an August 2017 survey of Blueprint customers by TechValidate, a 3rd-party research service. The profiled company asked to have their name blinded to protect their confidentiality.

Challenges

The business challenges that led the profiled company to evaluate and ultimately select Blueprint:

• Purchased Blueprint to:
  • Increase business visibility into development plans, designs, and progress before products are released
  • Increase maturity and agility of planning and requirements processes
  • Remove bottlenecks at the front end of development cycle
  • Manage changes required by the business
  • Stay ahead of regulatory and compliance issues
  • Improved communications and tracking
• Blueprint solved the following challenges created by the previous tool used:
  • Lack of an intuitive, understandable view of products to be delivered that can be reviewed with business stakeholders and large development teams
  • Lack of a permanent record system of what has been delivered
  • Lack of complete documentation of what has been delivered
  • Difficulty of having business stakeholders understand what is being worked on, and what has been delivered in a sprint
  • Overall time and effort required to manually write and coordinate user stories and test cases
  • The difficulty of tying development and testing efforts back to business objectives

Use Case

The key features and functionalities of Blueprint that the surveyed company uses:

• Uses Jira’s agile development tool

Results

The surveyed company achieved the following results with Blueprint:

• Completed the requirements/user stories on an average project with 31-40% less effort since using Blueprint