Skip to main content

Don't Call People Resources

I know that in project management, people are considered resources in the same way that raw materials are considered resources, but for software development projects I have found it counterproductive to treat people like so many interchangeable parts.

The success of a software project hinges on the interactions among many people, including the client, subject matter experts, project managers, testers, trainers and developers.  In addition to their experience and expertise, these people bring with them their personalities and communications styles. 

Because software development is more a team exercise, like filming a movie, than an individual exercise, like writing a book, the overall team dynamic is just as important as individual qualifications.   It is quite possible to put together a team of people with excellent resumes who will be quite ineffective when forced to work with one another.

I have run into clients who focus excessively on comparing resumes as if they provide an indication of future success.   Some of the best resumes I have seen belong to work avoiders who spend more time finding others to blame than accepting responsibility and getting things done.  Job hoppers have more interesting resumes than steady performers that stay with companies and projects for the long haul.

So many project methodologies are now used that you need to ensure everyone is on the same page.   Approaches and activities that work in one methodology are disastrous for others.  Excessive love of methodology and documentation over working software is ever more pernicious.

Experience of people who have worked as a team is a great asset for a software project.   Knowing the strengths and weaknesses of team members helps project managers and technical leads assign tasks to the right people, and to know how those people should be managed.   Some need close attention with frequent interaction, and others need time alone to do their work.  Some people will thrive in the intense pressure of a war room environment, while others will crumble.

So even if you call them resources on your project plan, don't treat people like resources if you want your project to succeed.

Popular posts from this blog

PowerApps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as PowerApps Portal and shifted to the PowerApps side of the Microsoft product family.


Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users.

The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription."

Pricing starts at $200/mo. for 100 dail…

ScreenMeet Remote Support Tool for Dynamics 365 Customer Service

I met Lou Guercia when he was president and CEO of Scribe Software, the leading CRM integration tool.  Scribe was acquired by TIBCO Software in 2018.  I recently reconnected with Lou and learned about ScreenMeet, the company he joined as chief operating officer.   The following is a description of the product provided by ScreenMeet:

ScreenMeet is a cloud-based remote support tool designed to integrate with Dynamics 365 Customer Service. By enabling customer service and IT support organizations to address critical technical issues directly from their CRM or ticketing platform, it streamlines the process and provides a fully browser-based support experience.

You can also use ScreenMeet with other CRM products or even on its own without a CRM.

Here is a short video demo of ScreenMeet with Dynamics integration:


ScreenMeet - Cloud-based Remote Support Integrated with Dynamics 365 Customer Support Once integrated with a Dynamics 365 CS organization, the ScreenMeet widget appears on Case pa…

Microsoft PowerApps and Microsoft Flow Licensing for Beginners

NOTE: Since this post was written, Microsoft has updated pricing.  For current pricing, see https://powerapps.microsoft.com/en-us/pricing

Next month marks two years since Microsoft announced the preview of its Flow workflow automation product.  Since then, PowerApps and Microsoft Flow have been gaining in popularity.

We at InfoStrat are receiving more questions from customers on how PowerApps and Flow are licensed by Microsoft.  This is a brief overview with links to authoritative Microsoft resources with all the details.

What are PowerApps and Flow? Microsoft PowerApps is a framework derived from Dynamics 365 (formerly Dynamics CRM) that allow you to build apps either with or without a form interface.  PowerApps works with Microsoft Flow.

Microsoft Flow is is a cloud software tool to build automated workflows that connect to many Microsoft and non-Microsoft systems and services.  For instance, you could write a workflow which would create a record in Dynamics 365 whenever a new file …