Skip to main content

Call InfoStrat to Make Things Right on a Software Project

More often than you might expect, InfoStrat is called to turn around a  software implementation which is in trouble.  After the client has consumed much of the budget and schedule for the project, it is falling behind and the client has doubts that it can be successful.



These turnaround projects are all the more challenging because they must be completed faster and at lower cost than the original project envisioned, and tension is already high at the beginning of the project.

How can we turn the project around?  Each case is different, but some common approaches are:

1. Reduce the size of the project team.  A large team can be a hindrance as time spent on communication increases.  A team is often slowed down by the slowest team member.

2. Use a team that has worked together before. Successful teams have strong cohesion and know each others' strengths and weaknesses.

3. Create a single client point of contact.  Conflicting requirements and feedback can paralyze a software project, and internal client communication and approvals also slow down the process.

4. Abandon failed approaches. Sometimes a project team finds it hard to disregard sunk costs, and sticks with an unsuccessful technical approach too long.

5. Change the project methodology.  If your project approach is more about deflecting blame than shipping a working product, it can undermine results. We have seen many projects with lengthy and well formatted documentation accompanying broken products.

6. Remember the iron triangle which forces tradeoffs among features, cost and schedule. Like the laws of physics, this can only be ignored at your peril.

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises