![]() Commitment to routinely travel to PI planning events.Overlapping core hours for DSU, Iteration Planning, demos and other events. ![]() Collaboration tools for communication, visualization and ideation.A wiki or intranet site providing access to Strategic Themes, Portfolio Vision and other critical information.Tooling for team and program Kanban boards and backlogs.High bandwidth video and audio connectivity.While being distributed does not change the basic Agile ways of working, it does impose some requirements on the business and the remote workers. We have both witnessed and participated in high-performing teams with a significant degree of distribution. The fact is that many Agile teams are distributed across geographies, sometimes with significant time zone differences. Simply, some of the people who can contribute the most are not available to be located-or relocated-on site. However, co-location is not always feasible. The Agile pod design above is a reflection of that. To this end, enterprises often spend significant time and energy establishing co-location. (“The most efficient and effective method of conveying information to and within a development team is face-to-face conversation”). Workspaces for Remote WorkersĪgile development is designed and optimized for co-located teams. In some cases, these have been provisioned as movable and stand-alone ‘phone booths’ inside a more open workspace. Where feasible, a few private phone cubicles support the need for individual privacy. In some cases, these team rooms can be shared with other teams and serve as an informal conference room for others. When not in use by the teams, it also provides a retreat for private conversations. The meeting room provides space for the team to post their information on the walls and collaborate with remote team members and other teams. Ideally, the facilities on the right of Figure 1 augment the pod. The pod is supported by whiteboards, a large monitor for video conferencing, and information radiators. In addition, the gathering spaces in the middle provide an area for hoteling team members, spontaneous pairing, and quick, informal sessions. However, the higher outside walls on of the pod largely separate the noise and conversation from the team next door. Their focus space is inside their cubicle, yet it allows informal communication and ‘overheard’ knowledge gain within the team. Walls within the pod are low, allowing for informal discussions. In this design, teams of 8-10 individuals work in a ‘pod’ of semi-private cubicles. An Agile pod, augmented, where feasible, by a team room and private phone cubicles Many organizations have arrived at what seems to be a fairly common and efficient design, as illustrated in Figure 1. While opinions vary considerably (XP shops, in particular, appear to favor the fully-open pairing concept), in our experience, neither of the two extremes is optimal. In the field, we’ve observed practices at the extremes, from individuals in traditional cubicle farms to completely open workspaces designed for ad hoc pairing, teaming, and ease of reconfiguration. Provide room for the team Daily Stand-up (DSU) and space for whiteboards, visual information radiators and at least one large monitor.Support the need for occasional privacy.Support the need for constant informal team collaboration.Provide individual focus space for being ‘in the flow’ of developing code, tests, and other artifacts.Out of these experiences, a few common requirements, some modestly self-conflicting, have emerged: Such experiments are not easily conducted, as arranging and rearranging a physical workspace involves facilities, capital expense, potential interior remodels, and more. In the search for ever higher productivity and employee engagement, many enterprises have experimented with team workspaces explicitly designed to support Agile development. Work Visualization Techniques that create transparency and alignment alongside opportunities to improve processes.Cross-Team Collaboration Spaces that support critical events such as PI Planning as well as encourage innovation.Workspaces for Agile Teams that balance the need to work together daily alongside occasional privacy.In this article, we’ll address three key topics and share best practices that have emerged: We describe these physical spaces that encourage collaboration, communication, and innovation as Agile Workspaces. Further, the environment must positively reinforce the cultural changes while amplifying the focus on face-to-face communication and information transparency. Experience and research have also shown that effective workspaces are one of the keys to high team productivity. Adopting Lean and Agile practices across the Enterprise greatly benefits from a physical environment for teams and Agile Release Trains (ARTs) that supports these new ways of working.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |