TL; DR: Create Personas with the Help of the Engineers
Creating valuable software requires knowing the customer—we all agree on that, right? The first question that then comes to mind is how to support this product discovery process in a meaningful manner in an agile environment? And the second question follows swiftly: who shall participate in the process—designers and business analysts or the engineers, too?
Read on and learn why personas are useful for product discovery purposes, how to create personas, and why the complete team—including the engineers—needs to participate in their creation.
After rebuilding an existing application on a new tech stack within time and under budget our team had an overall retrospective with stakeholders this week to identify systemic issues. We found more than 20 problems in total and derived eight detailed recommendation the organization will need to address when moving forward to the next level of agile product creation.
Read on and learn how we achieved this result in under two hours with an overall retrospective attended by 16 people.
Scrum has proven to be an effective product delivery framework for digital products like applications or apps. However, Scrum is equally suited to build the wrong product efficiently as its Achilles heel has always been the product discovery part. What product discovery part, you may think now. And this is precisely the point: The product owner miraculously identifies what is the best way to proceed as a team by gating and prioritizing the product backlog. How that is supposed to happen is nowhere described in the Scrum Guide. Consequently, when everyone is for himself, product discovery anti-patterns emerge.
From sunk costs, HIPPO-ism, my-budget-my-features to self-fulfilling prophecies — learn more about the numerous product discovery anti-patterns that can manifest themselves when you try to fill Scrum’s product discovery void.
Learn more about agile management anti-patterns the aspiring agile manager should avoid during the organization’s transition. From stage-gate through the back door to the ‘where is my report’ attitude.
Job ads for scrum master or agile coach positions reveal a great insight into an organization’s progress on becoming agile. To gain these, I analyzed more than 50 job ads for scrum master or agile coach positions. Learn more about what makes job ads such a treasure trove with the following 22 scrum master anti-patterns.
The following 56 scrum product owner theses describe the role of the PO from a holistic product creation perspective.
The 56 product owner theses cover the concept of the product owner role, product discovery, how to deal with external and internal stakeholders, product roadmap planning, as well as the product backlog refinement. The theses also address the product owner’s part in scrum ceremonies such as sprint planning, sprint review, and the sprint retrospective.