Executive leadership just gave the go ahead for the PMO to fire-up another project but it feels like staff is already over-capacity to take on more work. Here’s how I built a lightweight, easy-to-sustain project labor demand solution using SharePoint and Excel to measure and prioritize project labor demand.
Does this sound familiar?
Let me take a shot at reading your mind:
Your executive leadership team just gave the go ahead to fire-up another project but it feels like your staff is already over-capacity to take on more work. That’s right—feels—a squishy, subjective term. The reality is you don’t currently have a compelling way to show leadership your project labor demand. You’d prefer to wait two months (or more) before taking on more projects but that pushback won’t fly without hard facts.
In the early to mid-2000s Microsoft Corp. painted the world a beautiful picture of the ease at which one could exchange information across disparate systems, whether across the LAN or across the Internet. The company simultaneously eased both Office users and professional developers into unfamiliar terminology like Web Services, Simple Object Access Protocol (SOAP), and XML.
Don’t worry about the new terminology, Microsoft told Office users (paraphrased). With a few drag-and-drops and mouse clicks, we made it simple for you to call a web service with little to no coding experience. You’re going to love how easy it is to push and pull data using Visual Basic for Applications (VBA) within your Office files—namely Excel (paraphrased).