Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
Distributed Agile Teams: Beyond the Tools
Categories:
Agile,
Human Aspects of PM,
Leadership,
Information Technology,
Teams,
Communications Management
Categories: Agile, Human Aspects of PM, Leadership, Information Technology, Teams, Communications Management
| Many of today's agile project teams are distributed around the globe. While simple implementations of agile processes assume co-location, in larger enterprises, this is rarely the case. Selecting tools to assist remote communication helps, but it's not enough. Here are some human factors to consider, beyond the tools, to work successfully with a distributed team: Cultural differences can become apparent when working with global talent. Some people are uneasy if some social small talk is omitted as part of doing business. Some are uncomfortable if we don't simply get to the point. This affects agile teams as they implement practices such as self-organization, pair programming, and retrospectives. Remember people's assumptions can vary. Time-zone differences can be helpful by providing longer hours of coverage. But check with your teams on when they begin and end their workday. Different cultures have different laws and traditions on when to go home. Not all people have private transportation, and not all countries use daylight savings time. Finding teams in compatible time zones can be an advantage with more hours of coverage, if the hours and needs are remembered. Partnering with teams that are north or south of each other makes this easier because the time difference is less extreme. Communication differences among distributed teams also require forethought. Agile teams will notice a need for engaging and informative tools in their story grooming, estimating, planning and retrospective meetings. Telephone calls can be awkward because there is no visual cue as to who is speaking and no person to look at. Also, sound varies for each person depending on if they are in the same conference room, on a speakerphone, using a headset or cell phone. Make it a point to include people on the phone if part of the group is face-to-face. Video conferences or webcams might be a better option. Be aware of the background so it is not distracting. Also be aware of the lighting quality and direction -- illuminating an attendee's face is better than a dark silhouette. Spatial user interfaces, which extend traditional graphical user Interfaces by using two or three-dimensional renderings, give people someone to look at and allow positional body language and gestures to convey nonverbal information. However, be sure to allow training time for participants so they can make the most of these environments before needing to concentrate on a meeting. By using the right tool and having the right mindset, agile teams can work together across wide distances. How do you work successfully with distributed teams? |
The Courage Behind Boeing's Dreamliner Project
Categories:
PM Think About It
Categories: PM Think About It
| I'm sure many of you heard about the Boeing 787 Dreamliner that made its first commercial journey on 26 October. It is the most technologically advanced commercial airplane and enables air travel that is cheaper, faster and more comfortable. Perhaps you also heard about the process, communications and quality issues that delayed the project by three years and cost the company close to US$10 billion in overrun charges, according to the business news outlet Bloomberg. As a project manager, what jumps out to me is the fortitude of Boeing's management to ensure a quality product -- despite extraordinary pressure. I have no doubt that if it had wanted to, Boeing could have completed this project earlier. But rather than take shortcuts and risk potential issues, it held out for a product that met its standards. Much attention has focused on Boeing's attempts to save money and to secure global accounts by outsourcing a large portion of its component manufacturing and design. The idea was that assembly and time to market would be accelerated by allowing various parts of the plane to be flown to Boeing's facility in Seattle, Washington, USA. There, they could be pieced together in order. According to news reports, the move initially netted Boeing nearly 1,000 orders and helped keep its prime competitor, Airbus, at bay. But it marked a big change in Boeing's existing process to keep almost all of its engineering design in-house. The company typically delivers very specific "build-to-order" instructions to its manufacturing partners, outlining specifications and direction, and then collaboratively designing the parts. There were many challenges associated with a project as complex and pioneering as the Dreamliner project. One example is the process for oversight and quality control of multiple, globally based contractors. Issues arose, such as contractors subcontracting to suppliers who couldn't meet deadlines or quotas. In other cases, contractors shipped parts that wouldn't fit together correctly. Think about it: In my opinion, Boeing realized that it was more important to get the project done right versus done fast. And while the company has faced criticism, suffered some embarrassment and, yes, spent more than it anticipated, these are all short-term issues. In the long run, I believe the project will bolster Boeing's reputation for quality. It will also have finely tuned a project management process that should bring the company much higher returns in the future. |
Disciplined Project Management
Categories:
Project Planning
Categories: Project Planning
| We can all boast of great methods of managing people and project deliverables. But what gets the job done is discipline. And it's interesting to note how the team follows the leader: The more disciplined the leader, the more disciplined the team. A disciplined leader gives others an anchor -- a sense of stability and accountability. You may wonder why some people are disciplined and others are not. I believe it's a choice. Disciplined project managers strongly believe that delivering on the project result is a function of project management science and disciplined execution. Here are some ways to become a disciplined project manager: - Plan the next work week's activities a day or two ahead of time - Confirm activities the day before - Conduct daily reviews of what you did or didn't accomplish - Follow through on your commitments - Avoid time-wasters, such as unrelated conversations - Practice staying within the time allotted to the meetings, tasks and activities - Hold yourself accountable for your own deliverables by using a daily tracker document - Communicate with stakeholders and sponsors regularly, regardless of the results What are the ways you've become a disciplined project manager? And how has it helped you deliver better results? See more posts from Dmitri. |
Pancho Villa's Approach to Project Communication
Categories:
Human Aspects of PM
Categories: Human Aspects of PM
| "It is my duty to inform you that Pancho Villa is everywhere, and nowhere at the same time." Pancho Villa,1878 - 1923 Pancho Villa (1878-1923) was a revolutionary Mexican general and the subject of legends. In his time, Villa commanded the most powerful army in Latin America. Some considered him a bandit and cold-blooded killer. Others think of him as a true charismatic leader. His leadership style provides lessons that we can apply to our work as project managers -- specifically, when it comes to project communication. Historians says because of his fear, Villa would tell one member of his troop to "watch his back," and keep on an eye on suspicious behavior when he wasn't alert. Legend says that in this way, Villa braided the troops -- to keep them watching each other and "manage the risk" of being killed. I have adapted a similar approach to project management. Villa knew he couldn't supervise his troops all of the time. As we know, not everyone can be present for all meetings and working sessions during a project. Therefore, I often try to "braid" my team through a communication approach adapted from Villa's to keep information flowing. This communication technique reduces communication channels by holding one team member to be responsible for sharing important aspects of the project's journey with one or two other team members. For every two people on the project team, there should be one person updating them. In my experience, I have found this kind of communication useful with small teams between 8 to 12 people. This keeps everyone updated on the project because each team member has at least one person informing her about the project's progress and/or situations in face-to-face conversations. This allows me to avoid extensive email use. Even In some cases, fewer meetings are required and the meeting itself becomes more productive. What do you think? What communication technique you are currently using? Do you like the idea of "braiding" your project team? Do you think the braiding technique could apply to other project management aspects? Read more about project teams. Read more from Jorge. |
Posted
by Jorge Martin Valdes Garciatorres
on: November 10, 2011 11:22 AM
| Permalink |
Comments (5)
7 Essential Project Planning Documents
Categories:
Project Planning
Categories: Project Planning
| Solid project planning is a prerequisite for project success. Poor planning, meanwhile, can lead to missed deadlines, budget overruns, poor quality deliverables, frustrated project teams and even project failure. In my previous post, I offered five steps to assist in planning the project-planning phase. One of those steps involved preparing planning documents. To foster a successful planning phase, here are seven planning documents I believe most project managers will find indispensable. This list certainly might vary depending on the project setup, project size, complexity and organizational planning guidelines. 1. Project management plan -- This is used as a reference index, encompassing all planning and project documents. 2. High-level project schedule plan -- This document captures high-level project phases and key milestones. It is the document most project stakeholders will see or want to see. 3. Project team planning -- This document provides a "who-is-doing-what" view of the project. This document fosters efficient project execution and effective project communication. 4. Scope plan -- The scope plan documents the project requirements, the agreed scope and the Requirements Traceability Matrix (RTM) summary. 5. Detailed project work plan -- This keeps track of the activities, work packages, resources, durations, costs, milestones, project's critical path, etc. It will be an essential document and work guideline for your core project team. 6. Quality assurance planning -- This document tracks the quality standards your project deliverables will have to align to. These may typically include product testing approach and tools, quality policies, quality checklists, deviations definitions, quality metrics, product defect severity grades, acceptance criteria, cost of poor quality, etc. 7. Risk planning -- This document contains the project risks and the related mitigation plans; as well as the project opportunities and the related exploiting plans. The importance of this document is one of the most underestimated in project planning. Be prepared to have a contingency plan in case something goes wrong or to take advantage of opportunities when they arise. Start with this checklist when you sit down to plan for your next project-planning phase. Depending on your project's needs, fine tune the checklist and tailor it by adding and removing planning assets, determining the planning time frame, the underlying details and rigor. Revisit this planning exercise, learn from it and enhance it, to continuously improve your project planning skills. What project planning documents do you find indispensable? See other posts from Marian. |