Use level of effort in order to sequence based on complexity.

Use relative points because it increases the team's confidence in their estimate.

Use standardized points that reflect industry norms for estimating sizes.

Use story points because they can provide a better cost estimation than T-shirt sizes.

Avoid the conflict altogether

Yield to the other person's opinion.

Attempt to win the conflict to assert rank.

Collaborate to find a creative solution that works for both.

DevOps

Disciplined Agile Enterprise (DAE)

Foundation

Value Stream

Prove architecture early by working on architecture spikes or proof-of-concept user stories.

Open space or "unconferences" where agendas are set real time by participants.

Plan releases with relative sizing or planning poker concepts.

Architecture owners from each of the sub teams work together and guide the overall program.

Visualize work and workflow, perhaps leveraging Kanban boards or digital tools such as Jira.

Program manager guides the overall program and coordinates efforts among the team of teams.

People start to push against the established boundaries. Conflict or friction can also arise between team members and their preferred ways of working.

Individuals will be unsure of the team's purpose, how they fit in, and whether they'll work well with one another.

With hard work and structured processes, the team is likely to achieve its goals efficiently.

People start to resolve their differences, appreciate one another's strengths, and respect your authority as a leader.