TRENDS

CONCEPTS

PATTERNS

ISSUES


TRENDS

  • Team

  • System

  • Continuous Integration

  • People

  • Environment

  • Human Behavior

  • Growing

  • Coordination between teams

  • Cross-team coordination

  • Interdependent work

  • Shared responsibility

  • Shared work product

  • Cross-functional teams

  • Co-located teams

  • Long-lived teams

  • Organizational coaching

  • The Product Owner is outward focused on customers as well as inward focused on the teams, i.e he/she behaves as a connector between the two.

  • Synchronizing work with other members of the team as part of ‘continuous integration’.

  • The feature teams are aligned to creating end-to-end customer centric features.

Back to top

CONCEPTS

  • Mailing lists

  • Chat

  • Occasional meetings

  • Leadership meetings-leads or managers getting together for a leadership meeting

  • Some concepts that relate to Product Owner are- product development, internal (product) development, project development.

  • Teams must adopt ‘continuous integration’ of code which involves taking time out to go through code written by peers as well.

  • When there is much preference given to a customer domain, teams are led to more structuring decisions.

  • Teams need to be self-managing in terms of being able to execute tasks and manage and monitor process and progress.

Back to top

PATTERNS

  • Daily Scrum meetings

  • The Product Owner works on activities such as prioritizing items in the product backlog and clarification of items in the backlog.

  • Coordination between teams takes place through “Just talking”.

  • Most teams and manager follow lean management.

Back to top

ISSUES

  • Large changes to a stable system will destabilize and break it in large ways

  • People working together creates conflict

  • Unresolved conflict has a negative impact on team performance and creates a dysfunctional team atmosphere

  • Sometimes, the goal of a Scrum Meeting can become obsolete, in such a case if the Product Owner stills continues to go ahead with it, the session becomes less productive.

  • If people working on the same components/modules are not in constant communication about the status of their work, there could be overlap of feature or other functional implementations.

Back to top