Improve from sprint to sprint with issue-specific briefs. Chief Product & Technology Officer, Dror Jacoby, unveils our new collaborative improvement solution for product development teams.
How does Shamaym’s new improvement solution help developers?
Developers encounter and solve challenges every single day. Our most recent release empowers them to concretely improve outcomes by capturing lessons learned from previous sprints and releases, sharing knowledge across teams and issues, and putting those lessons into action when the time is right. All this happens through what we call an “improvement cycle”, a combination of issue-specific, personalized briefs that developers receive at critical points in the development process, and dedicated spaces to debrief, or capture learning when it’s fresh.
The ability for leaders to receive insights based on their developers’ actual lessons in an accessible, palatable manner, represents a major step forward in our mission to help teams improve their performance and adapt quickly to changing needs. The brief and its surrounding innovations in our new release will help teams create ultra-fast improvement cycles that will push them toward their goals at a faster pace than ever before, and with less required from them than at any previous point.
Can you walk us through the “improvement cycle”?
Suppose you lead a development team. You’ve just completed a sprint and it’s time to plan for the next one. As you begin to add issues to the sprint you receive a notification in Jira with a brief, a collection of automatically compiled lessons from previous sprints that are most relevant to the topics and keywords in the current one. This way, the most valuable learning from previous sprints is top-of-mind when you’re actually working on related challenges.
The sprint begins. When an issue is moved through the development pipeline, its completion triggers a reminder to debrief, offering a dedicated space to quickly record lessons and insights based on the most recent tasks performed.
One click, and developers are recording their lessons while they’re fresh.
When a developer begins work on a new issue they receive a brief with lessons specifically related to that issue.
What can teams expect to gain from the new improvement cycle?
Development teams we’ve spoken to express a genuine desire to learn and improve: to build better and better products with smoother workflows, less bugs, and happier users. They have the learning part down since most of them conduct retrospectives. But, like many of us, they struggle to access the learning from the retrospective when it actually matters–in the next sprint–and therefore they struggle with implementation.
This challenge was central in our design of the new improvement cycle for developers. Simply put, we wanted to help development teams improve more effectively. By turning learning and improvement from something that happens only during the retrospective to something happening constantly while teams work, where they work.
Great development teams already use our product to elevate quality, reduce the number of issues and escalations, and get team members highly engaged in the improvement cycle. We can’t wait to see what amazing products these new capabilities will help teams deliver!