Abel Almazan

A well-structured opportunity space has distinct branches. Learn more about opportunity mapping: https://buff.ly/4eLjiU5 #ContinuousDiscoveryHabits #OpportunityMapping #OpportunitySolutionTree #prodmgm #ux #engineering

7

1 comentario

I host twice-a-month community calls where we discuss challenges, topics, and questions related to adopting the habits described in my book. Want in? Come join us: https://buff.ly/3UM6iDE #prodmgmt #ux #engineering

4

I host twice-a-month community calls where we discuss challenges, topics, and questions related to adopting the habits described in my book. Want in? Come join us: https://buff.ly/3UM6iDE #prodmgmt #ux #engineering

8

A new article from our Mastering Agility publication. After reading the articles series from Willem-Jan Ageling about what he coined as "Scrum Fuild Teams ", Nuno Santos saw this approach as a good fit for handling work in a team that deals with projects in parallel. He describes in this article his experience in adopting it, what was used in the same way as the articles, and what was adopted differently. https://lnkd.in/eC_Eu4YQ #FluidTeams, #Agility, #Organize

5

Opportunity mapping unlocks a continuous cadence. Learn more about opportunity mapping: https://buff.ly/4895i42 #ContinuousDiscoveryHabits #OpportunityMapping #OpportunitySolutionTree #prodmgm #ux #engineering

10

Long-running pull requests (PRs)—those lingering open for more than a week—often signal deeper issues within a development team. Beyond the potential for merge conflicts, they can indicate uncertainty, misalignment, or overloaded team members. How to Recognize: 🔍Filter PRs by age and observe any prolonged discussions or stalled conversations. What to Do: 🌟Engage with Submitters: Start a dialogue to understand and resolve any blockers they’re facing. 🌟Evaluate Workload: Frequent long PRs might suggest team members are juggling too many tasks. Help them prioritize and manage their workload effectively. 🌟Set Clear Expectations: Foster a culture of timely feedback and communication to keep PRs moving smoothly. Addressing these long-running PRs not only enhances efficiency but also fosters a more collaborative and responsive team environment. Let’s keep our development processes both productive and supportive. 💬 Read more about patterns for data driven leadership: https://lnkd.in/efAZ9SXw

6

In the last episode, I talked with Ademar Aguiar about the Scrum Patterns book in which he collaborated with great names like James Coplien and Jeff Sutherland. In this cut, we talk about how teams should take responsibility for their process and face the adoption of each practice and each pattern as a choice. Listen to the full episode: https://lnkd.in/dfj6EKPe #scrum #patterns #scrumpatterns #cut #podcast

1

Share your discovery findings with the rest of the team. Learn more about avoiding handoffs: https://buff.ly/4e0if1g #ContinuousDiscoveryHabits #AvoidHandoffs #prodmgmt #ux #engineering

12

1 comentario

Nuno Santos discusses the use of adopting fluid Scrum teams in a not-so-standard environment. "Because of the complexity of work, the concept of Fluid Scrum Teams allows enough flexibility to work as a team on the Sprint Backlog but also to create enough cohesion on specific topics. Sure enough, this could also just be seen for the developers to set up within the Sprint for themselves — but especially with several data products it proved helpful for us to align beforehand in the Sprint Planning." #scrum #agile #teams #scrumteams #fluidteams https://lnkd.in/eC_Eu4YQ

3

1 comentario

No single way of collecting product requirements is a silver bullet for a good product. The key is for teams to become familiar with the advantages or limitations of the framework they’re working with. Whether that’s through teams saying they really felt heard during sprints or, on the VERY flip side, the product failing miserably 🚽 🌊 Waterfall 🌊  Linear and step by step, waterfall puts requirement gathering right at the start of the project, with the results of your findings trickling down into design, development and beyond.     As the standard process for some time, teams find it easy to understand why it’s placed early and means that you get detailed granular requirements really early which serves to clarify for any people later in the delivery chain.     Where it falls over though is that it requires you to pitch the perfect game collecting requirements unless you want expensive alterations later on. Missed insights, bad problem definition or choosing the wrong solution can all result in negative effects that run deep into the project without a way of easily (and cost effectively) pivoting because of its rigid structure.   👟 Agile 👟  Focusing on speed and better inter-team collaboration, the Agile methodology often uses sprints to build up an understanding of the requirements needed on an on-going and iterative basis.    As it’s far more fluid that Waterfall, Agile teams benefit from the ability to adapt requirements at a far cheaper cost as you’re consistently experimenting in the early phases. It also means you can scrutinise your hypotheses more often and as a result, get a better product at the end of it.    But Agile isn’t perfect for gathering requirements either. The iterative nature of Agile means that you need to firm with when you stop refining, otherwise you can be infinitely gathering requirements or waiting for the perfect product before starting which can be a huge delay. It can also create a level of uncertainty as you’re consistently modifying requirements, leaving the people to deliver the project in limbo.    In short, we believe it’s essential that product teams get to know the pros and cons of how they gather requirements, because without it, you’re making the risk of the below way higher:  💰 Expensive repairs or pivots  📦 Delivery times that never arrive  😡 Products users didn’t ask for    Read more on things you should remember when collecting requirements below 👇    https://lnkd.in/eMF46iWW #productmanagement #requirementgathering #productrequirements

5

SWIPE ➡️ for 3 common product discovery mistakes. 1. Jumping to solutions 2. Not working with stakeholders 3. Not involving engineers early enough What would you add? These and more discovery tips in our Product Discovery Playbook 👉 https://lnkd.in/gmPBcEDW

40

Breaking News - The Era of Copy-Paste Agile is Over! Maarten Dalmijn highlights a seismic shift in the Agile job market, urging organizations to abandon generic frameworks. It's time we embrace Agnostic Agile and tailor practices to meet the unique challenges of our organizations for true effectiveness.

9

1 comentario