Inspiration

DevOps is being a topic for many organizations nowadays. Imagine you have set up a pipeline which works like a charm.
So, how do you ensure your it doesn't deliver a rubbish to you production at the speed of light?

Have you seen suboptimal design decisions working in the production, and question yourself - how did we end up with this solution?

Or maybe, as a product owner, you want to distribute the knowledge in the team to ensure a support continuity, especially in such unprecedented times.

How we approach it

Our solution to the issues mentioned is a Peer Review practice. We have been supporting customers for extended periods of time, and we truly believe this practice can help achieve a lot:

  • Promote best practices & govern design
  • Distribute knowledge & Improve co-production
  • Socialize quality by dragging team members into regular quality discussions … and especially with the remote mode of operation that we have now.

Challenges we ran into

We usually encourage teams to use Pega branch reviews,… … but we have to admit there is a huge space for improvement. So we gathered together, despite the distance between the Munich and Moscow, and applied the design thinking to prototype and build our MLP… Minimalistic, but very Lovely Product :)

What it does

Peer Review Component provides the following features:

  • Streamlined Review process with stages
  • Review Tasklist provides visibility of work
  • Intuitive Review Explorer allows to easily navigate branch content and track review progress
  • Contextual review conversation in a Rule form
  • Best practices at fingertips in a History tab of rules

Accomplishments that we're proud of

Solution has naturally extended existing Pega Platform functionality. Review Explorer in the Application Explorer is perfect, it's so easy to use and it looks like it was always there.

What we learned

  • Design thinking approach is a great way to justify, plan and scope the work and to define the MLP.
  • UX is crucial; properly selected small changes in the UX can become great improvements for the end-users.

What's next for Pega Peer Review

Peer Review component is now pending approval in the Pega Marketplace, so it should be available for the community soon. We are very happy how this worked out and are excited to continue our journey. We have a full backlog of features to be implemented
… and we are planning continue until Infinity!

Built With

+ 17 more
Share this project:

Updates

posted an update —

New release was published on Pega Marketplace https://community.pega.com/marketplace/components/peer-review-component

Version 8.5.7: [New] Component upgraded to support Pega 8.5.x

Version 8.4.7: IMPORTANT: when updating from previous versions, make sure to close all reviews beforehand. Otherwise, comments will be lost [New] Review status and comments for the whole branch [New] Change log for the rule is shown above comments [New] Combined statuses option in Review explorer, in case you create many reviews for the same branch [New] Review comments are synced to conventional review form [New] "New" meta-status in Review explorer (like "Redo") groups all rules created since the last review [New] Tooltip of the rule shows the availability if not Available [New] Status tab is a default selection in Review explorer [Fix] Status calculation for rules without update timestamp [Fix] Comments from previous reviews are not shown anymore

Log in or sign up for Devpost to join the conversation.

Submission history