Agile Mindset
Tips for Agile Product Management by AgileSparks’ Experts
We asked our experts to give their 𝐛𝐞𝐬𝐭 𝐭𝐢𝐩𝐬 𝐟𝐨𝐫 𝐀𝐠𝐢𝐥𝐞 𝐏𝐫𝐨𝐝𝐮𝐜𝐭 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭 and came up with this list.Altogether, we have here over 𝟐𝟎𝟎 𝐲𝐞𝐚𝐫𝐬
Agile Mindset
Webinar: The Five Pitfalls of the Sprint Planning Event
Every professional Scrum Master knows that the way Sprint planning events are handled has a significant impact on the effectiveness of the team in achieving the Sprint’s goal.
In this Webinar, Oded Tamir, PST and Lead Coach at AgileSparks, talked about five common pitfalls that hinder your Scrum teams’ performance.
Agile Leadership
Working towards Sustainable Pace in Scrum, SAFe and Kanban
Aiming towards Sustainable Pace “Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.” – The
Agile
Build Psychological Safety in Teams Through Code Reviews
How would you describe your experience when someone reviews your code? Many developers report this is a source of stress, conflicts, and even power and
Agile
How to improve User Stories’ readiness and maturity so that the team can complete them quickly inside a Sprint?
Many teams complain that the stories they are working on are not ready for development and some details are missing which results in longer cycle
Agile
Practice Makes…
Finding true success with your SAFe implementation
We all believe that practice makes perfect. However, if you practice the wrong things the only thing you are perfecting is the wrong approach.
A big part of my personal life revolves around motorcycles, specifically road racing and coaching. When I am working with new racers or track riders wanting to improve their skills the first thing I do is to ask them to complete this sentence “Practice makes…” Almost everyone says “Perfect!”, but usually the opposite is true. When racers go out on track and continue to repeat bad habits, such as not moving their eyes down a track or using poor body position, they simply cement in the wrong technique, which makes it more difficult to correct later. I always teach the riders to focus on learning the basics and then build on these good techniques until they become “permanent”. I want to thank Nick Ienatsch from the Yamaha Champions Riding School for helping me to see the importance of learning the right skills before starting to practice. Working with Nick and the crew at YCRS and ChampSchool taught me so much about the importance of getting the basics right.
Agile
Leveraging SAFe 5.1 to organize around value and maximize customer-centricity
SAFe 5.1 doubles down on the importance of organizing around value. SAI SAFe Fellow, Andrew Sales will cover new and updated guidance for effectively identifying Operational and Development value streams to maximize the value you’re creating for your organization and accelerate time to market.
AgileSparks SPCT Yuval Yeret will bring his experience from working with dozens of enterprise-level technology companies to share practical tips and techniques that can be used with SAFe 5.1 to combine customer-centricity and Operational Value Stream identification. These patterns have helped both ISV enterprises, as well as IT organizations, organize around value.
Scaled Agile Framework
How Vendors Can Apply Customer Centricity When Organizing Around Value
A lot of our clients are technology vendors that struggle to use the SAFe Operational Value Streams “out of the box”. Here, I explore how such a B2B vendor should organize around value when building products that are used to support its customer’s business operations.
Scaled Agile Framework
INVEST in effective SAFe PI Objectives
Could the INVEST criteria Bill Wake came up with for evaluating User Stories help us come up with effective PI Objectives in SAFe as well?
I think a good PI Objective should be:
– Independent – meaning ideally it could be delivered and evaluated on its own without any dependency on other PI Objectives. And if a team is able to own a PI Objective and delivery it on its own – it’s a sign that it’s a cross-functional autonomous team.
Agile
Iterating faster with SAFe
Here’s a frequently asked question in the SAFe community: I wanted to understand what SAFe says about someone who wants to go faster than 2 weeks of iteration? I mean the whole PI concept is based on 5 iterations worth of planning. What if a team/organization wants to develop and synchronize faster than 2 weeks? Is speed going to be compromised by following the standards of PI cadence?
Here’s my take:
Adjusting Cadence Length in SAFe – Can you? Should you?
