Agile Team Development Flashcards
Why can forming an agile team be hard?
Culture, Adaption to change, conventional residues, time zones, trust, accept to inspect and adapt, …
What are the components of a successful team?
Skilled developers, established team values, good communication and motivation for improvements
What the steps to forming an agile team?
1) Forming: interact and work out what is expected from each person
2) Storming: conflict occurs as personal agendas come to light. Members assert themselves and challenge authority
3) Norming: The group finds ways to resolve conflicts and start to cooperate with each other
4) Performing: Confidence grows both individually and with other members of the group as they work towards a common goal
5) Adjourning: Having completed their task, the group dissolves
Explain the different ways you can help a team Jell?
Social Glue: Takes time to jell and build trust, meetings help each other learn about each other, creates opportunities
Build Trust: collaboration requires trust, show that it is safe to be open, be transparent about your motives, admit when you make a mistake and ask for help
Bridge the Gap: build trust between the different roles of the members in the team, people may not understand what their teammate does and could assume their role is harder than theirs
Explain the different ways you can build a team space?
Shared Workspace: shared workspace lets the communication flow, get everyone to sit down together and collab
Energizing the Team: great teams are self-motivated, create reachable but challenging goals, that way nobody is bored nor anxious. Find a compelling goal too and give time to explore new things or innovate
What are some hurdles that agile teams face?
Teams aren’t cross-functional: different disciplines working together under one team, need good relationships between individuals
No On-Site Customer: Dev team is one location, while the customer is in another (maybe even different time zone). Need to encourage customer to visit often and meet everyone
Team is a Resource Pool: Assume one project per team, no goal if the team is working on multiple projects.
Team Members Ostracize Someone on Their Team: What should you do when one person is not being worked with?
What is the life cycle of a user story?
Start as idea which then transforms to a conversation that shapes and grows. Now the conversation converges into specific test cases where they dictate what the software will do and how they should be tested