The Microsoft Dynamics NAV Project Exchange Zone
Ever watch the Olympic 4 x 100 relay, and how the runners pass the baton? As the first runner comes toward the second runner, the second runner starts to run. Ideally, there is an “exchange zone” where both team members are running the same speed and the baton is passed off seamlessly.
Project managers on Microsoft Dynamics NAV implementations can use this same “exchange zone” technique to their advantage when transitioning teams at the beginning and ending of projects that have sprints.
When starting a project, a project manager can integrate sales resources into the first sprint of the project as “floater” team members. “Floater” team members are team members outside the core team that come to specific sprints to provide unique skills or act as SMEs (Subject Matter Experts). Floaters have the same team responsibilities and authority as core team members during their limited engagement on the team.
By including sales on the sprint team in the project, the project manager is creating an “exchange zone” that helps transfer client knowledge elicited in the sales cycle to project core team members. Often, the sales team is accused of not transferring vital client information to the project team. Using the “exchange zone” technique gives sales and the core project team the opportunity, structure, and forum to refine captured client information elicited during the earlier sales cycle.
At the end of the project, a project manager can also use this same “exchange zone” technique to introduce the post project support team to the client during the project. Often, the support team is introduced to the client after the project completes. Introducing the support team as floaters during the last sprint of a project will facilitate the transition of client work to support when the project concludes.
Project managers that use the “exchange zone” technique greatly reduce the risks and confusion associated with team trade-offs at the beginning and end of projects.