4 docs tagged with "Coordination Risk"

Conducting regular reviews to discuss what went well, what didn't, and how to improve.

Conducting systematic reviews of work done.

Two developers working together on the same code.

Two developers working together on the same code.

Using version control systems to manage changes to the codebase.

Defining contractual obligations and agreements.

Managing communication strategies to promote the software and engage with the target audience.

Getting formal approval for various project stages.

Managing changes to systems and organisations in a systematic way.

The practice of assigning responsibility and authority to others to carry out specific activities or tasks.

The practice of gathering team members to discuss project progress, address issues, and make decisions.

The practice of gathering team members to discuss project progress, address issues, and make decisions.

Gathering and documenting the requirements for the software.

Managing relationships and communications with stakeholders.

Defining the scope and objectives of the project.

Defining the scope and objectives of the project.

Having a customer representative available onsite for feedback.

A Model Of Coordination Risk

Imagine talking to a distributed database, where your request (read or write) can be handled by one of many agents.

Within a team, Coordination Risk is at its core about resolving Internal Model conflicts in order that everyone can agree on a Goal and cooperate on getting it done. Therefore, Coordination Risk is worse on projects with more members, and worse in organisations with more staff.