Action #2: Identify the point(s) of collaboration where your chosen challenge appears

If you’d talk to consult with an experienced Agilist, talk to a live person, and ask your questions…

If you’d talk to consult with an experienced Agilist, talk to a live person, and ask your questions…

Points of Collaboration

Failure #2: Not My Job

Starting Your Adventure

AMMI Spiral Graph Logo

Welcome to

The Library

of Agile

“Nie mój cyrk, nie moje malpy”

“Not my circus, not my monkey”

– Old Polish saying

Why AMMI Doesn’t Have Roles

Roles differ and change between Agile methodologies. For example, several methodologies have a Scrum Master role, and some don’t. Some organizations have Project Managers, and others don’t. Some methodologies have Product Owners, some have Product Managers, others have both, and some use Project Managers instead. And in some methodologies everyone is just called a “team member”. 

 

You get the point. Roles mean a lot within an organization, but they don’t really mean that much in Agile. What really matters instead is collaboration, and more-importantly points of collaboration, but we can also lose enthusiasm, momentum, and support by forcing other people to sit through things they either don’t care about or can’t control.

The Library of Agile focuses on 6 primary areas of collaboration:

  1. People – People collaboration practices deal with psychology, social interactions, and interpersonal relationships — basically any time thinking individuals interact with other thinking individuals. 

  2. Design – Design collaboration practices incubate the creative and artistic processes used when inventing something new or expanding on existing inventions.

  3. Planning – Planning collaboration practices sort through the complex moving parts of a project and seek to organize them in a way that improves efficiency and effectiveness.

  4. Implementation – Implementation collaboration practices center around the process of architecting and constructing solutions. You may be used to seeing terms like “coding” or “engineering” used here, but Agile applies to more than software, so we use the more generic terms at the Library of Agile. Implementation could be the delivery of services, conversations or speeches, or the writing of documents.

  5. Verification – Verification collaboration practices ensure the completeness, integrity, security, and longevity of our solutions. Now, you may be used to terms like “testing” or “quality assurance”, but Agile applies to more than software or physical products, so we use the more generic terms at the Library of Agile.

  6. Operation – Operation collaboration practices maintain the frameworks that surround solutions. They help “keep the lights on” and maintain a consistent delivery of value to those who use our products.

Step #2: Focus on Points of Collaboration

Points of Collaboration

2.

Design

Collaborating Roles:

  • Product Manager

  • Product Owner

  • Business Analyst

  • UX Designer

  • Artist

 

Example Tasks:

  • Research

  • UX/UI

  • Design

3.

Planning

Collaborating Roles:

  • ScrumMaster

  • Project Manager

  • Personnel Manager

  • Team Members

Example Tasks:

  • Scheduling

  • Facilitation

  • Communication

4.

Implementation

4.

Implement

Collaborating Roles:

  • Developer

  • Architect

  • Clerk

  • Writer

Example Tasks:

  • Coding

  • Writing

  • Construction

5.

Verification

5.

Verify

Collaborating Roles:

  • Tester

  • Quality Assurance

  • Quality Control

  • Developer

Example Tasks:

  • Testing

  • Code Review

  • Reporting

6.

Operations

Collaborating Roles:

  • Network Administrator

  • Support

Example Tasks:

  • Environments

  • Inventory

  • Maintenance

1.

People

Collaborating Roles:

  • ScrumMaster

  • Project Manager

  • Personnel Manager

Example Tasks:

  • Reviews

  • Benefits

  • Culture

  • Growth