Episode 5 of the Pega Developer Podcast features a conversation between Pega’s Timothy Harfield (Sr. Director, Community Engagement for Intelligent Automation) and Baruch Sachs (VP Client Innovation) in which they discuss the evolution of the Pega Express methodology, the qualities that make a great application, and whether or not fully removing constraints and boundaries from product development is necessary for innovation.
Not able to listen to the entire episode? Here are a few key takeaways from the conversation between Timothy and Baruch:
The Pega Express Methodology was created to deliver value fast
While traditional methodologies like Scrum or Design Thinking can be helpful in the product development process, being overly rigid in applying them (or others) can result in a bloated application development process.
Because the Pega Platform and Pega Express Methodology have co-evolved, embracing the best of Scrum and Design Thinking, the result has been a truly synergistic relationship between technology and methodology focused on building and deploying apps faster through the creation of Minimum Lovable Products (MLP’s) in a 30 to 60 day period.
There are three pillars that ultimately make an application great
Pega Founder and CEO Alan Trefler has identified three pillars that are the foundation of any successful business application: case types, personas/channels, and data. Development teams need to prioritize these pillars in order to create a successful MLP. Without focusing on these three pillars, developers run the risk of going to market with an ineffective application that would likely require many iterations to complete.
Constraints are necessary for innovation to flourish
Common wisdom holds that eliminating constraints and boundaries is essential for creativity and innovation to flourish. That's just not true.
Constraints actually spur innovative solutions because they force product development teams to face some level of challenge or boundary in the creation process. Very few developers have the ability to work in an environment that is free from time or budgetary constraints. That’s where the Pega Express Methodology comes in. It forces developers to focus explicitly on what they absolutely need in order to successfully launch an MLP in a 30-to-60 day period of time. The result is not only decreased time to value, but a foundation that encourages future and ongoing innovation.
- JOIN THE CONVERSATION on Collaboration Center
- FOLLOW @PegaDeveloper on Twitter
- SUBSCRIBE to the Pega Developer Podcast on Spotify or via RSS