Skip to main content

Requests for Proposals and the Iron Triangle

One of the unchanging truths of project management is the tradeoff between time, features, and cost.  This relationship is called the project management triangle, iron triangle, or triple constraint.

Source: Wikipedia http://en.wikipedia.org/wiki/Project_management_triangle

The project management triangle has implications for organizations which issue requests for proposals (RFPs).  Typically, the goal of the RFP is to solve for price and to hire a vendor to provide services or a solution.

The more information that an RFP provides on the schedule and scope, the more accurate the cost can be.  Without sufficient details on the scope of a project, the vendor is forced to guess.  One guessing approach is called time boxing.  In this method, the vendor established a schedule and then determines the cost for a typical team to provide services for a comparable project.   Time boxing means that some features must be discarded in order to meet the schedule and cost.

The absence of requirements details, or the inclusion of vague and open-end requirements drives up the cost of bids to cover risk.  Unspecified deliverables have unspecified costs. The result is often that no acceptable proposals are received.

Typically, the budgeted cost is not revealed to the bidders.  Conventional wisdom is that sharing the budget would stop bidders from offering a price lower than the budget and hence make a bargain impossible. 

The reality is that a budget can help vendors come up with realistic and accurate pricing, as well as offering a viable project approach. 

If an RFP contains only one of cost, scope and schedule, it is unlikely to result in a successful procurement.  The best approach is to include all three and ask vendors to show how they can solve the problem best within these constraints.

Popular posts from this blog

Power Apps 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 Power Apps Portal and shifted to the Power Apps 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

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

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