Reading: Agile principles for good teamwork
The following six Agile principles are focused more on how your team works together in a cohesive way that builds trust, efficiency, flexibility, and encourages consistent/open communication. Please review these below and consider how they relate to your own experience in working with teams.
4. Work Together Daily - Business people and developers must work together daily throughout the project. A ritual you may have heard of called the "Daily Stand Up Links to an external site." is one key way a team ensures they're adhering to this principle.
5. Motivated Team - Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. Can you think of how tech companies and departments build teams of motivated individuals and the ways they provide a supporting/trusting environment for people to get work done?
6. Face-to-Face - The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Consider communication over the phone versus Zoom or text versus in-person. What has worked best in your experience with complicated team projects and why?
8. Constant Pace - Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Consider if you followed this principle in 333K. Did you get a constant amount of work done each week or did pace pickup through the project and peak at the end?
11. Self Organization - The best architectures, requirements, and designs emerge from self-organizing teams. Consider two options of team management: 1) a single manager assigns everyone work from the backlog for that week without considering each person's strengths and interests. 2) each person communicates their skills/interests and selects work from the backlog to get done that week. Which sounds better and which adheres more this principle? What have you experienced on past team projects?
12. Reflect & Adjust - At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly (aka Agile Retrospective). Think back to 333K. No one's project goes perfect (Clint's and Caryn's included). Can you think of issues in the K project that could have been addressed earlier in the project? Were there any awkward team dynamics that never were discussed? Do you think weekly reflections and adjustments as a team could have improved your experience and outcomes?
There are a total of 12 Agile principles and the above a just some. For a list of all of them go check out the full list of Agile principles here.