PMIPCC Network Meeting

What anti-patterns you typically observed ?

Sprint Planning antipatterns with respect to Customer Centric Agility

• Overemphasis on Velocity: Focusing solely on team velocity without considering the value delivered to the customer can lead to features being completed but not providing real customer value.

• Lack of Customer Involvement: Sprint planning should involve customer representatives to ensure alignment with customer priorities. An anti-pattern is excluding them from the planning process.

• Incomplete Backlog Refinement: Planning based on poorly refined or ambiguous user stories can lead to misunderstandings and rework, delaying valuable customer deliveries.

• Unclear Customer Priorities: Lack of clear communication or understanding regarding customer priorities may result in misaligned sprint goals and deliverables.

Daily Standup antipatterns with respect to Customer Centric Agility

• Status Reporting Instead of Collaboration: Team members just providing status updates rather than using the time to collaborate and address blockers can hinder quick adaptation to customer needs.

• Excluding Customer Feedback: Not incorporating customer feedback during the daily standup can lead to a lack of customer focus and missed opportunities for improvement.

• Extended Standups: Overly long standup meetings can reduce their effectiveness, leading to disengagement and less attention to customer-centric goals.

• Ignoring Customer-Related Impediments: Not addressing impediments that directly impact customer satisfaction during standups can hinder overall agility.

Sprint Review antipatterns with respect to Customer Centric Agility

• Lack of Stakeholder Involvement: If key stakeholders, including customers, are not actively involved in the sprint review, valuable feedback may be missed, and the product might not meet their expectations.

• Focus on Features Instead of Value: Prioritizing the number of features delivered rather than the value they bring to the customer can result in a product that does not fully meet customer needs.

• Insufficient Demo Preparation: Poorly prepared or ineffective product demonstrations can lead to misunderstandings and hinder the gathering of meaningful feedback.

• Ignoring Negative Customer Feedback: Dismissing or downplaying negative customer feedback without addressing the underlying issues can hinder improvement.

Sprint Retrospective antipatterns with respect to Customer Centric Agility

• Blame Culture: Focusing on blaming individuals for issues rather than identifying systemic problems and improvement opportunities can hinder a customer-centric mindset.

• Skipping Retrospectives: Skipping retrospectives denies the team the chance to reflect on what went well and what could be improved, reducing the team's ability to adapt to customer needs.

• Failure to Implement Improvements: Identifying improvements but not implementing them perpetuates issues and prevents the team from becoming more customer-centric.

• Lack of Action on Customer-Centric Insights: Identifying customer-centric insights during retrospectives but not taking action on them prevents meaningful improvements.

Backlog Refinement antipatterns with respect to Customer Centric Agility

• Unclear Prioritization Criteria: Without clear criteria for prioritizing backlog items based on customer value, the team may focus on less critical tasks, impacting overall customer satisfaction.

• Incomplete User Stories: Insufficiently detailed user stories may result in misinterpretations, leading to features that do not align with customer expectations.

• Neglecting Emergent Customer Needs: Failing to adapt the backlog to emergent customer needs during refinement can result in a product that doesn't meet current market demands.

• Lack of Collaboration on User Stories: Developing user stories in isolation without collaboration between the team and customers can lead to misunderstandings.