Pular para o conteúdo principal

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice

Whiteboard | 03:02

Build For Change: Delivery Methodology

Adopting an iterative development methodology allows customers to realize their business benefits sooner, reduce project risk and increase their visibility into project progress. Pega made the switch to Scrum in 2009 and recommends that all our customer implementations follow an Agile approach.


Transcript

Applications built on the Pega Platform deliver unique value to your business. Getting to that value quickly and effectively means selecting a development methodology that complements your project dynamics, while making the best use of your resources and their skills.

You probably have had some experience with one or more methodologies from legacy sequential models, like waterfall, to more iterative methodologies. You may have heard that using a more agile Scrum approach will allow you to realize your business benefits sooner, reduce your overall project risk, and give you maximum visibility into the project progress. How do you determine which model is right for you?

At Pega, we know exactly how you feel. In 2009, we were at the same crossroads. We decided to make the journey from a more traditional waterfall approach, to Scrum, and we have never looked back.

Pegasystems, as well as our customers that have made the transition to Scrum, have seen dramatic benefits in the following areas: earlier business value realization, higher quality applications, greater agility, greater transparency and visibility.

The Scrum methodology accelerates development by pushing smaller, more frequent releases into production. This coupled with the power of Pega's unified model-driven platform provides dramatic outcomes for our customers. We have seen customers fully up and running within months, or even weeks, following this process.

It is important to remember that implementing Scrum within an organization is a journey. It takes time to evolve from your current state to your future state with Scrum. The transition time will depend on a number of factors, including your organization's willingness to embrace a new rhythm of change. Organizations that are open to new and creative ways of getting things done tend to adapt and adopt faster, and see higher velocities in shorter time periods.

Pegasystems helps our customers make the same journey, leveraging a simple five steps process based on our lessons learned. They are Step 1, enable. Get your resources enabled on the methodology and technology. Step 2, identify. Identify the right project to start the journey with. Step 3, execute. Execute you project using all the best practice associated with Scrum. Step 4, inspect. Evaluate the progress and process along the way. Step 5, adapt. Change the behaviors of the team to increase the efficiencies.

If and when you decide to make this journey to Scrum, Pega will be with you every step of the way, to help guide you in making the transition as smooth as possible.

Related Resource

Produto

Revolucionando o design de aplicativos

Otimize rapidamente o design do fluxo de trabalho com o poder do Pega GenAI Blueprint™. Defina sua visão e veja seu fluxo de trabalho ser criado instantaneamente.

Compartilhar esta página Share via X Share via LinkedIn Copying...