Teradata’s Agile Development Methodology

Teradata’s Agile Development Methodology

What is Agile Development?

The key principle of agile development is to get software or solutions in front of business stakeholders early and frequently–think four weeks or less. This allows for incremental development and the flexibility to better adapt to feedback from the business. This process leads to the ultimate goal of agile, which is to create value for the business earlier and frequently.

Agile for Analytics is Different

While agile principles hold true across all project types, leveraging the agile methodology for analytics requires a different approach from software development. The system development life cycle is far more complex in analytic systems. Analytic solutions use data built from a completely different perspective and designed for an entirely different purpose than software development. To produce agile solutions for analytics, Teradata often separates the engineering of the solution from the operationalization of it. By building working prototypes for the analytic solution (the engineering part) to get feedback from the business first, we can move to operationalizing the solution separately with better requirements.

Teradata’s Agile Development Methodology

 

Key Methods in the Teradata Agile Development Methodology

Product Backlog

A collection of requirements, such as user stories, created by a product owner who represents the business stakeholders and prioritizes their needs

Decomposition and Estimation

A process that breaks down the user stories into technical work items (things that can be built in a relatively short amount of time) and uses absolute and relative methods to estimate them.

Engineering Sprint

A development cycle uses a cross-functional Scrum team of developers to create a working solution in four weeks or less and present findings to stakeholders. These sprints allow for more innovation and help focus the business on the most valuable analytic solutions.

Sprint Review

A formal opportunity for business stakeholders to assess and provide feedback on the work that the engineering team built during the engineering sprint.

Operationalization Team

The development team that takes the output from the engineering sprint (detailed requirements) and uses a Kanban approach to optimize workflow and drive toward the production release.

 

Benefits of the Teradata Agile Development Methodology

Greater Flexibility with Multiple Agile Frameworks

By using different agile frameworks for engineering and operationalization, the Teradata Agile Methodology provides greater flexibility to customize the approach based on the type of project and your organization’s environment.

Faster Time to Delivery

Regardless of the configuration of the solution, the Teradata Agile Methodology allows for different areas of development work to occur concurrently to increase development speed and for building your solution in increments to deliver value faster.

Increased Communication with Business Users

Teradata’s Agile Methodology motivates different organizations within a business to collaborate better so that issues can be addressed early and change can be more easily accommodated.

Decreased Risk

Because development is done in increments of four weeks or less, agile allows for the development team to adapt to stakeholders’ feedback earlier, minimizing the risk of having to make expensive and time-consuming changes at the end of a development life cycle.

 

How Agile Development Methodology Helps Get More from Your Data

The Teradata Agile Development Methodology can help your business unlock greater insight into your data by enabling more innovation and building analytic solutions that better address business needs. Hear from Teradata’s agile experts on the process of agile versus waterfall, learn about customer successes, and discover the benefits of evolving your development practices.

  • After years of inconsistent development techniques, find out how this UK-based retailer adopted agile to reduce development time. (A Bad Project Gone Good—Link to Blog)
  • Learn the most effective way our team has found to put working solutions in front of business users early and frequently. (Agile Development for Analytics—Link to Blog)
  • Get a handle on what being agile can help you accomplish with the Agile Tool Chest. (Agile Tool Chest—Link to Blog)
  • Learn how to ‘Ride the Waves’ of an Agile Development Model. (Waves of Agile Development—Link to Blog)
  • Gain greater flexibility with agile. (We Welcome Changing Requirements—Link to Blog)

 

Talk to Teradata

Is the Teradata Agile Development Methodology the right fit for your development team? Find out by speaking with our experts.

CONTACT US