The team is the most important thing, without a good team, you won’t be producing anything. So how can you tell, as a PO, if the team is going well or not?
- Communication – Stand-ups are open, communicative, and actionable. The team talks openly without prodding, are there at the right time, and engaged with “I’ll help do that” or “I will be done with that task by lunch”
- Alive – As the team is working, it’s somewhat noisy and lively. They turn around and ask questions, discuss at whiteboards and pull you in for clarification on something
- Responsibility – You don’t have to remind them to update their tasks, their status or anything else, they know they need to do it and they do. You are not their manager tasking them with items.
- Subscribed – The team members are actually worried or concerned about a feature or story. They are bought into the notion that this work is important for somebody.
- Work is Done – Stories are getting finished early in the sprint and they are asking you to look at them. The sooner something is finished, the faster you can build confidence in them that they are doing the right thing.
- Improvement – They are suggesting ways to improve. They are invested in the success and suggest technology choices, better ways to deploy, or new ideas to solve the problem than just taking what is provided.
- Questions and Clarifications – The are active in grooming sessions. If they ask questions, or need clarification, for something you are presenting then they are engaged and understand what the item is.
- Back and Forth – Everybody talks. In the different meetings, calls, and other team settings, there is a good balance of contribution from all members. No one person is dominating the conversation or shrinking from it.
- Agile Principles – They understand the principles in the agile manifesto and embrace them. They refer or reference them as they are trying to decide how to do something. They plan and develop with the ideas of iteration and incremental releases in mind.
- Yes and – They deal with change in a positive manner.
- Me / Myself / and I – They are quietly working through their day, rarely working on things together and only concentrating on their tasks.
- Bigger is better – They cannot break down stories into small deliverable tasks of less than 6 hours. They need to have a complete architecture picture figured out before they move forward
- I’m done – Focus is on the work they signed up for instead of the overall story or spring goal. Once they are done with their work, they are reluctant to pick up anything else.
- Timing – Late for agile ceremonies and not concerned about how it affects the others.
- Quality play – Not worried about the defects, quality, or experience of a feature. “That can be cleaned up later”.
- What do I need to do – Keep to themselves in meetings, demos, and stand ups. Just there for the tasks and can’t wait to leave.
- Old School – Resist the agile principles at most opportunities and would rather work how they are most comfortable.
- I need help – They are struggling with a technical piece, they don’t know how to implement something or need some significant help.
- Have an idea – If they keep deferring to the technical managers for something, then they are fearful or not focused on the team.
- “That’s not my job”.
The team will make or break your project. This part has to be done right and the right people have to be on the bus. Once you get a good team going, they really can be hard to stop. Don’t be afraid to tell them things they need to know or would be interested to hear ( road-map, direction, feedback ). The more information they have to do their job, the better they will be at it.
PO’s help or hinder their progress by having good stories ready for them at appropriate times, are available to answer questions, and accept the work.