Tag: Brian Springman

  • Detailed Review of Klient PSA Salesforce App

    Robot Using Klient PSA Salesforce project management app

    Klient PSA is reviewed against 200+ Salesforce project management software requirements on a downloadable spreadsheet. Klient PSA is scored overall for each of the ten project management processes. This post provides a summary of the key strengths and weaknesses for each of the processes.

    Summary Findings

    Klient PSA is a good overall PSA tool, though it doesn’t have all the bells and whistles of some of its larger competitors. Some key positive differentiators are:

    • Great Gantt chart scheduling tool. Even supports ‘fixed effort’ scheduling.
    • Invoicing functionality.
    • Standard integrations with 4 accounting packages.
    • Proposal/SOW functionality.
    • Supports Agile process (except for prioritizing tasks on board).

    Some of the negative differentiators are:

    • Not directly integrated with Salesforce Opportunities to forecast resources and revenue based on opportunities.
    • Doesn’t support daily or weekly rates.
    • Cannot re-order tasks within a Kanban column.
    • Can’t limit visibility of confidential projects.
    • Can’t share tasks with external team members.
    • Doesn’t support inter-project dependencies.
    Klient PSA Summary Scores

    Download Klient PSA Scorecard

    Click here to download the scorecard. It is an Excel spreadsheet with over 200 requirements scored for the tool.

    Pricing

    Klient PSA is $49/user/month but this includes the Salesforce licenses. I’m assuming the Salesforce licenses they are referring to are Platform Starter for customers who aren’t already on a Salesforce solution.

    Platform Starter is $25/user/month, so if you are planning on using Platform Starter for other solutions your net Klient PSA cost is $24/user/month. Please note that a Platform Starter license allows you to install an unlimited number of purchased apps but you can only create 10 custom objects yourself. To create up to 110 custom objects you need Platform Plus at $100/user/month.

    Scoring Methodology

    I’ve been evaluating all of the Salesforce project management software and sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. When I come across novel functionality in the software I’m evaluating I add it to the requirements list. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totaled the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you.

    Here are some links to help you research the app:

    Communications Management

    Like most PSA tools, Klient PSA does not have functionality to support change management and the related communications. However, it does have good project status communication functionality.

    Nothing to discuss in detail here.

    Cost Management

    Klient PSA has the standard PSA functionality to track labor costs and expenses. Two key differentiators is that it has the internal capability to generate an invoice and to integrate with four accounting packages. There are several gaps:

    • Can’t rollup multiple project costs to a program.
    • Doesn’t support daily or weekly rates.
    • Supports expense approvals but the approval process must be built.

    Strength: Integration with 4 Accounting Packages

    It has standard integrations with the following accounting packages:

    • Quickbooks
    • Sage Intacct
    • Xero
    • Accounting Seed

    Weakness: Costs Can’t Rollup to a Program

    It doesn’t support programs for groups of projects. You can create a parent project with several sub-projects, but the values of the sub-projects don’t rollup to the parent.

    The parent/sub-project relationship is only intended for reporting. So you could create reports with totals using the parent project as a filter.

    Weakness: No Daily or Weekly Rates

    It appears all the rate cards assume hourly rates. Daily or weekly rates have become popular in consulting. So if you often use daily/weekly rates, you’ll probably want to consider a different PSA tool.

    Weakness: Must Build Approvals

    This seems fairly common in the PSA apps. The app supports marking an expense or timesheet as approved and configuring who should approve it. However, you must build the approval process yourself. This should only take several hours to build and test.

    The PSA apps don’t provide the approval processes pre-built because approval processes can’t be packaged in a managed app. However, there is a workaround where they could support a manual install.

    Integration Management

    Klient PSA doesn’t have any standout features in this area, but it does have some gaps.

    Weakness: No Change Orders

    Most PSA tools don’t support documenting detailed scope line items. However, Klient PSA also doesn’t support creating change orders and routing them for approval.

    Weakness: No Confidential Projects

    You can mark a project ‘global’ so any resource can view it and record time against it. However, you can’t make a project confidential so only team members can view it. You can manage who can record time against the project.

    Weakness: Task Notifications

    It is missing useful notifications available on other PSA tools:

    • Alert to owner when task is assigned.
    • Alert to owner when task is ready to start because preceding task was finished.
    • Alert when no time has been entered on a completed task.

    Procurement Management

    Like most PSA apps, Klient PSA does not really support purchasing outside services or materials. You cannot create and track purchase orders. You can forecast cash flows through expenses, and track total vendor payments.

    Quality Management

    Klient PSA doesn’t have any testing or quality functionality.

    Resource Management

    Klient PSA has all the resource management functionality you’ll need to run a professional services project. One unique feature is the ability to search resource availability directly within a task. But there were also two gaps in functionality that are offered by other tools.

    Strength: Search for Available Resources Within a Task

    When you create a task and are ready to assign a resource, you can click a button to search for resources with the same project role that have availability. This makes it easy for the project manager to assign available resources in real time.

    Weakness: Doesn’t Publish Resource Openings

    Some other PSA tools allow the publication of resource requests so that employees can express interest in the work.

    Weakness: Forecast Resources Based Upon the Sales Pipeline

    Other tools are more integrated with Salesforce Sales Cloud, and thus they can generate forecasts of resourcing needs based upon the sales pipeline. This gives a long term view of resource shortfalls and time to address them.

    Risk Management

    Klient PSA has strong risk management functionality. It has only a few gaps that can easily be filled with less than an hour of configuration changes in Salesforce.

    Strength: Assign Tasks to Risks

    You can assign Salesforce tasks to the identified risk. This feature is often missing in other tools, but I consider it the most important part of risk management. When you identify a risk, you need to assign tasks to either investigate or address it and you want to be able to monitor the outstanding tasks associated with the risk.

    Schedule Management

    Klient PSA has an excellent Gantt chart and scheduling tool. It has nearly all the functionality of Microsoft Project, including the ability to use fixed effort tasks to resource level a task. It only has four significant scheduling gaps.

    Strength: Core Scheduling Options

    It has all the core and advanced scheduling options most projects will need:

    • All types of dependencies (FS, SF, FF, SS).
    • Lag and lead times.
    • Critical path.
    • Unlimited task hierarchy (i.e. levels in the work breakdown structure).
    • Tasks assigned to teams.
    • Multiple resources assigned to a task.

    Strength: Resource Leveling Tasks

    This is the first PSA tool, I’ve seen which offers a ‘Fixed Effort’ scheduling option. This means it will change the task’s duration if the assigned resources cannot work enough hours in the current duration. For example, if I have an 80 hour task and assign one resource to complete it in a week, it will push the duration out to two weeks.

    It doesn’t have the project-level resource leveling functionality as found in Microsoft Project. MS Project will shuffle all the tasks at once to ensure no resource is over allocated.

    It also offers the default ‘Fixed Duration’ scheduling option, which is usually the only option in other tools.

    Strength: Supports Agile Development

    It has all sorts of features to support Agile development. However, it does have one major gap where you can’t prioritize tasks on the Kanban board (see below). Here are the Agile features:

    • Organize tasks into sprints.
    • Define scrum teams.
    • Define epics.
    • Classify tasks as bugs or user stories.
    • Kanban board.

    Weakness: External Resources Can’t Work Tasks

    While tasks can be assigned to a non-Salesforce user, there isn’t anyway to communicate the task to the external resource. There also isn’t anyway for the external resource to update the task as complete.

    Other tools offer either an external website where people without Salesforce licenses can view the project and assigned tasks, or they email tasks with a link to click when the task is complete.

    Weakness: Can’t Prioritize Tasks on Kanban Board

    While it has good overall support for the Agile process, this is a major gap. You can move tasks between the columns on the Kanban board. However, the product owner cannot prioritize the tasks from top to bottom so the team knows what priority to work the tasks.

    Weakness: Can’t Assign Task Constraints

    Tasks on the schedule cannot be assigned constraints: Must Finish On, Must Start On, Early as Possible, Late as Possible. This shouldn’t be a major gap for most companies, and I’ve only found one Salesforce scheduling tool which offers this functionality.

    Weakness: Doesn’t Support Inter-Project Dependencies

    You cannot make a task on Project A dependent upon the completion of a task on Project B. This type of functionality is only supported by a handful of PSA tools and shouldn’t be an issue for most companies.

    Scope Management

    Like most PSA tools, Klient PSA doesn’t provide any scope management functionality. It doesn’t even support the creation of change orders, which is available in a few tools.

    Stakeholder Management

    Klient PSA doesn’t support any stakeholder management which is required for change management on a project.

    In Conclusion

    Klient PSA should be on your short list of PSA apps to consider if:

    • You only have Salesforce Platform. Because most of the other PSA tools require Sales Cloud for all their functionality.
    • Scheduling is very important to you.
    • You want native invoicing functionality.

    You should not include Klient PSA on your short list if:

    • You want a solution integrated with your sales pipeline.
    • You commonly use daily or weekly rates.
    • You need a fully functional Kanban board.
    • You need to block access to confidential projects.
    • You need to coordinate tasks with external resources.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Detailed Review of Certinia Professional Services Cloud

    Certinia Professional Services Cloud Salesforce project management app

    Certinia Professional Services Cloud (PSC) is reviewed against 200+ Salesforce project management software requirements on a downloadable spreadsheet. Certinia PSA is scored overall and for each of the ten project management processes. This post provides a summary of the key strengths and weaknesses for each of the processes.

    Certinia PSA Summary Findings

    Certinia PSC is a beast! The PSC app has 160 custom Salesforce objects. Plus it has nine other accounting apps which could be combined into a comprehensive solution:

    • Billings & Receivables
    • ERP Cloud
    • Revenue Management
    • Services CPQ
    • Procurement
    • Services Analytics
    • Order & Inventory Management
    • ERP Analytics & Reporting
    • Subscription & Usage Billing
    • Professional Services Quoting

    Certinia was previously named ‘FinancialForce’ and has obviously been building Salesforce apps for quite awhile. If you are looking for a PSA solution, you should place Certinia on your shortlist just because of its size and expansion potential.

    As for functionality, the only major gap is that Certinia PSC does not create, distribute and track invoices. You’ll have to purchase the Billing & Receivables app for that functionality. Other PSA apps include invoicing functionality.

    WARNING: I wasn’t able to install Certinia PSC into a Salesforce sandbox and test it directly. I had to rely on demos and documentation for this review. Certinia didn’t respond to my install request and doesn’t offer a test drive.

    Certinia PSC Summary Scores

    Download Certinia Evaluation Spreadsheet

    Click here to add the Certinia Excel spreadsheet to your basket and continue reading. Visit the basket page to complete the download.

    Pricing

    Certinia PSC’s lowest pricing published on Salesforce AppExchange is $40/user/month. I’m leery about this pricing because Certinia does not publish any pricing on their website, and claim they offer bundled and a la carte pricing. SoftwareConnect quotes $125/user/month for all apps/functionality. So I recommend you contact Certinia directly for quotes.

    Scoring Methodology

    I’ve been evaluating all of the Salesforce project management software and sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. When I come across novel functionality in the software I’m evaluating I add it to the requirements list. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totaled the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you.

    Here are some links to help you research the app:

    Download Certinia Evaluation Spreadsheet

    Click here to download the Certinia Excel spreadsheet.

    Communications Management

    Certinia PSC’s only communication management functionality revolves around providing project clear status metrics and project dashboards. It doesn’t support any change management activities: distributing communications or scheduling training.

    Cost Management

    Certinia PSC has considerable cost management functionality. I didn’t see any unique features which would differentiate it from the other PSA tools. It does have one large gap: invoicing. It does not generate or track customer invoices, though it does aggregate the data required to generate an invoice. The invoicing functionality resides in a separate Certinia app, or you can integrate Certinia PSC with your own financial system. Many of the other PSA tools provide invoicing functionality.

    Strength: All the Standard PSA Cost Management Functionality

    It has all the standard PSA cost management functionality, including some of the more advanced features:

    • Milestone-based billing events
    • Estimate at Completion (EAC) calculations
    • Multiple billing types
    • Rate cards

    Weakness: Separate Invoicing Functionality

    It will create ‘billing events’ which aggregates all the data to produce a customer invoice. A billing event can be triggered by achieving a project milestone or just based on the date. The billing event data is also customized based on the contract term: fixed fee, T&M, etc. So it does 90% of the work of creating an invoice.

    You can create and track invoices by also purchasing the Certinia Billings & Receivables app. You could also use their standard integration with SAP Concur, or build a custom integration with your invoicing system.

    One drawback of not having an invoicing system in PSC, is that the PSC financial metrics are based on billed amounts and not actually paid amounts.

    Integration Management

    This is one of Certinia PSC’s weakest areas when compared to other PSA tools. It covers most of the basics but it is missing some useful functionality.

    Strength: Consolidated Programs

    It doesn’t specifically have ‘programs’ but it does have parent and sub-projects. So you could setup your program as a parent project with the projects as sub-projects. I believe all the sub-project data will rollup to the parent project.

    Weakness: Can’t Block Visibility to Confidential Projects

    There are advanced permission controls which govern what actions a user can perform within a project. However, I could not find a setting that would block all visibility to confidential projects. You should confirm this if you are considering a purchase.

    Weakness: Lacking Some Timesheet Automation

    Other PSA tools have some useful timesheet automations that Certinia PSC lacks:

    • Flag completed tasks without time entries
    • Auto-populate timesheet with assigned tasks

    Weakness: Lacks Task Alerts

    It lacks two useful task alerts:

    • Notifying a task owner that a task has been assigned to them
    • Notifying a task owner that a task is ready to be worked because the preceding task was completed

    Weakness: Support for Agile Methodology

    It’s only support for an Agile software development methodology is an integration with JIRA. So if you use JIRA, this won’t be much of a gap. If you want to support your Agile methodology within your PSA tool, it has the following gaps:

    • Releases
    • Epics
    • Themes
    • User Stories and acceptance criteria
    • Burndown chart
    • Sprints
    • Kanban board

    Procurement Management

    Like most PSA tools, Certinia PSC doesn’t have any real procurement management functionality, other than to forecast expenses. If your projects involve lots of vendor contracts then you’re going to need to supplement PSC.

    Quality Management

    Like most PSA tools, doesn’t support any testing or quality functionality.

    Resource Management

    Certinia PSC checks all of the boxes related to resource management. It’s functionality is comparable to the other PSA tools and I didn’t find any unique strengths. I only found one significant gap related to the resource allocation view, but because I didn’t have my own copy of Certinia PSC I can’t be sure it is a gap.

    Strength: Standard PSA Functionality

    Some of the more advanced functionality that PSC supports that is missing from some other tools:

    • Soft booking resources
    • Publish resource openings

    Weakness: Doesn’t Differentiate Between Soft and Confirmed Allocations in Planner View

    It doesn’t appear to differentiate whether a person’s allocation to a project is soft or confirmed in the main resource planning view, where you are trying to match people to resource requests. Other PSA tools use color coding, so that the resource planner knows they can re-assign soft allocations if necessary.

    I didn’t have a copy of Certinia PSC, so I was relying on demos. Therefore, you should confirm this gap for yourself.

    Risk Management

    It has the ability to record and track risks comparable with all the other PSA tools. The only gap which it also shares with most of the PSA tools, is the ability to assign tasks to the risk.

    Schedule Management

    Certinia PSC has a very good Gantt chart. It is only missing the ability to assign constraints to tasks.

    It’s one major scheduling gap, is that it doesn’t synch PSC tasks with Salesforce tasks. This means a person must look up their assigned tasks in two places.

    Strength: Very Good Gantt Chart

    It has all the basic scheduling features of Microsoft Project, except one: can’t assign task constraints (Must Start On, Must Finish On, etc.). Here are some of the advanced features it does have:

    • All dependency types (FS, SF, FF, SS)
    • Lead/Lag
    • Unlimited task hierarchy (some PSA tools only support 2-3 levels of tasks)
    • Multiple people assigned to one task
    • Reschedules dependencies based on predecessor’s actual dates
    • Supports inter-project dependencies
    • Critical path

    Like all the other PSA tools, it doesn’t support resource-based rescheduling. It will not automatically resource load level tasks.

    WARNING: I wasn’t actually able to put my hands on the Gantt chart to test for myself. The functionality listed above is based upon Certinia’s documentation. You should confirm for yourself.

    Weakness: Doesn’t Synch with Salesforce Tasks

    It is a huge inconvenience for people to have to go to multiple places to see all the tasks they are assigned. Therefore, I’m a strong proponent that a PSA tasks should create a duplicate synched Salesforce task. This allows someone to view all their assigned tasks in the Salesforce task list. This functionality is supported by several tools.

    Scope Management

    Like most PSA tools, Certinia PSC doesn’t capture detailed scope items. However, it does get kudos for have a change order process and supporting a full work breakdown structure.

    Strength: Unlimited Work Breakdown Structure

    You can create an unlimited hierarchy of tasks in the Gantt to align with your work breakdown structure. It is also very easy to create task hierarchies by simply indenting the task on the Gantt. Many PSA tools limit you to 2-3 levels.

    Strength: Change Orders

    It supports the creation of change orders and routing them for approval.

    Stakeholder Management

    Like most PSA tools, Certinia PSC doesn’t support change management and therefore doesn’t have functionality for planning or managing stakeholders.

    In Conclusion

    If you are looking for a PSA tool, Certinia PSC should be considered for your short list. It is comparable to all the big Salesforce PSA tools. Since I wasn’t able to get my hands on Certinia, you’ll need to verify this review if it makes your short list of options.

    The key differentiators when compared to other PSA tools are:

    • Lacks the invoicing functionality within PSC
    • Doesn’t synch with Salesforce tasks
    • Doesn’t support Agile development
    • Has a great Gantt chart
    • Option to implement the complete suite of Certinia apps

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Precursive PSA Salesforce App Reviewed By a Project Manager

    Precursive writing in Japan as symbol for Precursive Salesforce project management software

    Precursive PSA

    Precursive PSA is reviewed against 200+ project management software requirements on a downloadable spreadsheet. Precursive PSA is scored overall for each of the ten project management processes. This post provides a summary of the key strengths and weaknesses for each of the processes.

    Precursive PSA Summary Findings

    First of all, Precursive has four product offerings for Salesforce project management. You can buy OBX as a standalone Kanban board scheduling tool. There is also PSA which adds resource and cost management functionality, and which can be installed in three ways:

    • Without OBX
    • With OBX, connected so OBX tasks feed the resource management tool
    • With OBX, unconnected so OBX tasks don’t feed the resource management tool

    This review is focused on the connected version of PSA with OBX. I have a separate review of the standalone OBX version. I have a few notes on how functionality will differ in the unconnected version.

    Overall, Precursive PSA is a robust, well-rounded PSA tool and is comparable to the other tools (i.e. Kantata, Cloud Coach, etc.). I really like the OBX Kanban board approach with the unique screen that allows you to enter task details directly on the board. It has a unique feature which allows you to use different revenue recognition methods for different projects, thus resulting in accurate financial estimates.

    Precursive PSA
    Total Score52%
    Communications Management9%
    Cost Management62%
    Integration Management48%
    Procurement Management0%
    Quality Management17%
    Resource Management88%
    Risk Management58%
    Schedule Management62%
    Scope Management0%
    Stakeholder Management17%

    Overwhelmed trying to find the best PSA tool? Give me your functionality priorities and I will give you a shortlist of 3-5 PSA tools that best suit your needs. You can then focus your detailed assessments on only a few tools. Saves you weeks of research and demos.

    Precursive PSA Pricing

    PSA’s lowest standard price is $40/user/month ($480/user/year). They have a 20 license minimum so starting costs are $9,600/year. They state that they do have different types of licenses for different roles. You’ll need to contact Precursive to get a custom quote.

    Precursive PSA Scoring Methodology

    I’ve been evaluating all of the Salesforce project management software and sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. When I come across novel functionality in the software I’m evaluating I add it to the requirements list. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totals the ratings by process to show how the apps compare by process. Therefore, you can assess the Salesforce project management apps based on which processes are the most important to you.

    WARNING: Unlike most of my reviews of Salesforce project management apps, I was not able to install a complete version of PSA to perform my review. I was able to install OBX (schedule management), but I wasn’t able to put my hands directly on the resource and cost management functionality. Instead, I based my review on online demos and the Precursive knowledgebase.

    Here are some links to help you research the app and download the requirement spreadsheet. Please note, the ‘Get it Now’ link on AppExchange just creates a form for Precursive to contact you, so to perform your own review on a free trial you’ll have to contact them directly.

    Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Precursive PSA quickly and thoroughly.

    Communications Management

    PSA only has three basic communication features: project status, chat, and external access. The chat feature is simply the standard Salesforce Chatter. I’ll explain the others below.

    Strength: Project Status History

    It is the first app I’ve seen that records a history of the project status. You create a project health record with explanations for the health rating. There is also an adjacent tab that displays risks and issues.

    Strength: Share Projects with Customers

    You can give customers access to the project’s Kanban board through a Force.com website. There are advanced settings so you can control which boards and tasks are published to the external website.

    Weakness: No Change Management

    It isn’t built or intended to support change management (i.e. communication or training). If your projects have significant training requirements then you’ll want to consider a learning management system (LMS).

    Cost Management

    PSA has all the basic cost and invoicing functionality a professional services firm will need. Two differentiators are: the ability to use different revenue recognitions models, and the ability to bill using day rates. Its greatest weakness is a gap in the ability to forecast an estimate at completion (EAC) based on actual costs and remaining tasks. This gap can be addressed with some custom configuration within Salesforce.

    Strength: Different Revenue Recognition Models

    PSA supports three revenue recognition models:

    • % of project completion (intended for fixed-price projects)
    • Equal per period (for example, 1/6 per month for a 6 month project)
    • Billable time submitted (i.e. timesheets)

    The method of revenue recognition can vary by project. This allows the revenue forecast to correctly align to the actual revenue recognition method, resulting in accurate financial forecasts.

    Strength: Day Rate Invoicing

    When creating a rate card for a customer or project, you can specify to use day rates (i.e. $1,000/day) for a resource. This has become a popular billing method within consulting and IT services, and is not supported in some of the other Salesforce project management and PSA tools I’ve reviewed.

    Weakness: Lacks EAC Calculation

    PSA has the data required to calculate an estimate at completion (EAC) but it doesn’t provide this calculation pre-built. This is unfortunate, because this is a key project metric, telling you if the project is forecasted to be within budget based on the costs incurred so far and the progress. To build this, you will have to calculate the cost performance index (CPI) and then add the actuals to the forecasted values adjusted for the CPI.

    Integration Management

    PSA has some basic integration management functionality (dashboards, risks and issues), but not any unique strengths. It has major gaps around: scope management and grouping projects into programs.

    Weakness: Lacks Detailed Scope

    It doesn’t documented detailed project scope and it doesn’t support creating or approving change orders.

    Weakness: Can’t Group Projects

    It doesn’t support programs or portfolios. Thus you can’t aggregate project information to an overall program or use portfolios for aggregated reporting

    Procurement Management

    The only procurement management functionality is the ability to record expenses and project cash flows.

    Quality Management

    PSA doesn’t have any testing functionality.

    Resource Management

    PSA has great resource management functionality and I like the resource planning screen design. Its strengths are in the ability to forecast resource demand based upon the sales pipeline and the ability to differentiate between forecasted and confirmed allocations. I didn’t find any major gaps or weaknesses.

    Strength: Forecast Resource Demand from Sales Pipeline

    If you use standard project types with pre-defined roles, then you can relate the standard project type to a sales opportunity. You can then forecast your resource demand from opportunities still in the sales pipeline. This gives you a long term outlook of your resource requirements.

    Strength: Forecasted Versus Confirmed Allocations

    When viewing resource availability in the Resource Plan screen, the existing allocations are color coded so the resource manager knows which are ‘soft’ allocations based on forecasts or are confirmed allocations. This gives the resource manager the flexibility to adjust allocations that are not yet confirmed.

    Risk Management

    PSA has basic functionality to document risks. However, you cannot assign tasks to address the risks.

    Schedule Management

    PSA has basic functionality to create and schedule tasks. It has basic Gantt functionality. It has three unique strengths. First, it has a unique interface which allows you to add task details within the Kanban board. Next, it has a unique feature to create milestone metrics. Lastly, you can synch Precursive tasks with external calendars like Outlook or Google.

    As for gaps, it lacks advanced scheduling functionality like different dependency types, critical path or constraints. It doesn’t support releases or sprint planning.

    Strength: Kanban View with Task Details

    I really like its Kanban board that allows you to enter task details like dependencies and checklists, right within the board.

    Strength: Milestone Metrics

    Unlike most scheduling tools, you don’t simply set a task’s duration to zero to create a milestone. You actually define a separate milestone record and then associate it with a task. This allows you to measure the elapsed time between milestones. This would be very useful if you wanted to track key stages across all of your projects, like how long does it take onboard the team from contract signing.

    Strength: Synch with External Calendars

    I’m a strong believer in giving users one source for all their assigned tasks. If your company uses external calendars rather than Salesforce, then this is a big feature. When a task is created or updated in Precursive, a task will be added to the assigned person’s external calendar. The only caveat is that the synch is only one-way. The user will need to log into Precursive in order to update or complete the task.

    Weakness: Lacks Advanced Scheduling

    If you are looking for a full-fledged scheduling tool like MS Project, Precursive is not for you. Here are some of the missing scheduling functions:

    • Only supports Finish/Start dependencies
    • Only supports ‘Must Finish On’ constraint
    • Doesn’t calculate critical path
    • Doesn’t support fixed work scheduling

    Weakness: No Release or Sprint Planning

    This is the biggest gap when compared with JIRA. Precursive doesn’t contain release or sprint objects, so you can’t organize your board tasks by release or sprint. Therefore, you can’t track progress against the release or sprint. I think you could work around some of this by configuring Precursive. You could have a separate board per release. You could add a custom field to assign tasks to a specific sprint.

    Scope Management

    PSA lacks most scope management functionality, like detailed scope items and change orders. However, it does support creating a detailed work breakdown structure with headers and subtasks. Unfortunately, creating a subtask isn’t as easy as indenting a task under another as in many other Gantt tool.

    Stakeholder Management

    PSA doesn’t have any stakeholder management or change management functionality. If you had a small list of stakeholders, you could create a ‘Stakeholder’ role and assign them to the project team.

    In Conclusion

    Precursive PSA has very solid PSA functionality. You should place it on your shortlist of options if you are selecting a PSA tool. It has an edge over other PSA tools if accurate forecasting of financial revenue is important. It also has an edge if you prefer to plan your projects on a Kanban board.

    If you are looking for a generic Salesforce project management tool, like a PMO tool you should consider other options. This is because it lacks any change management functionality and is weak in overall integration management.

    If you are just looking for a Salesforce scheduling tool, then you should also consider other options. PSA doesn’t come close to the functionality of MS Project, because it is missing advanced scheduling features.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Detailed Review of Precursive OBX Salesforce App

    Precursive writing in Japan as symbol for Precursive Salesforce project management software

    Precursive OBX is reviewed against 200+ project management software requirements on a downloadable spreadsheet. Precursive OBX is scored overall for each of the ten project management processes. This post provides a summary of the key strengths and weaknesses for each of the processes.

    Precursive OBX Summary Findings

    This is a detailed review of the Precursive Salesforce project management software formerly named ‘TaskFeed’. The Precursive OBX app is a Salesforce project management tool available on the Salesforce AppExchange, it supports the onboarding process for professional services firms. There are actually two Precursive apps: OBX and PSA. This review only covers OBX.

    Precursive OBX is a great Kanban board tool built natively on Salesforce. The main question is whether it is as good as the master of all Kanban boards (JIRA) and whether being native offers significant advantages over using the JIRA/Salesforce interface. When trying to make this decision, you also need to factor in the integration of OBX with PSA which provides full professional services automation (PSA) functionality.

    In the end, the only scenario I can come up with for installing Precursive OBX as a standalone app, is if you want to customize it using Salesforce data or workflows. If you are a professional services firm looking for a PSA solution then you should evaluate OBX in the context of implementing the complete suite of Precursive products. If you are simply looking for a Kanban board to manage your sprints, then JIRA has better functionality, and there shouldn’t be a need to integrate with Salesforce. If you are looking for a PMO tool for internal use, then you should consider other Salesforce project management tools.

    I’d also lean towards JIRA because it is cheaper. The first ten users of JIRA are free. JIRA is $16/user/month if you need their Gantt view, but only $8.15/user/month if you don’t need the Gantt view. OBX pricing starts at $20/user/month for a starter package, and then the minimum pricing is $40/user/month beyond the starter package.

    Precursive OBX Summary Scores

    Download Precursive OBX Evaluation Spreadsheet

    Click here to add the Precursive OBX Excel spreadsheet to your basket and continue reading. Visit the basket page to complete the download.

    Precursive OBX Pricing

    The standard pricing listed on AppExchange is confusing. It states a starter package of $20/user/month ($240/user/year) with a minimum of 20 licenses ($4,800/year), but a minimum cost of $40/user/month ($480/user/year) as default pricing ($9,600/year).

    Precursive OBX Scoring Methodology

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. When I come across novel functionality in the software I’m evaluating I add it to the requirements list. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totaled the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you. WARNING: The video demos for OBX on the Salesforce AppExchange include PSA functionality, so you cannot rely on the demos if you are only interested in OBX.

    Here are some links to help you research the app:

    Download Precursive OBX Evaluation Spreadsheet

    Click here to download the Precursive OBX Excel spreadsheet.

    Precursive OBX Communications Management

    OBX only has three basic communication features: project status, chat, and external access. The chat feature is simply the standard Salesforce Chatter. I’ll explain the others below.

    Strength: Project Status History

    It is the first app I’ve seen that records a history of the project status. You create a project health record with explanations for the health rating. There is also an adjacent tab that displays risks and issues.

    Strength: Share Projects with Customers

    You can give customers access to the project’s Kanban board through a Force.com website. There are advanced settings so you can control which boards and tasks are published to the external website.

    Weakness: No Change Management

    It isn’t built or intended to support change management (i.e. communication or training). If you projects have significant training requirements then you’ll want to consider a learning management system (LMS).

    Precursive OBX Cost Management

    OBX doesn’t have any cost management functionality.

    Precursive OBX Integration Management

    OBX has some basic integration management functionality (dashboards, risks and issues), but not any unique strengths. It has major gaps around: scope management, approvals and grouping projects into programs.

    Weakness: Lacks Detailed Scope

    It doesn’t documented detailed project scope and it doesn’t support creating or approving change orders.

    Weakness: Can’t Group Projects

    It doesn’t support programs or portfolios. Thus you can’t aggregate project information to an overall program or use portfolios for aggregated reporting.

    Precursive OBX Procurement Management

    OBX doesn’t have any procurement management functionality.

    Precursive OBX Quality Management

    OBX doesn’t have any testing functionality. You could add some custom fields to the tasks to document acceptance criteria and some test details.

    Precursive OBX Resource Management

    OBX only provides resource management functionality around assigning and tracking task status, as well as, controlling access to the project. It lacks the functionality to track people’s availability against existing allocations to staff projects.

    Strength: Project Access Control

    It has good functionality to control project access. All projects are confidential. Only people added as team members have access to the project. You can control whether the team members have read or edit access at the click of a button.

    Weakness: Lacks Staffing Requests and Assignments

    You can assign resources to tasks and assign hours, however, you can’t create staffing requests and fill the requests based on people’s availability.

    Precursive OBX Risk Management

    OBX supports documenting risks. However, you can’t assign tasks to the risks.

    Precursive OBX Schedule Management

    Precursive OBX has basic functionality to create and schedule tasks. It has basic Gantt functionality. It has three unique strengths. First, it has a unique interface which allows you to add task details within the Kanban board. Next, it has a unique feature to create milestone metrics. Lastly, you can synch Precursive OBX tasks with external calendars like Outlook or Google.

    As for gaps, it lacks advanced scheduling functionality like different dependency types, critical path or constraints. It doesn’t support release or sprint planning.

    Strength: Kanban View with Task Details

    I really like its Kanban board that allows you to enter task details like dependencies and checklists, right within the board.

    Strength: Milestone Metrics

    Unlike most scheduling tools, you don’t simply set a task’s duration to zero to create a milestone. You actually define a separate milestone record and then associate it with a task. This allows you to measure the elapsed time between milestones. This would be very useful if you wanted to track key stages across all of your projects, like how long does it take onboard the team from contract signing.

    Strength: Synch with External Calendars

    I’m a strong believer in giving users one source for all their assigned tasks. If your company uses external calendars rather than Salesforce, then this is a big feature. When a task is created or updated in OBX, a task will be added to the assigned person’s external calendar. The only caveat is that the synch is only one-way. The user will need to log into OBX in order to update or complete the task.

    Weakness: Lacks Advanced Scheduling

    If you are looking for a full-fledged scheduling tool like MS Project, OBX is not for you. Here are some of the missing scheduling functions:

    • Only supports Finish/Start dependencies
    • Only supports ‘Must Finish On’ constraint
    • Doesn’t calculate critical path
    • Doesn’t support fixed work scheduling

    Weakness: No Release or Sprint Planning

    This is the biggest gap with JIRA. OBX doesn’t contain release or sprint objects, so you can’t organize your board tasks by release or sprint. Therefore, you can’t track progress against the release or sprint. I think you could work around some of this by configuring Precursive. You could have a separate board per release. You could add a custom field to assign tasks to a specific sprint.

    Precursive OBX Scope Management

    The only piece of scope management functionality supported by Precursive OBX, is that you can create a detailed work breakdown structure. I was able to create multiple levels of subtasks. Many PSA tools only support 1-2 levels of tasks.

    Precursive OBX Stakeholder Management

    Precursive OBX doesn’t have any stakeholder management functionality. You could configure the role types to add ‘Steering Committee’ or ‘Stakeholder’ values and add them to your project teams.

    Precursive OBX Conclusion

    While I like many features of Precursive OBX as a Kanban board for onboarding teams, I struggle to find its niche relative to other available products (JIRA). It might be a good fit if you want the flexibility of Salesforce to do a lot of customization.

    It is definitely more of a specialized tool that a broad Salesforce project management tool. If you are looking for a PSA tool, you’ll need to consider the full Precursive suite. If you are looking for a PMO tool, you’ll need to look elsewhere.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Detailed Review of Projectivity Salesforce Timesheet App

    Projectivity Salesforce Timesheet App - Steampunk Version

    Projectivity is reviewed against 200+ project management software requirements on a downloadable spreadsheet. Projectivity is scored on the cost management and resource management processes. This post provides a summary of the key strengths and weaknesses for both of the processes.

    Projectivity Summary Findings

    Projectivity is a Salesforce timesheet app by Atachh available on the Salesforce AppExchange. Projectivity is a dedicated Salesforce timesheet app, with time reporting and invoicing functionality. Overall, it has good functionality but not as good as the large professional services administration (PSA) tools. It might be a good option for a company that only needs basic resource management functionality for their projects. However, Projectivity uses its own ‘project’ object, so it is going to be difficult for a company to integrate it with the company’s own custom project object, or the project object from another project management app.

    I believe Projectivity might work for a company starting from scratch that would install Projectivity for the resource management functionality, and then build their own custom project management solution on top of Projectivity’s project object.

    Projectivity
    Total Score10%
    Cost Management23%
    Resource Management43%

    Download Projectivity Evaluation Spreadsheet

    Click here to add the Projectivity Excel spreadsheet to your basket and continue reading. Visit the basket page to complete the download.

    Projectivity Pricing

    The first five Projectivity licenses are free. Additional licenses are $10/user/month ($120/user/year). If implementing Projectivity, you will need to purchase a license for the project managers, the resource managers and anyone who will submit a timesheet.

    Projectivity Scoring Methodology

    I’ve been evaluating all of the Salesforce project management software and sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. When I come across novel functionality in the Salesforce project management software I’m evaluating I add it to the requirements list. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totals the ratings by process to show how the apps compare by process. Therefore, you can assess the Salesforce project management software based on which processes are the most important to you. In Projectivity’s case, only the Cost Management and Resource Management processes were applicable.

    Here are some links to help you research the app. You can confirm my scoring by installing Projectivity into a sandbox:

    Download Projectivity Evaluation Spreadsheet

    Click here to download the Projectivity Excel spreadsheet.

    Cost Management

    As a Salesforce timesheet app, Projectivity will calculate actual costs and billable fees from approved timesheets. It will also aggregate this data from multiple timesheets to support creating a customer invoice. Projectivity doesn’t actually create an invoice, but creates a JSON file which can be fed into another tool to publish and send the invoice.

    Strength: Customer-Specific Rate Cards

    Projectivity allows you to create a specific rate card for each resource that is specific to the customer or job. This allows you to vary pricing between customers or between projects for the same customer.

    Strength: Calculates Margin

    Each resource has a cost and a billing rate that varies between projects. This allows you to calculate actual profit margin for a project.

    One area of concern, is limiting access to people’s salary information. Many company’s I’ve worked with have addressed this by using an average ‘standard’ cost for resources. This means project and resource managers don’t have visibility to salary information. However, it also means the margin calculations are precise. You could also address this in Projectivity, by creating new permission sets that limit visibility to the resource cost to only certain individuals authorized to view salary information.

    Weakness: No Budget Planning Functionality

    It doesn’t have any rollup functionality to total the planned role costs for a total project budget. It only rolls up actual hours, not planned. You could work around this by creating custom reports which total the rate cards for planned project roles, and then entering the budget in the static project field.

    Weakness: Doesn’t Handle Expenses

    Not being able to report or invoice expenses is an extremely large gap for a Salesforce timesheet app.

    Weakness: Limited Billing Options

    It appears only really setup to handle T&M contracts based on actual hours, minus the materials (see above). It has a fixed cost option on a resource’s rate card, but I couldn’t figure out how this would be used to generate an invoice. There isn’t any option to bill per day which is popular in the consulting industry. There also isn’t an option to bill a higher rater for overtime.

    Weakness: Tracking and Forecasting Budget Variance

    It lacks any real functionality to calculate an estimate at completion (EAC) and compare this to the project’s budget to highlight any forecasted variance. This requires being able to total incurred costs and remaining forecasted costs adjusted by the project’s cost performance index (CPI).

    Resource Management

    This is Projectivity’s area of greatest strength, but it still falls short of fully-functional PSA tools. It is primarily a Salesforce timesheet app. It has a strong and clear process for defining skills, resources, project roles and matching these to fill project resource needs. It has a large shortfall in the ability to determine a person’s available capacity.

    Strength: Define Skills and Roles

    It has thorough functionality for defining skills and roles. These are used to identify people that match project resource needs.

    Strength: Project Access Control

    Projects are not public. The owner of the project has to grant access, and can limit whether the person has read only or edit access. This a feature lacking from much of the Salesforce project management software I’ve reviewed.

    Weakness: Determining Resource Capacity

    Its biggest shortfall is the Resource Console which is intended to show the resource manager a resource’s availability and project allocations. However, it doesn’t display the hours available or allocated for any period. So you aren’t able to match resource requests to the person’s availability. Also, the feature to identify resources which match a resource request appears to only match skills/roles and does not take into account a person’s availability.

    Projectivity Resource Console Screenshot

    In Conclusion

    If you are looking for a Salesforce timesheet app that only tracks hours (and not expenses), Projectivity may be an option for you. Otherwise, if you have a need for full resource management or project cost/profitability functionality, you should consider a full-feature PSA Tool. If you are looking for a full feature Salesforce project management software, you should consider broad PSA or PMO tools.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Detailed Review of Salesforce Professional Services Automation App

    Salesforce professional services automation robot

    Salesforce Professional Services Automation (PSA) is reviewed against 200+ project management software requirements on a downloadable spreadsheet. Salesforce Professional Services Automation is scored overall for each of the ten project management processes. This post provides a summary of the key strengths and weaknesses for each of the processes.

    Salesforce PSA Summary Findings

    The Salesforce PSA app by Salesforce Labs is overly simplified. It really only supports one process: Resource Management. It doesn’t even address much of the standard resource management functionality. I can’t even come up with one piece of unique functionality. Its only strength is that it is free, but I can’t imagine a professional services firm would find it very useful.

    Salesforce PSA Summary Scores

    Download Salesforce Professional Services Automation Evaluation Spreadsheet

    Click here to add the Salesforce Professional Services Automation Excel spreadsheet to your basket and continue reading. Visit the basket page to complete the download.

    Salesforce PSA Pricing

    It is free since it was created by Salesforce Labs. But, you get what you pay for it.

    Scoring Methodology

    I’ve been evaluating all of the Salesforce project management software and sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. When I come across novel functionality in the software I’m evaluating I add it to the requirements list. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totals the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you. You can confirm my scoring using the Salesforce PSA app test drive or by installing it into a sandbox

    Here are some links to help you research the app.

    Download Salesforce Professional Services Automation Evaluation Spreadsheet

    Click here to download the Salesforce Professional Services Automation Excel spreadsheet.

    Communications Management

    Salesforce PSA has virtually no communications management functionality. It has the standard chatter feature, and a project status field.

    Cost Management

    Salesforce PSA has the absolute minimum functionality you would want for a PSA tool. You can set a budget in a static field, and then track actual hours and expenses based on timesheet entries. It doesn’t have any way to rollup a budget value based on planned resources. It also doesn’t have any invoicing capabilities.

    Strength: Project Specific Rate Card

    It does support specific rates for a project, so that the same resource can be billed at different rates for different clients. This is functionality missing in some PSA tools.

    Weakness: No Budget Rollup

    It does not rollup the budget or estimated costs based on individual forecasted resources or expenses.

    Weakness: No Invoicing Functionality

    You can manually set the invoice status on an individual resource’s timesheet or expenses. However, there is no way to create a consolidated invoice across team members and to track partial payments or credits against the invoice.

    Integration Management

    Salesforce PSA has very little integration capabilities. About the only functionality it has is the ability for everyone to view the project description, project data, and to log issues. It is lacking any scope management, project access controls or program/portfolio groupings.

    Weakness: No Scope Management

    There are a couple descriptive fields on the project where you could summarize the scope, but there is no way to document the detailed scope and no way to issue change orders.

    Weakness: Single-Level Planning

    The only support object is a ‘project’. There isn’t any way to group or rollup projects to programs or portfolios. There isn’t any way to plan releases within a project.

    Procurement Management

    Salesforce PSA doesn’t have any procurement functionality.

    Quality Management

    Salesforce PSA doesn’t have any quality management functionality.

    Resource Management

    Salesforce PSA’s primary focus is resource management. It has the most functionality in this area, but it still has half the functionality of the best PSA tools.

    Strength: Project-Level Resource Allocation

    Resources are allocated to projects on a percentage basis. I believe this is a more practical approach compared to other PSA tools which allocate resources by hours to individual tasks. In other words, you can assign John Doe 50% to Project A and 50% to Project B.

    Strength: Visibility to Open Resource Requests

    Resources and their managers can view open and unfilled resource requests. They can then contact the staffing managers to express interest in the assignment.

    Weakness: No Time Series View of Resource Allocation

    There isn’t any view showing a time series across the top (day, week, month) and the resource’s availability and allocation for the time periods. This is a key tool for ensuring resources are properly allocated.

    Weakness: No Project Access Controls

    Access to the projects is wide open for any Salesforce user in the organization. There is no way to create confidential projects, to limit edit access or to limit access to financial data.

    Risk Management

    Salesforce PSA doesn’t have any risk management functionality.

    Schedule Management

    Salesforce PSA has virtually no scheduling functionality. The basic thing you can do is record the start, end and key milestone dates. You can also assign standard Salesforce tasks to the project. There isn’t any Gantt Chart or advanced scheduling functionality, like dependencies.

    Weakness: No Gantt Chart

    There isn’t any Gantt Chart, so there isn’t any way to create a detailed project plan.

    Scope Management

    Salesforce PSA doesn’t have any scope management functionality.

    Stakeholder Management

    Salesforce PSA doesn’t have any stakeholder management functionality. You could add some custom fields to the project object to track things like individual stakeholders.

    In Conclusion

    I can only imagine Salesforce Professional Services Automation app being implemented by a very small company that would eventually migrate to a fully functioning PSA tool. Check out my comparison page for reviews of the fully functioning PSA tools.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Kantata Review (SX) by a Project Manager

    Kantata Review (SX)

    This Kantata review of SX/Kimble concludes that Kantata SX should be on the software short list of any large company buying a PSA tool. Kantata pricing is expensive, with a minimum purchase of 50 seats so it is not ideal for small companies. Large companies can also consider it for a PMO or Salesforce project management solution if cost or resource management are high priorities. Otherwise, its extra functionality, cost and lack of change management are going to be issues for most PMO applications.

    In this Kantata review, Kantata SX is reviewed against 200+ project management software requirements. Kantata SX is reviewed and scored against each of the ten project management processes. This post provides a summary of the key strengths and weaknesses for each of the processes.

    Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Kantata SX quickly and thoroughly.

    Kantata Review (SX) Summary

    The Kantata SX app is a project management tool available on the Salesforce AppExchange. It was previously named Kimble. Kantata SX scores highest for resource management, and second for costs management among all the PSA tools I’ve reviewed.

    Kantata SX should not be confused with Kantata OX which is a separate cloud solution built outside of Salesforce, but which integrates with some Salesforce objects. Kantata OX was formerly named Mavenlink, and I have a separate review of OX.

    Kantata has a huge amount of professional services automation (PSA) tool functionality, and therefore should be included in anyone’s assessment of Salesforce PSA tools. It has excellent resource and cost management functionality, which are the main focus of PSA tools. However, it also has a very good scheduling tool which is rare in PSA tools.

    Its broad functionality also makes it an option for an internal project management office (PMO) tool. However, I believe most PMO shoppers will find lots of the functionality overkill for a PMO tool, while there are some large change management gaps. The relatively high cost would also make it prohibitive for most PMO applications.

    Kantata Pricing

    Kantata pricing isn’t published on their website, pricing is contract-based. Prices vary based upon the number of seats, license term, usage of each user, integrations, add-ons and support level. The minimum number of seats is 50. As of spring 2025, Kantata pricing will vary between $50-$110 per user based upon the above factors. Thus the annual minimum license cost for 50 users will range from $30K – $66K.

    Communications Management

    Kantata has the basic functionality to communicate project status. However, it doesn’t have any change management-related functionality around scheduling and tracking communications or training.

    Strength: Project Status Reporting

    It has strong functionality related to reporting project financial status, such as, profitability. It also has a unique feature that generates a notification to management if the project status changes.

    Weakness: Lacks Change Management

    It obviously was not built with a focus on change management. There isn’t any functionality focused on identifying stakeholders and the training or communications they require.

    Cost Management

    Cost Management is one of the processes in which Kantata excels. It appears to be very focused on planning and measuring project profitability. This is ideal for the management of a professional services firm.

    Strength: Invoicing

    It has strong invoicing functionality. It supports multiple billing types, milestone-based invoicing and custom rate cards per account. It will even track invoices and customer payments.

    Strength: Cost Metrics

    It has numerous metrics to measure the project’s financial performance: utilization, earned value, profit margin and estimate at completion.

    Strength: Expenses

    It has the ability to forecast and track actual expenses in detail. It also has the ability to require management approval of expenses, which is lacking from some other PSA tools.

    Weakness: Lacks Some Rate Types

    I couldn’t find any ability to support day rates rather than hourly rates. Day rates have become popular in the consulting industry. It also didn’t appear to support overtime rates, but these are fairly rare in my experience.

    Integration Management

    Overall, Kantata has good integration management functionality with only a few gaps. It has very advanced project access controls. It also supports the creation and routing of change orders. The main weaknesses are a lack of detailed documentation of the scope, and a lack of documentation of benefits to support a full business case.

    Strength: Change Orders

    Users have the ability to create change orders and to route them for approval. Budget changes can also be routed to the client for approval. This is functionality lacking from many other tools.

    Weakness: Lacks a Business Case

    Since it is a PSA tool focused on supporting the services firm, it isn’t surprising that it doesn’t have any functionality to support estimating and documenting a business case. It has lots of cost management functionality, but no functionality to document benefits and an overall ROI. This isn’t a gap for a PSA tool, but anyone looking for an internal PMO solution might consider this a gap.

    Weakness: Lacks Detailed Scope

    It lacks the ability to list a detailed scope by: people, process and technology. Thus, it also lacks the ability to track changes by system or organization.

    Procurement Management

    Kantata has strong procurement management functionality, with the ability track vendor spending against purchase orders and the ability to forecast project cash flows.

    Quality Management

    This is one of Kantata’s weakest areas. I suspect this is because it is not focused on software development firms. It basically doesn’t have any functionality focused on testing processes or software as part of project.

    Resource Management

    Resource management is Kantata’s greatest strength with a whopping coverage score of 93%. In fact, the only gap I could find was the ability to track people’s use of time off against their accrued allotment. I view this is a minor gap, since this is usually handled in company’s HR or payroll system.

    Strength: Everything

    Sort the scoring spreadsheet by the ‘Resource Management’ process and you’ll see I couldn’t find any major gaps. You can create very detailed resource demand forecasts by skill and then assigned name or unnamed resources. There is even one piece of functionality I’ve never seen before: the resource manager can publish openings so people can express their interest in working on the project.

    Strength: Project Access

    It has very detailed and robust functionality for controlling project access. A project team member can be given read or edit access to various components of the project. Most importantly, the access can be specific to the project which is unique among project management apps. For example, you can give a person edit access to the financials on one project but block their access on another project.

    It also has the ability to make projects confidential, so only team members have access. This is important for sensitive projects like mergers or staffing reductions. Making projects confidential is a feature lacking from many other tools.

    Risk Management

    Kantata has the basic required risk management functionality. The major gap, is that you can’t assign the risk or associated tasks to people.

    Weakness: Can’t Assign Tasks to Risk

    The most important aspect of a risk is to develop and action plan to address it. Therefore, ideally you could assign tasks tied an individual risk, as can be done in some other tools. Also, while the risk has a field for who identified the risk and who is the standard record owner, it doesn’t have a field for assigning the risk to someone to resolve it.

    Schedule Management

    The scheduling tool in Kantata is excellent, which is rare for PSA tools. The only better Salesforce scheduling tool I’ve found is Inspire Planner, and there are only a few feature differences between the two. Most PSA tools only support 2-3 levels of tasks, which greatly limits the work breakdown structure, but Kantata doesn’t have this limitation. It also supports critical paths, all dependency types and lag. I also consider it very important that it will synch Kantata tasks with Salesforce tasks for a single view of what user must complete.

    From a pure scheduling point of view, it only lacks the ability to define constraints and it doesn’t automatically reschedule successor tasks based on actual completion date. Most of the other gaps are related to features you would want for IT development, which doesn’t appear to be an area of focus.

    Strength: Gantt Chart

    Excellent! Very close to the Gantt Chart functionality found in MS Project. Only gaps are:

    • Constraints (i.e. Must Start On, As Early As Possible, etc.)
    • Rescheduling successor tasks based on actual dates
    • Load leveling of resources

    Strength: Synchs to Salesforce Tasks

    I consider it very important that there is a single location where a user can view all the tasks assigned to them. If users have to go to several locations to see all their tasks, they are going to miss some things. Tasks planned in Kantata will create identical Salesforce tasks, so a user has a single view. Note: the documentation mentioned this functionality for OX, so I’m assuming it also exists for SX.

    Weakness: IT/Agile Schedule Management

    It lacks several pieces of scheduling functionality which a systems development project would use. These are:

    • Releases and go-live dates
    • Sprints
    • Agile epics and themes
    • Dedicated user stories (can use the standard tasks)
    • Burndown reports

    Weakness: Inter-Project Dependencies

    It lacks the ability to document and collaborate on inter-projects dependencies. For example, Project A cannot go live until Project B delivers something.

    Scope Management

    Kantata has the two most important pieces of scope functionality: a detailed work breakdown structure and change orders. It only lacks the ability to document a detailed list of the scope by people, process and technology like would exist in a project charter.

    Stakeholder Management

    Stakeholder management is Kantata’s weakest area, and this relates to its lack of change management functionality. The only stakeholder-related functionality it has is the ability to assign people to the project team with a role of ‘stakeholder’. This falls far short of what is needed for change management, since change management planning is often done at the group rather than the individual level.

    Kantata Scoring Methodology

    WARNING: Kantata doesn’t provide a free trial or test drive that can be loaded from the Salesforce AppExchange. The company didn’t reply when I requested a free trial for purposes of this review, thus, I wasn’t able to put my hands on the software to personally test all the requirements. Therefore, this review is based on reviews of online demos and documentation.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. When I come across novel functionality in the software I’m evaluating I add it to the requirements list. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totals the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you.

    Here are some links to help you research the app:

    Kantata Review Conclusion

    Kantata SX should be on the software short list of any large company buying a PSA tool. The 50 seat minimum and high cost put Kantata pricing out of reach for small companies. The minimum annual license cost will be $35K.

    You can also consider it for a PMO or Salesforce project management solution if cost or resource management are high priorities. Otherwise, its extra functionality, cost and lack of change management are going to be issues for most PMO applications.

    If you found this Kantata review useful, please leave a comment.

    Regards,

    Brian

    Additional References

  • Resource Hero Review by a Project Manager

    Resource Hero a Salesforce Resource Planning App

    Resource Hero

    Resource Hero is a Salesforce resource planning app. It is best suited for a company that wants to manage resources at a high level like: opportunities or projects. It does not support managing resources at the task level. It would be an ideal Salesforce resource management app for a company project management office (PMO).

    In this post, Resource Hero is reviewed against 200+ project management software requirements on a downloadable spreadsheet. Resource Hero is scored only for resource management out of the ten project management processes. This post provides a summary of the key strengths and weaknesses for the resource management process.

    Resource Hero Summary Findings

    This is a detailed review of the Resource Hero Salesforce project management software available on the AppExchange. Resource Hero is a nifty tool. It would be ideal for a company managing resources at a high level like: opportunities or projects. It is not practical for a company that wants to manage resources at an individual task level. I actual think this is a strength because trying to manage resources at an individual task level is very impractical. Many of the Salesforce professional services administration (PSA) tools are structured around managing resources at a task level, so Resource Hero would be a good alternative. It would be ideal for an internal company project management office (PMO).

    Resource Hero is actually much better than the score below indicates. I estimate it has 80% of the functionality of much more expensive PSA tools. I had to give it partial credit because out-of-the-box it only manages resources for Salesforce Opportunities. However, it can be configured to assign resources to any Salesforce standard or custom object. So, it would have to be configured to assign resources to a project. I think such a configuration would only be a couple of hours of work.

    Purchase the scorecard spreadsheet with to evaluate Resource Hero quickly and thoroughly. Use the scorecard spreadsheet to compare Resource Hero side-by-side with other tools.

    Resource Hero Pricing

    It is $15/user/month, which equals $180/user/year. This is less than half many of the PSA tools available on the Salesforce AppExchange.

    Resource Management

    To use Resource Hero for project management you would configure it to assign resources to projects. This will allow you to assign hours, a cost rate and billing rate for that person for that specific project. A timesheet will then allow you to capture actuals hours and costs. Resource Hero then has standard reports and dashboards which will show the forecasted hours, costs, income and margins for the project over time.

    Resource Hero would be ideal for a company’s internal PMO to track resource assignments and forecast internal and external labor costs. You can assign a resource to multiple projects using a hours per week, and then review total allocations across all projects. You can also assign external resources and then forecast total costs per month.

    Strength: Assign People at the Project Level

    Most PSA tools sum labor from the individual task assignments to the total project. This is usually very impractical. Resource Hero allows you to simply assign X hours per week of a resource’s time to a project. You can also define a resource to an external resource, so you can estimate people which aren’t Salesforce users or contacts.

    Strength: Project-Specific Rates and Forecasts

    When assigning a resource to the project, you enter a specific cost and billing rate for the assignment. This is similar to a project-specific rate card. Allows forecasting of labor costs, labor revenue, utilization and profit margins.

    Weakness: Can’t Manage at the Task Level

    If you are a professional services company that wants to assign tasks with specific labor hours and then total the hours to the resource level, then Resource Hero is not the tool for you. It could be setup to rollup the task assignments to the project or resource, but this would require duplicating the hours assignment for the task in Resource Hero for every task.

    Weakness: Can’t Approve Timesheets and Expenses

    Resource Hero doesn’t support tracking people’s expenses or approving their timesheets and expenses. You will need a separate tool for expenses. You could create a custom approval or reports to serve the purpose of approving timesheets.

    Scoring Methodology

    I’ve been evaluating all of the Salesforce resource planning software and sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. When I come across novel functionality in the software I’m evaluating I add it to the requirements list. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    For Resource Hero, I only evaluated the Resource Management process and a few resource-related requirements in other processes. Therefore, I only included the overall score for Resource Management. The score is artificially low, because I had to assign ‘Yes – With Configuration’ to most requirements, because using Resource Hero with projects will require several hours of configuration. You can confirm my scoring by installing the free trial into a sandbox.

    Here are some links to help you research the app:

    In Conclusion

    If you have an internal PMO, and are looking for a Salesforce resource planning tool to supplement the rest of your project management solution, then you should take a close look at Resource Hero. If you are searching for a PSA tool, you should probably consider one of the more expensive tools that supports a much wider range of functionality like: invoicing and project planning.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Detailed Review of Varasi Program Management Salesforce App

    Japanese class scheduled using Varasi Program Management Salesforce app

    Varasi Program Management is reviewed against 200+ project management software requirements on a downloadable spreadsheet. Varasi Program Management is only scored for the communication management process out of the ten project management processes. This post provides a summary of the key strengths and weaknesses for the communication management processes.

    Varasi Program Management Summary Findings

    The Varasi Program Management app is a project management tool available on the Salesforce AppExchange for scheduling live training programs. Varasi Program Management refers to training ‘programs’ or other types of live events. It doesn’t refer to managing a large program which is a group of projects. Varasi Program Management is a good basic tool for managing live training and events. You can schedule multiple sessions for a program, then track enrollment and attendance, as well as, location details and expenses for the sessions.

    There are four large gaps which limit Varasi Program Management’s usefulness for project management. First, it can only be used for live training sessions like classroom training or webinars. The majority of project training is now done using computer-based training (CBT). Because Varasi is build around sessions, I couldn’t figure out any way students could be enrolled in a CBT and their completion tracked.

    The second gap is the ability for students to self-enroll. I didn’t see any practical way for students to view a list of available sessions and to self-enroll in a session. A student would have to access the Varasi Program Management app and know what program to access. Ideally, an app would assign a student to a program and they then could self-enroll in a specific schedule through a portal.

    The third gap is that students are defined as Salesforce Contacts, not Salesforce Users. So if you are planning internal training for an internal project you may have to setup your internal students as Salesforce Contacts in order to user Varasi Program Management.

    The last gap is a lack of any functionality to identify the training subjects and audiences as they relate to the changes being made by the project. The change management planning which would define the training sessions and audiences is outside of its scope.

    Varasi Summary Scores

    Download Varasi Evaluation Spreadsheet

    Click here to add the Varasi Excel spreadsheet to your basket and continue reading. Visit the basket page to complete the download.

    Varasi Program Management Pricing

    It is free.

    Varasi Program Management Scoring Methodology

    I’ve been evaluating all of the Salesforce project management software and sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. When I come across novel functionality in the software I’m evaluating I add it to the requirements list. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totals the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you. You can confirm my scoring using the Varasi Program Management test drive or by installing the free trial into a sandbox.

    Here are some links to help you research the app:

    Download Varasi Evaluation Spreadsheet

    Click here to download the Varasi Excel spreadsheet.

    Communications Management

    This is the only process relevant to Varasi Program Management. If you are looking for a tool to schedule and track live training sessions, you should take a close look at this tool. If you will have lots of computer-based training (CBT), then you should consider other tools like a training management system (TMS).

    Strength: Schedule Recurring Sessions

    When defining the sessions for a training program, you can create multiple sessions at once by setting up a recurring schedule, such as, 10 total sessions held every Tuesday and Thursday. It will even calculate the number of sessions required based on the total students and max class size.

    Strength: Track Session Details

    You can track session details such as:

    • Location and location contact
    • The instructor and assistants
    • Expenses
    • Enrollment and attendance

    Weakness: Doesn’t Support Computer-Based Training (CBT)

    Because it is built around training sessions, I couldn’t figure out any way Varasi Program Management could be used for enrolling and tracking completion of computer-based training (CBT). CBTs can be interactive training or simply watching a YouTube video. A CBT doesn’t have a specific session, it has an assignment and required completion date.

    Weakness: Doesn’t Support Self-Enrollment

    For a large project, you want to schedule various training session options and then have students self-enroll for a session that is convenient for their schedule. Technically, you could give Salesforce users access to Varasi and instruct them on how to find their assigned program and to enroll in a session, but this doesn’t seem very practical.

    Weakness: Students as Contacts

    Session students are defined as Salesforce Contacts. Therefore, if you are planning internal training where most of the students are Salesforce Users, you’d have to create a contact record for each student rather than using the existing user record.

    Weakness: Doesn’t Support Any Change Management Planning

    Varasi Program Management is simply a training scheduling tool. It doesn’t provide any functionality to plan what needs to be taught and who needs to receive the training.

    In Conclusion

    You should consider Varasi Program Management if you need a simple tool for scheduling external live training sessions. If you are looking for a tool to help plan change management or manage computer-based training you should research PMO or TMS tools.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Detailed Review of Resource Availability Checker Salesforce App

    Shogun trying to figure out why Resource Availability Checker keeps scheduling people who are on vaction.

    Resource Availability Checker is found to have a serious bug that makes it unusable.

    Resource Availability Checker App Summary Findings

    This is a super simple app used to identify which people with a certain skill set are available for a particular meeting time. The app is used for scheduling meetings as Salesforce Events.

    This isn’t a bad little app in concept, but it has a serious bug that would disqualify it from use within a company. The app doesn’t recognize a person is unavailable if they have an all-day event scheduled. So, you end up scheduling people for meetings when they are on vacation.

    How to Use the Resource Availability Checker App

    First, don’t. See the serious bug above. But if you insist, you must follow this process:

    • Create a custom lightning record page for the Event Object that includes the custom “Resource Availability Checker” component.
    • List all the relevant skills in a new custom object called “Skills”.
    • For each of the new skills, assign all the people with that skill to the related “Skill Qualification” object.

    Once the setup is complete, when you create an event, you can specify the skills required. When you click ‘Check Available Resources’ it will list the people who have availability on their calendars. You can then click on the name to add them to the meeting.

    Resource availability checker screenshot

    Pricing

    It is free.

    In Conclusion

    You can only use this app for scheduling if you are okay with it not recognizing all-day events. I’m not sure what use case would be okay with this, but maybe one exists.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Detailed Review of DayBack Salesforce App

    Working on Japanese calendar by hand instead of DayBack Salesforce app

    DayBack is reviewed against 200+ project management software requirements on a downloadable spreadsheet. DayBack is scored overall for each of the ten project management processes. This post provides a summary of the key strengths and weaknesses for each of the processes.

    DayBack Summary Findings

    This is a detailed review of the DayBack Salesforce project management software built by SeedCode. DayBack is a neat tool, beautifully implemented. The screens are well designed, it is super easy to learn and setup, and the online help is excellent. Unfortunately, I can only think of several project management use cases. Its primary functionality is scheduling resources to 15-minute increments. There isn’t much use for this in project management.

    Here are the project management use cases:

    • Consolidated List of Tasks. A user can get a consolidated view of all of their assigned tasks, even though you are using multiple apps to create tasks. For example, you may have Salesforce tasks and tasks created by your Salesforce project management app (Cloud Cache, TaskRay, etc.). It would be ideal if your project management app doesn’t create cloned Salesforce tasks.
    • Scheduling Deployments. If you are performing large detailed software deployments, you could create a custom object to schedule tasks to the minute and use DayBack to view the resulting total schedule. I’ve used these types of schedules for overnight deployments.
    • Finding Available Meeting Times. Scheduling meetings is a big part of a project manager’s job. If you use multiple calendars in your company like: Salesforce Events, Google Calendar or Microsoft 365 you can view the Salesforce Event, Google and Microsoft schedules side-by-side. The Google Calendar and Microsoft 365 calendars aren’t integrated with the Salesforce Events, but you can view them on the same page.

    You won’t be able to use DayBack for project resource management and scheduling. This is because:

    • Tasks are Only Displayed on the Due Date. Since project tasks are only assigned by day and not specific start/end times, DayBack only displays the task on the end date. So, a task isn’t displayed across the entire duration for start day to end day.
    • Doesn’t Display Work Allocated Against Availability. DayBack does have a charting function which could total the work allocated to a resource for a day. However, you would need an underlying object which stores the person’s assigned work (hours) by day per task. Most apps that have this underlying object are going to have a way to manage allocations, so why would you need DayBack?
    Screenshot of DayBack schedule

    DayBack Pricing

    Pricing starts at $19/user/month if billed yearly ($228/user/year). The price rises to $23/user/month if billed monthly ($276/user/year).

    This seems to be very reasonable pricing. However, if you were using it for simply the use case of providing users a consolidate list of their assigned tasks, the cost could become excessive. If you had 100 users who were assigned tasks, you would be paying $22,880 per year for a consolidated view.

    Now, if you are only buying licenses for project managers then the price seems extremely reasonable.

    DayBack Scoring Methodology

    Because it is a specialized tool, it wasn’t realistic to score it against my usual 200+ project management software requirements. Instead, I’ve summarized its relevant functionality.

    Here are some links to help you research the app:

    In Conclusion

    While DayBack is a great tool, it has limited relevance to project management. Use it if you need to find open times across multiple calendars, or for non-project management applications like scheduling field services.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Detailed Review of Neilon Project Management Salesforce App

    Shopkeeper invoicing customers using Salesforce Neilon Project Management app

    Neilon Project Management is reviewed against 200+ project management software requirements on a downloadable spreadsheet. Neilon Project Management is scored overall for each of the ten project management processes. This post provides a summary of the key strengths and weaknesses for each of the processes.

    Neilon Project Management Summary Findings

    Neilon Project Management app is primarily a professional services administration (PSA) tool with functionality limited to project quotation and invoicing. It also appears to have been built for a very specific use case for a certain type of project work. There are lots of use case-specific validation rules and field values which would have to be changed for most users.

    The invoicing is very simple. The invoice totals must be calculated elsewhere and you simply enter the invoice totals into the Neilon Project Management app. Neilon Project Management generates very emails as part of the process and tracks the open invoice until it is paid.

    Download Neilon Evaluation Spreadsheet

    Click here to add the Neilon Excel spreadsheet to your basket and continue reading. Visit the basket page to complete the download.

    Neilon Project Management Pricing

    Neilon Project Management is listed as a free app on the Salesforce AppExchange, but the Neilon Technologies website lists paid versions. The free version if available for up to 10 users. The next tier is a site license for $25/month ($300/year) for unlimited internal users and up to 200 community users. The final tier is $50/month ($600/year) for unlimited internal and community users.

    App Scoring Methodology

    I’ve been evaluating all of the Salesforce project management software and sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. When I come across novel functionality in the software I’m evaluating I add it to the requirements list. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totaled the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you. You can confirm my scoring using by installing Neilon Project Management for free.

    Here are some links to help you research the app:

    Download Neilon Evaluation Spreadsheet

    Click here to download the Neilon Excel spreadsheet.

    Communications Management

    The only communications management functionality in Neilon Project Management is the ability to identify stakeholders. However, it appears that Neilon may be referring to stakeholders as really project team members.

    It also gets some points because you could easily add status fields to the project object (called ‘Jobs’) to communicate the project status.

    Cost Management

    This is Neilon Project Management’s main functionality. It has the ability to record projects costs and to issue invoices. The main weakness is that it only tracks costs at the project level with a single data entry for different types of costs. There isn’t any way to record actual hours by worker and total to the project invoice. There also doesn’t appear any way to set a project budget and then track the actual costs as a variance to that budget.

    Strength: Different Invoicing Options

    It allows the user to select several different invoicing options such as, pre-paid or at completion. This appeared to all be one-and-done invoicing. I didn’t see a way to invoice a customer every week or every month for a long project.

    Strength: Automated Emails

    It will automatically generate several emails to the customer, such as, quotes and invoices.

    Weakness: Doesn’t Record and Rollup Actual Hours

    Invoices are created at the project level. There isn’t any functionality for people to enter time into timesheets and to allocate that time to a project.

    Weakness: Doesn’t Track Cost Variances

    There is only one field for project costs. So that supports both the forecasted budget for quotations and the actuals for invoices. You cannot quote a budget and then track variances from that budget over time.

    Integration Management

    Neilon Project Management isn’t really intended to support integration management processes, but it does check a few boxes. You can log project issues, and with some slight modifications you can add descriptive data about the project. The main weakness is a lack of reporting dashboards.

    Weakness: No Dashboards

    There aren’t any pre-built dashboards for management to track the progress of projects. There is a tab which lists projects which are ready to be invoiced and outstanding invoices that haven’t been paid.

    Procurement Management

    No procurement management functionality.

    Quality Management

    No quality management functionality.

    Resource Management

    Neilon Project Management doesn’t have the typical resource management functionality you see in a PSA tool, where you can view resource availability and track resource allocation across projects. The only functionality it has is the ability to identify project stakeholders and man days on the project. So, I believe what Neilon labels as ‘stakeholders’ are actually intended to be project team members. The problem is that you only give the stakeholder a start date and end date and total man days. You can’t use this view resource allocations by day, week or month.

    Weakness: Cannot Manage Resource Availability and Allocations

    There isn’t any way to view resource availability for assignment to a project. There also isn’t any way to view a resource’s total allocation across projects in a time period to know if they are over allocated.

    Risk Management

    No risk management functionality.

    Schedule Management

    There basically isn’t any scheduling functionality. The only two requirements Neilon Project Management fulfills is that you can record the overall project’s start and end date.

    Scope Management

    No scope management functionality.

    Weakness: No Scope or Change Orders

    There isn’t any way to capture the scope details of a project. You could add simple text field to the project object to meet the minimum requirement. However, it also lacks any way to address change orders.

    Stakeholder Management

    I’m not sure how to score this process. Neilon Project Management does have an object labeled ‘stakeholders’. However, it looks to me that this is more intended to capture project team members rather than to capture the audience for training and communication (i,e. change management).

    Strength: Identify Individual Stakeholders

    You can identify individual stakeholders, and you could customize the roles they are assigned.

    Weakness: Doesn’t Support Change Management

    You can’t identify groups as stakeholders and record how they will be impacted by the project.

    In Conclusion

    If you are looking for a simple invoicing tool, you may want to consider Neilon Project Management. However, I warn you that it appears to have been built around a very specific service and process. You most certainly will need to customize many of the picklist values and validation rules.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Detailed Review of Task Manager Salesforce App

    Samurai reviewing tasks on Salesforce Task Manager app

    Task Manager app is reviewed and found to provide a nice task view but to have limited overall usefulness.

    Task Manager Summary Findings

    First of all, Task Manager by Algoworks is not a full Salesforce project management app. It is actually simply a tab with a custom view of standard Salesforce tasks. Therefore, I did not perform my usual scoring against the 200+ project management software requirements. I consider this a specialty tool which you could install for free to complement your Salesforce project management solution.

    Task Manager provides a nice task view and some convenient filters. However, you probably don’t need it if you’ve installed a full-fledge Salesforce project management app. Secondly, since Task Manager only shows Salesforce tasks you could only use it with Salesforce project management apps which synch their tasks with Salesforce tasks.

    Task Manager Pricing

    Task Manager is free.

    Task Manager Scoring Methodology

    I didn’t use my standard scoring methodology where I score the app against 200+ project management software requirements. Instead, I loaded Task Manager into a sandbox environment, reviewed its documentation and have summarized my findings in this post.

    Here are some links to help you research the app:

    Schedule Management

    Task Manager can only be used for project management if your scheduling tool synchs its tasks with standard Salesforce tasks. This is because Task Manager only displays standard Salesforce tasks.

    Task Manager has the following pieces of functionality: main feature is that it has a stoplight based on the status of the active tasks: red for overdue, yellow with upcoming tasks, and green for future tasks. It also allows you to filter the tasks based upon the stoplight color. You can also search the tasks by name. Finally, you can filter the tasks based upon: ‘All Active Tasks’, ‘Delegated Tasks’ or ‘Tasks without Due Date’.

    • A stoplight based on the status of the active tasks: red for overdue, yellow with upcoming tasks, and green for future tasks
    • Ability to filter the tasks based upon the stoplight color
    • Ability to search the tasks by name
    • Ability to filter the tasks based upon: ‘All Active Tasks’, ‘Delegated Tasks’ or ‘Tasks without Due Date’
    Task Manager by Algoworks screenshot

    In Conclusion

    If you really like the formatting of the Task Manager task view, then by all means, download this free tool. However, most Salesforce project management apps are going to have similar functionality so installing Task Manager won’t be necessary.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Detailed Review of Inspire Planner Salesforce App

    Inspire Planner Salesforce project management app in Edo Period Japan

    Inspire Planner has the most robust scheduling functionality among the Salesforce project management tools I’ve reviewed. It has the same base scheduling functionality as Microsoft Project. It only lacks some of Project’s work effort scheduling and resource load leveling functionality.

    Inspire Planner was reviewed against 200+ Salesforce project management software requirements on a downloadable spreadsheet. Inspire Planner is scored overall and for each of the ten project management processes. This post provides a summary of the key strengths and weaknesses for each of the processes.

    Inspire Planner Summary Findings

    Inspire Planner is focused on scheduling, and has the best project scheduling functionality I’ve found among the native Salesforce project management tools. If you are simply looking for a Salesforce scheduling tool, then Inspire Planner should be on your short list for review.

    If you are looking for a broad professional services administration (PSA), project management organization (PMO) or project portfolio management (PPM) solution you should consider integrating Inspire Planner’s scheduling functionality with another solution. I know several Inspire Planner customers that have done this, building their own project object and linking it to Inspire Planner.

    While Inspire Planner’s scheduling functionality is thorough it lacks some of advanced features found in Microsoft Project. It lacks the ability to schedule based upon work effort rather than duration. It also lacks the ability to resource load level a schedule. Resource load leveling is the ability to push out tasks so a resource is never over allocated.

    Despite its focus on scheduling, Inspire Planner does have some functionality in each of the project management processes and has resource management capabilities approaching those of a PSA tool.

    Inspire Planner Scores by PM Process

    Download Inspire Planner Evaluation Spreadsheet

    Click here to add the Inspire Planner Excel spreadsheet to your basket and continue reading. Visit the basket page to complete the download.

    Inspire Planner Pricing

    Inspire Planner is $34/user/month with a 10 user minimum. This equals an initial minimum investment of $4,080 a year. Any Salesforce user that will create or view Inspire Planner data will need a license, thus the license count can add up quick if you have users assigned tasks and they are updating them in Inspire Planner.

    Inspire Planner tasks are cloned as Salesforce Tasks and they are synched and can be updated. Therefore, technically you should be able to assign users tasks and have them view and update them as Salesforce Tasks without an Inspire Planner license. This could minimize some of your licensing costs, so you don’t need to purchase licenses for users who are rarely assigned tasks. You should discuss this option with Inspire Planner as there may be some other implications:

    • While the license can’t be enforced technically to access Salesforce Tasks created from Inspire Planner Tasks, Inspire Planner’s terms and conditions may require it.
    • Inspire Planner has some custom Salesforce Task page layouts and lightning web components which may not be accessible without a license. You could replicate these yourself if necessary.

    Inspire Planner also has an external portal for non-Salesforce users outside your company to be assigned tasks and to view the project. I couldn’t find any documentation stating that these users would need a license.

    Scoring Methodology

    I’ve been evaluating all of the Salesforce project management software and am sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. When I come across novel functionality in the software I’m evaluating I add it to the requirements list. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totaled the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you. You can confirm my scoring using the Inspire Planner test drive or by installing the free trial into a sandbox.

    Here are some links to help you research the app:

    Download Inspire Planner Evaluation Spreadsheet

    Click here to download the Inspire Planner Excel spreadsheet.

    Communications Management

    Inspire Planner is not intended to be a change management tool (i.e. training and communication) but it does use Salesforce’s Chatter tool for project collaboration. It also has lots of functionality to report the project status.

    Strength: Automatic Status Report

    Inspire Planner will create a weekly PDF status report for distribution to project stakeholders. Read More.

    Strength: Lots of Status Fields

    It has an overall status field and sub-fields and comments for project schedule, budget and scope.

    Weakness: Not a Change Management Tool

    It doesn’t have any functionality to plan or track project communications or training. You could handle some of this by creating a project schedule dedicated to the communication or training tasks.

    Cost Management

    Inspire Planner captures all costs and labor at the task level. The task values then rollup to the project level. It also captures a rate per resource so that labor costs can be calculated. However, it lacks the full cost, expense and invoicing functionality needed for a PSA tool. It also cannot rollup budgeted or actual costs to a program, parent project or release level. You could build custom reports to perform this summations.

    Relying solely on rolling up the budget and costs from individual tasks could also be problematic when planning the project. There isn’t any way to note a total budget value at the beginning of a project without having created all the supporting tasks. You could create ‘dummy’ tasks to just house the initial budget estimates. But it would then become problematic as you add detailed costs with individual tasks.

    Strength: Sums Project Costs

    Inspire Planner automatically sums all task budgeted and actual costs to the project level.

    Strength: Calculates Earned Value, EAC and CPI

    Earned value, estimate at completion (EAC) and cost performance index (CPI) are all calculated automatically.

    Weakness: Only Sums to the Project Level

    Costs are not rolled up to the parent project (i.e. program), portfolio or release levels. You could build custom reports to generate these sums.

    Weakness: No Invoicing Capabilities

    Inspire Planner lacks common PSA functionality to support generating customer invoices from a customer specific rate card and actual hours worked.

    Integration Management

    Inspire Planner supports basic integration functionality. It supports planning at the release, project, parent project (i.e. program) and portfolio levels. It has the ability to limit access to confidential projects. It can also log project risks and issues.

    The major gaps are in the area of documenting the business case or project scope. It also doesn’t come with any standard approval routings. So it doesn’t support change orders, routing timesheets for approvals, or routing projects for approval upon completing gates.

    Strength: Multi-Level Planning

    Inspire planner support planning and reporting at the release, project, parent project (i.e. program) and portfolio levels. Please note that task values such as costs or hours only roll up to the project level. Also, the release level is only available for the Agile project type.

    Strength: Risks and Issues

    Project risks and issues can be documented. This is done through custom object with a checkbox to denote if the record is a risk or issue. I take some exception with this approach. I believe an issue is just a task to answer a question: “How are we going to ….”. So I’d prefer to see issues as simply a task type.

    Weakness: Missing Business Case and Scope

    There isn’t any functionality to capture benefits which would form the basis for a business case where benefits offset projected costs. A simple text field could be added to list benefits, but this wouldn’t allow tracking realization of the benefits.

    There aren’t any fields for capturing scope. Clearly stating scope is critical to reaching consensus among stakeholders. A text field can easily be added to summarize the scope, but will not capture the full details or dedicated records.

    Weakness: No Approval Routings

    No standard approval routings are provided with the app. Standard approvals often associated with projects are: change orders, stage gate, and timesheets. You can build your own approvals using standard Salesforce functionality, however if you want highly dynamic or automated approvals you may want to design them to accurately estimate the effort to build them yourself.

    For example, I once built an approval that routes a project to the steering committee members. Building this to handle varying numbers of steering committee members per project was a significant amount of work.

    Procurement Management

    Inspire Planner doesn’t really have any procurement management functionality. You could add some custom fields and build some reports to allow you to forecast cash flows and capture vendor spend against contracts.

    Quality Management

    Inspire Planner doesn’t really have any functionality for testing software or other quality control. You could add an ‘acceptance criteria’ field to the user stories in the Agile projects. You could also add a ‘Test’ column in the Kanban to designate user stories that are ready to test.

    Resource Management

    Inspire Planner has strong functionality in the resource management process. The only significant gap I found is the ability to plan and forecast resources at a high level a the beginning of a project. All the planning starts at the task level. So there isn’t any way to simply plan resources at the project level. For example to allocate a person or a skill to a project at 50% of their time.

    Strength: Time Series Resource Allocation

    There is a very clean and intuitive screen where a manager can review resource allocations across all projects for different time periods: day, week, month, quarter. The manager can view the data as hours or as percentage of available time. Please note: I found a bug where the percentage allocation is only calculated correctly by day.

    Weakness: Financial Access

    There isn’t a way to block a team member’s access to financial data for a specific project. There are instances where a project manager doesn’t want all team members to see how much things cost or how much is being paid to a certain vendor. You could create a custom permission set which prevents certain users from viewing financial data on any projects. But, you won’t be able to control this on a project-by-project basis.

    Risk Management

    Inspire Planner has all the risk management functionality you should need. The only gap is the lack of a risk matrix that lists all risks with a quantitative measures of the impact to the budget or schedule. However, I’ve never found risk matrices to be very useful.

    One thing to note is that a risk can be related to an Inspire Planner task to address the risk. I think it would be more helpful to associate multiple Inspire Planner tasks to a single risk. However, this can be addressed in one of two ways. First, you could associate the risk to a task with a checklist. Or, you could associate multiple standard Salesforce tasks to the risk.

    Schedule Management

    Schedule Management is Inspire Planner’s main strength. It is the best native Salesforce scheduling tool I have found. It has all the basic scheduling functionality found in Microsoft Project. It only lacks some of Project’s advanced features around work effort scheduling and resource load leveling. For example, it is the only native Salesforce tool I’ve found which supports constraints (i.e. Must Finish On, Must Start On, etc.).

    It only has two gaps which I think are significant. First, it doesn’t re-schedule downstream dependent tasks based upon the actual completion date. So if a preceding task finishes late or early, the expected finish date needs to be updated along with the actual finish date to update the downstream tasks.

    Second, it doesn’t have any functionality to address inter-project dependencies. Meaning, you cannot record that a project or task is dependent upon a deliverable from another project. You cannot create dependencies between tasks on different projects.

    Strength: Advanced Scheduling Features

    It supports all dependency types (Finish-Start, Finish-Finish, etc.), predecessor lag and all but two types of constraints. It will also display the critical path. These are features often not supported by the native Salesforce scheduling tools. The only two types of constraints it does not support are: As Soon As Possible and As Late As Possible.

    Strength: Large Work Breakdown Structure

    You can create a large number of task groupings by simply indenting the tasks as you can do in Microsoft Project. This gives you the flexibility to create the work breakdown structure you want. I often use at least four to five levels within my project schedules. Most native Salesforce scheduling tools only support one or two levels.

    Strength: Good Gantt Design

    I really like the Gantt design as it mimics the Microsoft Project design which I’m used to you and I find very efficient for building project plans. You customize the task data columns listed on the left side of the window. It is very easy to create tasks and to create task groups. Tasks can be re-ordered by dragging and dropping. Dependencies can be created by dragging and dropping.

    Weakness: Doesn’t Reschedule Based on Actual Finish Date

    If you build a chain of dependencies between tasks, the downstream tasks are only rescheduled if the estimated finish date is updated. The downstream tasks are not rescheduled when the actual finish date is updated. This can be worked around by also updating the estimated finish date when a task is completed.

    Weakness: Doesn’t Support Inter-Project Dependencies

    There isn’t any way to record or track inter-project dependencies. You cannot make a task on one project dependent upon the completion of a task on another project. You can work around this to some extent by duplicating the other project’s task on your project and assigning the task to the other project’s project manager. However, your project’s schedule won’t be automatically updated if the other project slips.

    Scope Management

    Inspire Planner only has two pieces of scope management functionality. First, it supports creating a detailed work breakdown structure. Secondly, the Agile project type supports defining components to be built.

    Most Salesforce native schedule tools limit the levels of tasks that can be grouped in the Gantt chart to 1 or 2 levels. Inspire Planner does not have such a limitation. This allows you to thoroughly organize the work by a logical structure: stage, release and deliverable/component.

    Technical components can be defined and inventoried so the team has a clear understanding of what needs to be built. At the beginning of projects, I use components to estimate the overall project effort and required resources. The component object is only available when using the Agile project type.

    There isn’t a way to document details about what is in scope and what is out of scope for the project. Ideally, scope is defined within three categories: people/org, processes and technology/systems.

    Cannot create change orders and route them for approval when the scope, budget or schedule change from the original plan.

    Stakeholder Management

    Inspire Planner is not intended to be a change management tool and therefore, doesn’t have any real functionality to document or manage project stakeholders. You are able to assign custom project roles, so you could create a ‘steering committee’ role and assign individuals to the team. This would at least give your most important stakeholders access to the project.

    In Conclusion

    Inspire Planner is a fantastic native Salesforce project management tool for scheduling. I haven’t found anything better and have recommended it to clients. So if you are simply looking for a native Salesforce scheduling tool, look no further. You can review key differentiators between the top four Salesforce project management scheduling tools here.

    However, if you are looking for a fully functional PSA tool for your professional services firm, you will want to consider other dedicated PSA apps. Though you will find that most PSA scheduling tools will lack the functionality of Inspire Planner.

    If you are looking for a broad PMO or PPM tool, you should consider integrating other apps with Inspire Planner. In fact, I built a cutting edge project management solution for a client using Inspire Planner integrated with a custom project object and other tools.

    This was an automated solution where the Inspire Planner schedules used standard tasks which then drove automated workflows. When the user opened their assigned task they were presented the project-specific documentation required to perform the task, a screen flow to walk them to the process, and links to procedure documentation to explain the task. This solution integrated the flexibility of scheduling the tasks with the consistency of standard workflows and procedures. You can read more about it here.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Detailed Review of TaskRay Salesforce App

    TaskRay is a post-sales onboarding task management tool. It has a very clean and intuitive user interface, as well as, lots of task view options: Kanban board, Gantt, Calendar, etc. It is well-suited for this very narrow use case, but it is lacking key functionality to serve as a professional services administration (PSA) tool or a general project management tool.

    TaskRay is reviewed against 200+ project management software requirements on a downloadable spreadsheet. TaskRay is scored overall and for each of the ten project management processes. This post provides a summary of the key strengths and weaknesses for each of the processes.

    TaskRay Summary of Findings

    TaskRay is more of a task management tool than a scheduling or project management tool. It supports start up tasks once a project has been sold by a professional services firm. This is the same functionality found in many PSA tools. However, TaskRay lacks much of the functionality found in the leading PSA tools (Kantata, Certinina, etc.).

    When compared to the project management process as defined in the PMBOK, TaskRay has a coverage of 34% with complete gaps in cost, procurement and risk management. It basically has two main areas of functionality: task scheduling and time reporting. It seems odd that given its purpose as an onboarding tool, it doesn’t have the ability to translate actual reported hours into costs or customer invoices. The table below shows the coverage of each process as a percentage basis compared to full coverage.

    WARNING: This is a review of the Premium version of TaskRay. The other versions of TaskRay have limited resource management capabilities (see pricing section).

    TaskRay
    Total Score34%
    Communications Management14%
    Cost Management9%
    Integration Management29%
    Procurement Management0%
    Quality Management17%
    Resource Management57%
    Risk Management0%
    Schedule Management58%
    Scope Management6%
    Stakeholder Management17%

    Download TaskRay Evaluation Spreadsheet

    Click here to add the TaskRay Excel spreadsheet to your basket and continue reading. Visit the basket page to complete the download.

    TaskRay Pricing

    TaskRay has three packages with different levels of pricing. The premium package is required for resource management functionality which is a core feature of PSA tools. TaskRay’s pricing for the premium package is high when compared with other PSA tools.

    Just keep in mind that anyone who will edit or view any project data will require a license. This will include anyone who will view or complete a TaskRay task or any manager who wants to view a project status. This user count can add up quickly.

    • Starter – The lowest price option is $25/user/month. There is also reference to a site license option, as well as, a 10 person starter pack.
    • Standard – Median price of $40/user/month. Adds the following functionality:
      • Dashboards
      • External collaboration (i.e. communities)
      • Time tracking
    • Premium – Highest price of $60/user/month. Adds the following functionality:
      • Resource management
      • Advanced work management controls for task weighting and ongoing progress, and putting projects on hold

    Scoring Methodology

    I’ve been evaluating all of the Salesforce project management software and sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. When I come across novel functionality in the software I’m evaluating I add it to the requirements list. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totaled the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you. You can confirm my scoring using the TaskRay test drive or by installing the free trial into a sandbox.

    WARNING: I was only able to load the standard TaskRay package in my sandbox to evaluate it. The additional resource management functionality available with the premium version had to be assessed using demos and documentation. The resource management functionality in the premium version, was acquired by purchasing Flux Capacity.

    Here are some links to help you research the app:

    Download TaskRay Evaluation Spreadsheet

    Click here to download the TaskRay Excel spreadsheet.

    Communications Management

    TaskRay (TR) is not intended to be used for change management and therefore, has little communication functionality. It does support Chatter for collaboration on the project. It also supports basic project status reporting which can be easily enhanced by adding fields to the project object.

    Cost Management

    TaskRay doesn’t have any cost management functionality. As an onboarding tool, it is similar to a PSA tool, but it lacks any ability to track costs or to generate invoices based on hours worked. This is strange since it does capture actual hours and whether they are billable. However, it doesn’t have the ability to record rates to turn hours into billable dollars. It also doesn’t have any ability to capture and bill expenses.

    Integration Management

    Integration Management is the process of coordinating the overall project and the different project management processes. TaskRay has limited functionality in this area.

    Strength: Confidential Projects

    Confidential projects can be created where only project team members have access to the project. You can even control the level of access each team member has to the project: read or read/write.

    Strength: Assigned Task Notification

    TaskRay sends the owner of a task an email notification when they are assigned a new task.

    Strength: Multiple Schedule Views

    TaskRay supports a whopping five views of project tasks: Kanban Board, Calendar, Gantt Chart, Spreadsheet and Row. The Kanban Board columns can be customized to match your Agile approach.

    Gantt view in TaskRay Salesforce app

    Weakness: No Programs or Portfolios

    TaskRay doesn’t support grouping projects under larger programs or portfolios. This wouldn’t be needed for post-sales onboarding but is a main requirement if it is going to be used for general project management.

    Weakness: Risks and Issues

    TaskRay does not support documenting project risk or issues.

    Procurement Management

    TaskRay doesn’t have any procurement management functionality.

    Quality Management

    TaskRay doesn’t have any of the testing functionality you would need for a software development project. You could use the tasks as user stories and add an acceptance criteria field to the task.

    Resource Management

    TaskRay has basic resource management capabilities that should suffice for very simple projects. It does not have the robust resource management capabilities a professional services firm is going to need, and that is typically found in a PSA tool.

    Strengths: Defining Project Team

    TaskRay has a clean and intuitive interface for defining the project team. It also supports customizing the level of project access by individual team member.

    A very helpful feature is that you can build project templates where tasks are assigned to a role. Once the project is created from the template you can assign an individual to the role, and all the related tasks will be automatically updated. This avoids having to update hundreds of tasks with resource assignments.

    Weakness: Lacks Resource Allocation Time Series Reports

    TaskRay lacks the ability to view resource allocations and availability across a time series (i.e. day, week, month). In other words, most PSA tools have a grid view with days, weeks or months as the columns and a resources as the rows. This allows the project manager to see over allocations over a certain time period. TaskRay only offers reports where you can view this information for a single month or day.

    Weakness: Lacks Skill Assignments

    TaskRay lacks the ability to define skills and assign multiple skills to a person. You can assign a single role to a resource. This is not going to be sufficient for software development teams where you need to plan resources based on specific technical skills.

    Risk Management

    TaskRay doesn’t have any functionality to record and mitigate project risks.

    Schedule Management

    Schedule Management is TaskRay’s greatest strength. It supports five views of the task schedule (see above) and the user interface is very clean and intuitive. The Gantt chart functionality is on par with the other Salesforce scheduling apps. Unfortunately it has three gaps which limit it to only very simple projects:

    • One level of work breakdown structure
    • Doesn’t reschedule based on actual completion dates
    • No critical path

    Strength: Multiple Schedule Views

    TaskRay supports a whopping five views of project tasks: Kanban Board, Calendar, Gantt Chart, Spreadsheet and Row. The Kanban Board columns can be customized to match your Agile approach.

    Strength: Project Templates

    New projects can be created from standard templates. If you know how to build Salesforce Flows, you can also build a custom flow to automatically create projects when an opportunity closes. It also has a nice feature where you can assign a person to a template role and all tasks with that role will be updated with the specific person as owner of the tasks.

    Strength: Task Predecessors

    TaskRay supports all predecessor types: Finish-Finish, Start-Start, Start-Finish and Finish-Start. Multiple predecessors can be assigned to a single task with lags.

    The project manager can even assign a task from another project as a predecessor. The caveat is that the succeeding tasks will not be rescheduled based on this external project predecessor. But, it does allow the project manager to note external project dependencies.

    One gap in the predecessors, is that succeeding tasks are only rescheduled when the preceding task’s estimated end date changes. If the preceding task’s actual end date varies from the scheduled date, the downstream tasks are not rescheduled.

    Another gap is that it doesn’t support display the standard task predecessor notation in the Gantt View. For example: “10.1FS+1d”.

    Strength: Assign Tasks to External Contacts

    TaskRay can assign tasks to external contacts. The external contact will receive an email notifying them of the assigned task and can even mark the task as complete by clicking a link in the email.

    Strength: Baselines

    TaskRay has a very easy to use baseline feature. You can take multiple snapshots of the schedule and then select which baseline is displayed in the Gantt Chart view.

    Weakness: One Level Work Breakdown Structure

    TaskRay only allows one level of work breakdown structure. This means you can create a task group and then tasks within that group. You can’t indent any task to create a new group as you can in Microsoft Project. This means you could not create the following hierarchy: Release 1/Financial Interface/Task 1. In large, complex projects it is not unusual to have a work breakdown structure with at least four or five levels.

    Weakness: Doesn’t Reschedule Based on Actual Completion Dates

    You can setup predecessors and it will reschedule downstream tasks based on the preceding task’s estimated start or finish date. However, when you start/complete a task, it doesn’t reschedule the downstream tasks based upon the actual start/finish date. You can work around this by also updating the estimated date to match the actual start/finish date.

    Weakness: No Critical Path

    TaskRay does not calculate a critical path. I find this very useful in large complex projects, because it tells me where I need to focus my efforts to ensure the project completes on schedule.

    Scope Management

    TaskRay doesn’t have any functionality to record the project scope or to issue change orders for approval when the scope changes.

    Stakeholder Management

    TaskRay doesn’t have any significant stakeholder or change management capabilities. You can use the role feature to assign people the roles of ‘Stakeholder’ or ‘Steering Committee Member’, but this is about it.

    In Conclusion

    If you are looking for a simple-to-use scheduling tool, TaskRay may suit your needs. However, if you are looking for a PSA tool or general Salesforce project management (PMO/PPM) tool you should consider other options.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Flowdometer Reviewed by a Project Manager

    Flowdometer Salesforce project management app

    Flowdometer is a neat tool for measuring the elapsed time of standard process or project steps in Salesforce. Flowdometer is a Salesforce app listed on the AppExchange.

    All My Project Management Tool Reviews

    I have personally reviewed many of project management tools, including dozens of the Salesforce project management apps. I’m continually adding more reviews.

    Summary of Findings

    Flowdometer is a specialized free app for measuring the time elapsed for a Salesforce object to be updated. It is intended to be used for standard processes like customer installations to measure performance to goals or service level agreements. The key here, is that it needs to be used for a standard flow or process. It isn’t very applicable to custom projects like an internal re-engineering effort or software development project.

    Flowdometer would be a very useful Salesforce app for any organization wanting to measure the performance of their sales force, customer service or their install/implementation projects. In the case of sales, you can measure the time to qualify or convert a lead, or the time to qualify or close an opportunity. For customer service you can measure the time to close a case. For product installations you can measure the time to complete the standard installation steps/stages.

    I don’t think you’d be able to use the tool to measure standard cycle times for tasks in a project plan/schedule. I built a project development solution for a solar developer that used standard project templates with standard task IDs. You might be able to use Flowdometer as a design guide for building a similar solution to measure cycle time of such standard tasks in a project plan.

    Flowdometer Pricing

    Flowdometer is free. If you would like help customizing your Flowdometer solution, Muse Operations provides Salesforce development services.

    How Does Flowdometer Work?

    I must be stupid, because it took me a little while to figure out how Flowdometer worked, but once I did, it was pretty obvious. There are two main objects: flows and steps. Steps are detail (child) objects of the master (parent) flows. Every time you create a record of an object that is being tracked, a Salesforce record-triggered flow creates a Flowdometer flow record. Child step records are created every time the field being measured is updated, along with a time. For example, if you are measuring opportunities: a Flowdometer flow record is created when the opportunity is created. A step record is created every time the stage field is updated (prospecting, qualification, etc.).

    Flowdometer also has functionality which creates a standard goal for each step record. And it has detailed reporting functionality built to present all the step and flow measures.

    Can Flowdometer be Used for Custom Projects?

    Yes, but for the custom projects I typically work on (re-engineering, software development, Six Sigma, product development, etc.) it would have limited usefulness. There are standard stages for the various custom project types, so you could measure the time to complete the standard stages based on the type of project. It would probably be most useful to measure the early stages of the projects to ensure projects aren’t being blocked or aren’t stuck in analysis paralysis. The build or implement stages are going to vary too much between projects to yield useful metrics.

    How Would I Use Flowdometer to Measure Projects?

    First, you need to have a custom project object which stores information about your individual projects. You could build your own project object or use one of the various Salesforce project management apps: Mission Control, Milestone PM, Project Lifecycle Pro, etc.

    Next, you need a standard status or stage field for your projects. So if you were a home builder you’d need stages like: land purchased, designed, land cleared, foundation, framing, etc. And, you need to make sure people update these status/stage values in a timely manner. Flowdometer measures when the status/stage field was updated, so if your production supervisor doesn’t get around to updating the status/stage for three days your data is going to be incorrect.

    Finally you need to setup Flowdometer to measure the standard status or stage field in your project object. Flowdometer provides detailed documentation on how to setup measurements for a custom object. Basically, you would create a Salesforce record-triggered flow off your custom project object to create the flow and step records. You can create the new Salesforce flow using the Opportunity flow as a template. Then you simply change the fields assigned to the subflow variables to match your custom object. The varCurrentFieldTracked would equal your project status/stage you want to measure.

    Sample Flowdometer flow
    Flowdometer Flow Template
    Flowdometer Subflow Variables

    Flowdometer Scoring Methodology

    I didn’t perform my typical scoring methodology for Flowdometer, because it is a specialized tool and not a broad project management software solution. So, scoring it against 200 project management requirements wouldn’t be relevant. Flowdometer would fall under the Integration Management/Monitor and Control Project Work part of the PMBOK project management process. I’ve added a new requirement to my spreadsheet to measure standard stage cycle times.

    To review Flowdometer, I reviewed the demo and the available documentation. I also installed Flowdometer into a sandbox environment to review the custom objects and flows. I also performed some tests by creating and updating opportunities.

    You can perform your own assessment by loading Flowdometer into a sandbox:

    In Conclusion

    Flowdometer should be considered by any company wanting to measure standard cycle time for the various stages of: the sales process, customer service cases, or installation projects. Unlike many of the free apps on Salesforce AppExchange I did not find any bugs when I was testing Flowdometer so it appears to be well built and maintained.

    Regards,

    Brian

    Additional References

  • Mission Control Salesforce App Reviewed by a Project Manager

    Mission Control Salesforce App

    Mission Control Salesforce App

    The Mission Control Salesforce app is one of the best PSA (professional services automation) apps available on the Salesforce platform. Mission Control’s greatest strength is in resource management. It is ideal for Salesforce customers that want to track resources to the individual task level. Besides resource management, Mission Control project management functionality is also strong in: cost management and schedule management.

    Mission Control Summary of Findings

    Overall, Mission Control Salesforce app (MC) is incredibly detailed. I believe this may be its greatest strength, as well as, its greatest weakness. Mission Control is a professional service administration (PSA) tool, so if you are a professional services firm that plans and tracks every minute of people’s time, then Mission Control is the tool for you. However, I’ve never found this level of planning realistic for internal software or business improvement projects. I think for general applications, project managers will find the level of detail in Mission Control overwhelming.

    If you’d like to learn more, keep reading for a detailed review. The Mission Control Salesforce app review is based upon a fit/gap analysis of 200+ project management software requirements. The fit/gap analysis is summarized with scores for each of the ten project management processes. Furthermore, I provide a summary of the key strengths and weaknesses for each of the processes within this post.

    When compared to the project management process as defined in the PMBOK the Mission Control Salesforce app has a coverage of 59% with some coverage in all the processes. As a PSA tool, it scores highest in cost and resource management. The table below shows the coverage of each process as a percentage basis compared to full coverage.

    Mission Control Salesforce App Summary Scores

    Overwhelmed trying to find the best PSA tool? Give me your functionality priorities and I will give you a shortlist of 3-5 PSA tools that best suit your needs. You can then focus your detailed assessments on only a few tools. Saves you weeks of research and demos.

    Mission Control Salesforce App Pricing

    Mission Control Salesforce app’s pricing is straight forward it is $39/month/user with a five seat minimum. So it requires a minimum starting investment of $2,340/year. Just keep in mind that anyone who will edit or view any Mission Control project management data will require a license. This will include anyone assigned a Mission Control task and will view or complete it in Mission Control or any manager who wants to view a project status. This user count can add up quickly.

    I don’t think users assigned a Mission Control task that synchs to Salesforce tasks will require a Mission Control license, but you should confirm this with Mission Control. I wasn’t able to test this as license requirements aren’t enforced in a sandbox environment. Here is what I mean: when a task (Mission Control calls them ‘actions’) is created in Mission Control, you have the option of also creating a duplicate Salesforce task which is synched to the Mission Control task. If the user is only going to view/update the Salesforce task, they should not require a Mission Control license. Therefore, you shouldn’t need to purchase licenses for people who are only going to be assigned project tasks rarely.

    Communications Management

    Mission Control (MC) is not intended to be used for change management and therefore, has little communication functionality. It does have a few unique features, and some of its weaknesses can be resolved with simple configuration updates.

    Strength: Automatic Status Report

    Mission Control can automatically publish a PDF status report and email it to stakeholders each week. There are also multiple configuration fields which allow you to customize which topics should be included in the status report.

    While this is impressive functionality, it is so detailed without any summary information, I doubt it would ever get read. The standard status report is 6 pages long, and contains detailed metrics like the number of completed or overdue tasks. It does not have basic summary data like the overall project health (red, yellow, green) or key accomplishments for the week or key upcoming tasks.

    Strength: Customer Access to Project Data

    Mission Control creates an external website which the client can access to track the project status. There are configuration check boxes which allow the project manager to control which type of project data the customer can view.

    Strength: Identify Stakeholders

    Mission Control does provide the capability to identify individual project stakeholders that are either Salesforce users or Salesforce contacts. This stakeholder list can then be used for planning communication or training.

    However, it only has the ability to identify individual stakeholders. Often, when planning communication or training you want to specify groups rather than individuals. For example: Atlanta call center. You might be able to work around this gap by using Mission Control’s ‘Asset’ stakeholder type or adding a new custom type.

    Weaknesses

    There isn’t any functionality for planning communication or training.

    It boggles my mind, but there aren’t any standard fields to communicate overall project health. For example, red, yellow or green. Or to use stoplights for costs, schedule and scope. This can be corrected fairly easily by adding these fields to the project object.

    Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Mission Control quickly and thoroughly.

    Cost Management

    As you would expect with a PSA tool, Mission Control has very strong cost management functionality. It has the ability to vary tax rates, to track and approve billable expenses, vary the billing types, etc. I only found a few minor functionality gaps, and these can be easily fixed by adding some custom fields.

    Strength: Roll Up of Costs

    Costs are associated to actions and then actions can be rolled up to projects and programs. Client-incurred costs are also summed to generate invoices. There are also checkboxes which control the summations. For example, you can check whether the cost is billable or not.

    Strength: Route Expenses for Approval

    Expenses can be routed to a manager for approval. This is especially important when expenses are being billed to the client.

    Integration Management

    Integration Management is the process of coordinating the overall project and the different project management processes. Mission Control has good functionality in this area. It is unique in that it provides a meeting planning tool and a tool for recording project retrospectives. It has the standard common functionality, such as, issues, risks, time entry, dashboards and task alerts. Mission Control is weak in the area of project-specific security and access.

    Strength: Meeting Planning Tool

    Mission Control has a unique meeting planning tool. It creates and object record for each meeting so the meeting can be planned and recorded. It includes an attendee list and can record actual attendance. It includes an agenda, and tasks can be assigned to the individual agenda items. Also, recurring meetings can be cloned from prior meetings.

    There is one major gap. The meeting tool doesn’t show attendee’s calendars in order to pick a meeting time when all will be available. So, while it is good for recording the meetings, the meetings will have to first be scheduled in a tool like Microsoft Outlook.

    Strength: Project Retrospective

    Mission Control gives project retrospectives a high priority by providing a dedicated object. You can record the weaknesses and strengths identified during the retrospective and even share them across project teams.

    Strength: Task Alerts

    Mission Control provides two task alerts which are very useful. First, a person assigned to a task can receive an alert notifying them that they have been assigned a task. Second, when a preceding dependent task is completed, a notification can be sent to the person assigned to the succeeding task that the task can be started. There are also simply checkboxes that toggle these alerts on or off.

    Weakness: Project-Level Access

    It appears that Mission Control doesn’t provide any project-level access controls. Meaning, anyone with a Mission Control license can view all projects. You can control which data an individual user can view globally across all projects, but you cannot vary the data they can view between projects. At the role level, you can control the data displayed on specific screens, but I don’t think you can control their access to the underlying data. So you could assign a user to a specific role and then assign the role to the project to vary the data displayed on the screens for a specific project.

    This would be a problem if you wanted to have confidential projects within your company. This could be important for a pending merger or a project which would result in staffing reductions. It could also be a problem if users fill different roles on different projects and you want to limit their data access based on their role. For example, a project manager will need access to financial data on their own projects, but you may not want them to have access to the financial data of all projects.

    Mission Control Salesforce App Role Access Options

    Weakness: Project Scope and Business Case

    Mission Control lacks the ability to document details of the project’s scope and business case. It doesn’t have the ability to capture individual scope records, though changes are captured in change requests. It also doesn’t have the ability to capture detailed benefits and project savings to develop a business case.

    Procurement Management

    Mission Control has strong procurement management functionality in that it can forecast cash flows and capture the spend per vendor.

    Quality Management

    Mission Control doesn’t have any real functionality for testing software or processes. The only functionality it provides is documenting acceptance criteria for user stories and requirements. However, the acceptance criteria is a single text field, so you won’t be able to record which criteria passed and which failed when testing.

    Resource Management

    Resource management is Mission Control’s greatest strength, but could also be its greatest weakness if you don’t plan or track every minute of your resource’s time. It is primarily setup to allocate labor hours to every task, sum those hours and rates into a budget and then track and bill those hours throughout the project. This makes sense as this is the main function of a PSA tool.

    However, after thirty years of project management, I’ve come to the conclusion that this level of planning is not necessary and is a unnecessary burden. I simply allocate a percentage of a person’s time to a project by week. I estimate the total hours required by estimating the deliverables, not be assigning hours to specific tasks.

    Also, I worked at a large global consulting firm, and resource allocations were never planned at this level. People were assigned to a client at a percentage level by week. This gave the visibility needed for managing utilization and resource availability.

    Strengths: Detailed Resource Planning

    Mission Control has all the key functionality you would need to perform detailed resource planning. You can assign skills and plan by skill. You can assign holiday schedules to individuals or groups. You can measure utilization.

    Resources and labor hours are assigned to individual tasks. Summary reports can should a person’s total allocated versus available hours by day, week or month. These allocations are updated as tasks are rescheduled.

    Mission Control Salesforce app's highly detailed task (action) record

    Weakness: Project-Level Resource Allocation

    Mission Control has a tool to do an initial labor forecast based on skill. However, the only method I could find for forecasting an individual’s labor allocation is to assign a person to a project role and then assign that role to tasks with individual labor estimates. I could not find any functionality where I could simply assign a person to a project at 50% for a month.

    I suppose you could work around this restriction by creating ‘dummy’ tasks for each resource which represent their project allocation. However, this would then become problematic if you also assign them to specific tasks with labor estimates.

    Risk Management

    Mission Control has good functionality for recording risks. It only has two gaps that I could find. First, it doesn’t have a full-fledged risk matrix which would total all the financial or schedule impacts for a project. However, I find risk matrices to be a limited value. Second, only one task can be assigned to any one risk. Therefore, cannot build a detailed action plan for a risk.

    Schedule Management

    Mission Control has a good scheduling tool and Gantt chart. It should suit the needs for most professional services companies, but it would not suit the detailed scheduling needs for a construction project. The biggest gap is that the task hierarchy and work breakdown structure is limited to only three levels. You cannot simply create as many task groupings as you would like. Next major gap is that it does not calculate a critical path. Lastly, it does not support planning software releases.

    Strength: Basic Gantt Chart Functionality

    The Gantt Chart functionality is very similar to Microsoft Project and is easy to use. You can add new tasks and create dependencies by dragging and dropping. It supports all task dependencies except for Start-Finish (which is rarely applicable). You can quickly modify and re-order tasks within the Gantt view. It supports multiple predecessors for a task and lag for a predecessor.

    The Gantt is rescheduled based upon dependencies when predecessor tasks are updated with either planned or actual dates. The rescheduling functionality worked in all but one case, as I was testing it. In one case the finish date or the preceding task was updated and the dependent task’s start date didn’t not change. So, you should thoroughly test this functionality for yourself.

    Mission Control Salesforce App Gantt Chart

    Strength: Inter-Project Dependencies

    Mission Control supports creating dependencies between tasks on different projects. For example, Task 10 on Project B cannot start until Task 20 on Project A is completed. I’ve found that this is often not supported on other project management software.

    Strength: Assign Multiple People to a Task

    Multiple people can be assigned to a task in Mission Control and it handles the resource allocation. I’ve found this to be a differentiator on project management software.

    Strength: Synchs with Salesforce Tasks

    Mission Control created tasks will also create a cloned Salesforce task. These tasks are also synched so that when one is marked as complete, the other one is also updated. This is incredibly important functionality because it means that a Salesforce user can view all their assigned tasks in one place. They don’t have to view everyday tasks on their Salesforce home page and then have to open the project management app to view their project tasks.

    Weakness: Three Level Work Breakdown Structure

    Mission Control only supports three levels of tasks: milestone, task (called an action), and a checklist. Unlike Microsoft Project, you cannot simply indent a task to make it a child of the preceding task. This would be a serious handicap for me, but may not be a major issue for you. I can easily use five or six levels within my project plans.

    Weakness: Doesn’t Calculate the Critical Path

    Unlike most scheduling tools, Mission Control does not calculate the slack between dependent tasks and highlight the critical path which lacks any slack. As a project manager, I find this functionality extremely useful. First, it isn’t obvious in large complex project plans. Second, it helps prioritize which tasks to focus on so I ensure they don’t slide.

    Weakness: No Releases

    Mission Control doesn’t have a ‘release’ planning object. I would find this very problematic, especially with the limitation to a three level work breakdown structure. I plan the project build and change management around releases. Not having this capability would make it very difficult to forecast and communicate release dates. You could define a milestone as a release, but then you could not group the tasks any further by deliverable.

    Scope Management

    Mission Control has two strong pieces of scope management: it documents requirements and it issues change requests. The only gap is that it doesn’t have strong functionality for listing individual in-scope and out-of-scope items at the beginning of the project.

    Stakeholder Management

    Mission Control supports identifying stakeholders, but it doesn’t integrate this into a full stakeholder management solution to support communication and training (i.e. change management). You cannot identify the change impacts from an upcoming release and map that to the stakeholders that will be impacted, and the resulting level of support, communication and training that is required.

    The other significant gap, is that is geared to identifying individuals as stakeholders, not groups. I believe you could work around this by using the ‘Asset’ classification of a stakeholder, but that wasn’t its intended purpose. While key executives need to identified as individuals, most communication and training is planned at the group level.

    Download Mission Control Evaluation Spreadsheet

    Click here to download the Mission Control Excel spreadsheet.

    Mission Control Scoring Methodology

    I’ve been evaluating all of the Salesforce project management software and sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. When I come across novel functionality in the software I’m evaluating I add it to the requirements list. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totaled the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you. You can confirm my scoring using the Mission Control test drive or by installing the free trial into a sandbox.

    Here are some links to help you research the app:

    In Conclusion

    If you are looking for a professional services automation (PSA) tool where you can easily manage your team and bill your clients, then you should seriously consider Mission Control software. However, if you are looking for a more generic project management solution, I think you will find the detailed planning required by Mission Control to be stifling.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Review of Salesforce Gantt-Chart Lightning Web Component

    Shogun Evaluating Salesforce Gantt-Chart Lightning Web Component App

    Salesforce Gantt-Chart LWC is broken. Move along, nothing to see here. Based on the reviews it hasn’t worked since 2019, even though the listing says it was updated in January 2023. I loaded it into a sandbox to see if I could at least learn how to build my own Gantt chart object but I wasn’t able to view any of the lightning web component details to learn how it was built.

    Summary of Findings

    Broken. The Salesforce Gantt-Chart Lightning Web Component was published by Salesforce Labs. This means it was developed for internal use within Salesforce, and they shared it publicly for free use on the AppExchange. However, as evidenced that the Gantt-Chart Lightning Web Component has been broken for four years, these apps are not maintained or supported. Therefore, if you install one of these apps you may run into issues in the future if it is broken by a future release. Since the apps are managed, you most likely won’t be able to fix the issues if it does become broken in the future.

    The app is very simple. It has three objects: project, resource and allocation. It is supposed to show a listing of the people assigned to a project with their allocation along a timeline. Once I created a project, resource and allocation I received the following error message whenever I navigated within the app.

    I thought that the error could have been caused by an incorrect install. However, I wasn’t even able to download the provided install guide because I wasn’t able to log into the source with my Salesforce account. Given there are several comments dating from 2019 that the app was broken, I came to the conclusion it wasn’t an error with my install.

    Gantt-Chart Lightning Web Component
    Total Score0%
    Communications Management0%
    Cost Management0%
    Integration Management0%
    Procurement Management0%
    Quality Management0%
    Resource Management0%
    Risk Management0%
    Schedule Management0%
    Scope Management0%
    Stakeholder Management0%

    Salesforce Gantt-Chart Lightning Web Component Pricing

    Free. But of course, it is broken so not even worth that price.

    In Conclusion

    It is broken and will probably never be fixed. Enough said.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • IT Project Estimation – A Practical No-Nonsense Guide

    Shogun Performs IT Project Cost Estimation on a Spreadsheet

    This post covers the process of IT project estimation related to developing or implementing software. This is a practical guide based on what has worked for me over the last thirty years. I started my career performing far too precise analysis which missed some of the bigger picture. Now I identify the critical elements while performing less precise analysis.

    My approach performs IT project estimation in several steps. First, a high-level estimate is created with a 20% contingency during the plan stage. Next, a detailed estimate is created with a 10% contingency on the first iteration of the analyze and design stages. Finally, story points are used to estimate the Agile sprints.

    I also typically create both a top-down and bottom-up estimate. The top-down is used in the early planning stages and it shifts to a more detailed bottom-up estimate as more information is learned about the project. A bottom-up estimate may also need to be adjusted based on the practicalities of labor staffing. Meaning, you determine you need 3.2 developers to meet the release dates but you might have to staff full-time resources so you must budget for 4 full-time developers.

    Plan Stage IT Project Estimation

    The goal of this stage is to perform a high level IT project estimation so management can evaluate the financial return and budget for the project (i.e. assess the business case). This should all be desktop analysis done on the back of an envelope. Not looking for precision at this point, but looking for a range. Is it going to cost $10K, $100K, $1M?

    Software Package License Costs

    If a software package will have to be purchased, I perform the IT project estimation during the Plan Stage based on the vendor’s standard license costs. A short list of possible of vendors is developed and I either issue a request for information (RFI) to the vendors or pull standard pricing right off their websites. If the software will require hiring a software consulting partner to help with implementation, then I get typical costs from the software vendor (some offer standard packages) or consulting partner recommendations which can then provide standard pricing quotes.

    Labor Costs

    During the Plan Stage labor costs are developed in collaboration with IT managers and possibly external development firms. An experienced project manager and/or IT manager should be able to review a project description and initial technical design to estimate if a project will be 3 months, 6 months, a year or more in length. Key to the IT project estimation will be the initial technical design which should identify the major technical components required, such as, APIs, new user interfaces, etc. This information will typically be captured in a context diagram, technical component inventory or the work breakdown structure of the initial project plan.

    Generating the initial labor estimate then boils down to multiplying the typical team size by the number of months estimated to complete the project. Hourly wage rates are varied based on whether the resource will be internal or external. So management ends up getting a high level estimate. For example, $1.2M ($1M + 20% contingency) with a total project length of 12 months.

    Analyze/Design Stage IT Project Estimation

    The Analyze and Design Stages produce the detailed business requirements and user stories, as well as, the technical requirements and user stories. In a large Agile project, the Analyze and Design stages may be iterated to develop detailed user stories just-in-time for the sprints. However, the goal should be to finalize the overall project budget and schedule at the end of the first iteration of the Analyze/Design Stage. This is so management can make a fully informed decision as to whether to approve the beginning of development and formation of the full project team.

    But how to generate an accurate complete IT project estimation when all the requirements and users stories have not been completed? The answer is to estimate at the component level. By this point, the team should know how many and what type of technical components must be built. Technical components are items such as, APIs, user interfaces, database tables, reports, etc.

    Task-Level IT Project Estimation is Too Complex

    Early in my career, I’d attempt to create super complex project plans while trying to assign labor hours for every task. This excessive detail gave the illusion of improved accuracy, but it was a fool’s dream. It also made the project plans extremely complex in that every component being built needed four tasks (analyze, design, build and test) with labor estimates.

    The project plan should be simple and streamlined and not attempt to capture every user story as a task. The work breakdown structure should be: project stage, release and major component. The project plan should focus on an overall timeline and only contain the detailed tasks that will be managed outside the Agile Kanban board, such as, change management, marketing, business case development, etc.

    Component-Level IT Project Estimation is ‘Just Right’

    I now perform IT project estimation by either using an Excel spreadsheet tool or an estimation tool like in Project Lifecycle Pro to estimate at the component level. Each standard technical component type is assigned twelve labor standards. A labor standard is assigned for analyze, design, build and test for each of three effort rankings: high, medium, low. For example a report ranked ‘low’ might have a build labor standard of 1 hour. While a report ranked ‘high’ might have a build labor standard of 4 hours. These labor standards are stored as a tab in the estimation spreadsheet and then populated using VLOOKUP for each of the component records.

    The IT project estimation is performed in a meeting with the product owner and IT manager or architects. Each technical component type which must be built is ranked by effort as either: high, medium or low. The standard labor hours are then automatically applied to the analyze, design, build and test tasks. The team reviews the standard labor values and makes manual adjustments as necessary.

    Estimate Non-Critical Components in Bulk

    Definition of the technical components can be iterated. Non-critical components such as reports can be estimated as a total rather than having to identify every specific report needed at the beginning of the project. For example, you could simply guesstimate that about ten reports will have to be built. Then multiply the standard labor estimate per report by ten. However, you will want to specifically identify critical components before you lock down the IT project estimation. For example, are you going to modify an existing user interface to capture additional data, or are you going to have to build an entirely new user interface and workflow?

    Labor Totaled by Role

    Once all the components are ranked by effort, the total labor hours can be totaled for analyze, design, build and test. These tasks also correspond to the roles on the team. Analyze is usually performed by the business analyst or product owner to document functional requirements. Design is performed by the architects or IT leads to document technical requirements. Build is performed by developers, and includes unit testing. Test is the acceptance testing performed by business analysts or QA department. So now, the project manager has a total estimate of labor for business analysts, architects, developers and QA.

    IT Project Estimation by Release

    Finally, the list of technical components to be built are assigned to releases. And thus, the labor estimate can now also be summed by release. The project manager and product owner can now begin release planning. Given the planned staffing of the team and the hours estimated for the release a release date can be forecast. Of course, the team staffing or the release scope can also be refined to hit target release dates.

    For example, ten technical components have been prioritized for Release 1. The total estimated build labor is 500 hours. The team is assigned three developers. At 80% utilization, each developer can work 32 hours per week (the remaining eight hours is for vacation, holidays, meetings, or any other non-working time). 500 hours divided by 96 hours per week (32 x 3) results in 5.2 weeks, rounded up to 6 weeks. Now the project manager has a release estimate of 6 weeks or 3 sprints, and can give management a realistic possible release date. The project manager can also begin coordinating marketing and change management efforts around the target release date.

    Analyze/Design Stage Gate

    At the end of the first iteration of analysis and design, a stage gate should be held for management to approve the beginning of the build stage. Up to this point, project costs should have been fairly low but once build begins costs will increase significantly. If a software package is being purchased, then licenses will have to be purchased to support the install and configuration. If software is being developed, then the internal or external developers will have to be staffed along with QA resources.

    For management to make the decision to proceed at a much higher spend rate, they need the following information. They will need a timeline for the releases: when are they going to get something for their money?. They need a staffing plan: how many people will have to be dedicated to the project and for how long? They will need a total cost estimate within a plus/minus ten percent: how much is it going to cost? Finally, they need a business case comparing the costs to benefits: will they get a fair return on their investment?

    Build Stage IT Project Estimation

    Agile software development is all about building functionality in the correct priority and working as efficiently as possible. Agile is about getting the functionality built, not wasting time planning and budgeting. So now I need to marry the overall IT project estimation done above with running the day-to-day sprints. And I need to do this while minimizing the distraction for the developers.

    Group User Stories by Component and Release

    The first step is to assign user stories to components. This can be done by making each component an epic or creating custom labels per component. As user stories are created the author should be assigning the component value. Now, user stories can easily be sorted by component and prioritized accordingly.

    JIRA has standard functionality to define a release by assigning user stories. Continuing the example from above, we have ten components planned for the first release. Let’s assume we have an average of three user stories per component. We have the user stories assigned to the components so we can prioritize the thirty user stories towards the top of the backlog. Finally, we assign the thirty user stories to the first release in JIRA.

    Sprint Planning and Story Points

    Please note this is the first time in this estimation process that the developers will be pulled away from coding to plan. The first thing I do when planning a sprint is meet with the product owner to ensure that the product backlog is correctly prioritized for at least the next sprint. I hold this meeting a couple of days prior to the team sprint planning meeting.

    The entire team is assembled for the sprint planning meeting. The product owner starts the meeting by explaining their rationale for prioritizing the user stories and what they feel is the minimal viable product for the next release. The product owner also shares the estimated release date but emphasizes that we will operate under Agile principles and that the release date will not be finalized until we are into the final sprint.

    The team walks through each user story in order. Story points are assigned to each story, but the majority of the conversation should focus on ensuring the developers understand each user story and soliciting their input on the best approach. For example, the user story could have made a false assumption on the best technical approach. Or, developers may suggest changing the priority of some stories because they are related and will be more efficient to code together. Of course, the developers are ultimately determining what amount of work is feasible for the sprint.

    Monitoring and Adjusting the IT Project Estimation

    The sprint planning meeting is the first opportunity to adjust the labor estimates. If we continue the example, thirty stories were planned in three sprints for the first release. If only five stories make it into the first sprint, then it is likely all the stories are not going to be completed in three sprints. I probably wouldn’t start communicating a new release date at this point, but I’d make sure no commitments were made against the release date. I’d tell marketing not to sign any advertising contracts, or training not to schedule any training dates yet. Of course, I could also request additional developers if the release date has to be met.

    During the sprint, the burndown chart will be the ongoing guide to forecast the possible release date. It will be fairly obvious whether the original release date is realistic based on the burndown chart progress. JIRA also shows the status of the stories assigned to the release. If 66% of the release stories are completed by the end of the second sprint, then the release date is probably sound.

    Adjusting and Maintaining Labor Standards

    As part of the sprint retrospective, the project manager should review if the labor standards used for the component-level estimate where accurate. If the labor standards were significantly off, then this is a good time to share the initial estimate for a component with the developers and discuss why the estimate was wrong. Perhaps it was an issue that could not have been foreseen, like the new functionality unearthed a bug in existing code. Or perhaps, the wrong people were ranking the complexity of the component.

    In Conclusion

    I hope that I’ve made the case that component-level IT project estimation achieves the right balance of providing management high-level guidance while avoiding unneeded detail. Remember that your estimates are going to revert to the mean, so the positive and negative variances should average out to a reasonable estimate. Management only cares about the total cost so they can budget and plan resources. They mostly care about cost overruns which are addressed by adding 20% contingency during the plan stage and 10% later. You can always give back funds later in the project as things become more certain.

    The project team should be focused on building the solution as efficiently as possible not on worrying about meeting estimates or detailed reporting of their time. You shouldn’t care if one report took 30 minutes to build and another took 1.5 hours as long as they average out to your standards. So there isn’t any need for developers to track their time to this level. You really don’t even care if component estimates are accurate as a whole, you care if your overall budget estimate or release dates are going to vary enough that management must be informed. Meaning, you are going to need more money or other groups dependent upon the release date must change their plans.

    IT Project Estimation Related Info

    If you are looking for a project management tool for IT project estimation and currently have Salesforce, please consider my Salesforce project management app: Project Lifecycle Pro (PLP). It is a comprehensive project management office (PMO) and project portfolio management (PPM) tool. PLP supports the IT project estimation process I describe above. You maintain a labor standards table within PLP which is customized for your component types and populated with your labor standards. Components are inventoried within PLP and tied to releases and requirements. The components are also ranked by complexity which automatically applies your labor standards and sums the totals to the release. One really nice feature is that the labor standards can be applied or overridden manually for individual components at the click of a button.

    If you are interested in learning more about Project Lifecycle Pro or the benefits of using your existing Salesforce licenses for project management, please follow these links:

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Personal Review of Salesforce PMT

    Salesforce Project Management Tool

    Salesforce PMT is only a good option for those with Salesforce Service Cloud, because Service Cloud is required for PMT to function. If you currently have Service Cloud licenses and you are looking for a very basic project management tool, then PMT may be a good option for you. If you are looking for a fully functioning project management tool you should skip PMT.

    This post reviews Salesforce PMT against 200+ project management software requirements on an RFP-level fit/gap analysis spreadsheet which is available for download. Salesforce PMT is scored against all ten of the project management processes. This post provides a summary of the key strengths and weaknesses for each of the processes.

    All My Project Management Tool Reviews

    I have personally reviewed many of project management tools, including dozens of the Salesforce project management apps. I’m continually adding more reviews.

    Summary of Findings

    If you don’t currently have Salesforce Service Cloud: STOP. The PMT functionality is not worth having to purchase Service Cloud licenses.

    If you are looking for Salesforce’s equivalent to a scheduling tool like Microsoft Project or Primavera, PMT is not for you. PMT recently added a Gantt chart, but it is still buggy and lacks lots of basic scheduling functionality.

    If you are a professional service’s firm (software development, consulting, accounting, engineering, etc.) wanting to manage your client projects, PMT is also not for you. You should search the Salesforce AppExchange for PSA tools to find the several apps dedicated to this industry.

    Overall, PMT has limited functionality. There are even three processes where PMT doesn’t have any functionality. The table below shows the coverage of each process as a percentage basis compared to full coverage.

    Salesforce PMT Pricing

    PMT is free, however, it requires Service Cloud. If you need to purchase Service Cloud for PMT in addition to another Salesforce license, the minimum additional cost will be $300/yr/user. If your users are already on Service Cloud, then PMT is truly free.

    Download PMT Evaluation Spreadsheet

    If you are considering purchasing PMT, then download this spreadsheet to understand the detailed functionality. This is an RFP-level fit/gap analysis with 200+ requirements.

    Communications Management

    The only Communications Management functionality Project Management Tool (PMT) has is the ability to communicate project status.

    Cost Management

    Project Management Tool (PMT) does not have any functionality for recording or tracking project costs.

    Integration Management

    Integration Management is the process of coordinating the overall project and the different project management processes. Project Management Tool (PMT) has fairly good functionality in this area. Basic project information is captured, along with scope and risks. Project issues can also be documented. Access to the projects is controlled by only granting access to the users assigned to the project. Projects can also be grouped into programs.

    PMT’s gaps in integration management are primarily related to not supporting Agile project information like epics and themes. PMT also cannot record schedule baselines. PMT doesn’t support creating and routing change orders.

    Procurement Management

    PMT does not have any significant procurement functionality.

    Quality Management

    PMT does not have functionality for testing or quality control. It receives some points in the scoring because an acceptance criteria field could be added to the tasks.

    Resource Management

    PMT has the ability to allocate resources to the project and can report these allocations using different time periods (weeks, months, quarters).

    Risk Management

    PMT only has a single text field to record risks associated to the project. This prevents recording mitigation plans or assigning specific tasks to an individual risk.

    Schedule Management

    PMT captures isolated tasks and can display them on a Gantt chart. This is about the extent of its scheduling capabilities. As of October 2023 the Gantt chart is pretty buggy. Tasks aren’t being displayed on the correct day in the Gantt. I was having difficulty changing tasks, duration, start or finish dates within the Gantt. PMT’s Gantt is also missing basic scheduling capabilities:

    • Doesn’t support dependencies between tasks.
    • Tasks cannot be scheduled using durations.
    • Tasks don’t capture labor.
    • Tasks can’t be arranged in chronological order.

    PMT has a major flaw in that it uses a custom task object. That means that PMT tasks are stored separately from the standard Salesforce tasks. This means for a user to see all of their assigned tasks they must look in two different places: the Salesforce home page and the PMT dashboard.

    Scope Management

    PMT only has a single text field to note scope of the project. It doesn’t have any capability to capture project requirements.

    Stakeholder Management

    The only stakeholder management functionality PMT has is to record some key stakeholders such as ‘Owner’s Department’ and ‘Project Initiator’. It doesn’t have any functionality to support change management by identifying changes and the people who will be impacted.

    Scoring Methodology

    I’ve been evaluating all of the Salesforce project management software and sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my 30 years of project management experience and experience evaluating project management tools for clients. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four point.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totaled the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you.

    In Conclusion

    If you currently have Service Cloud licenses and you are looking for a very basic project management tool, then PMT may be a good option for you. If you don’t have Service Cloud or are looking for a fully functioning project management tool you should skip PMT.

    Regards,

    Brian

    Additional References

  • Detailed Review of Project Lifecycle Pro Salesforce App

    Project Lifecycle Pro is subject of insanely precise free review by Japanese scholar.

    Project Lifecycle Pro is reviewed against 200+ project management software requirements on a downloadable spreadsheet. Project Lifecycle Pro is scored overall and for each of the ten project management processes. This post provides a summary of the key strengths and weaknesses for each of the processes.

    Summary of Findings

    Overall, Project Lifecycle Pro (PLP) is intended to be the foundation of a comprehensive project management solution and to integrate with other best-of-breed solutions.

    If you are looking for Salesforce’s equivalent to a scheduling tool like Microsoft Project or Primavera, Project Lifecycle Pro (PLP) is not the right solution. PLP is intended to support all the project management processes except scheduling and is intended to integrate with a best-of-breed scheduling tool for a comprehensive project management solution. If you think all you need for a project management solution is a scheduling tool, then you should keep reading to understand the full project management process and what is needed to support it.

    If you are a professional service organization (software development, consulting, accounting, engineering, etc.) wanting to manage your client projects, Project Lifecycle Pro is not for you. You should search the Salesforce AppExchange for PSA tools to find the several apps dedicated to this industry (Mission Control, Cloud Coach, etc.).

    When compared to the project management process as defined in the PMBOK PLP has a coverage of 52% with some coverage in all the processes. This is pretty good considering its intended scope and when compared with other Salesforce project management apps. The table below shows the coverage of each process as a percentage basis compared to full coverage.

    Project Lifecycle Pro
    Total Score39%
    Communications Management27%
    Cost Management31%
    Integration Management56%
    Procurement Management13%
    Quality Management17%
    Resource Management31%
    Risk Management83%
    Schedule Management25%
    Scope Management94%
    Stakeholder Management71%

    Download Project Lifecycle Pro Evaluation Spreadsheet

    Click here to add the Project Lifecycle Pro Excel spreadsheet to your basket and continue reading. Visit the basket page to complete the download.

    Project Lifecycle Pro Pricing

    Project Lifecycle Pro has three tiers of pricing. First, it offers a small business site license at $3,000/year for companies with less than 50 employees. Second, it offers a site license at $10,000/year for businesses with more than 50 employees. Lastly, it offers custom pricing for non-profit businesses. Full functionality is provided in all three of the pricing levels.

    Scoring Methodology

    I’ve been evaluating all of the Salesforce project management software and sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. When I come across novel functionality in the software I’m evaluating I add it to the requirements list. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totaled the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you. You can confirm my scoring using the Project Lifecycle Pro test drive or by installing the free trial into a sandbox.

    Here are some links to help you research the app:

    Here is the spreadsheet used to score the app:

    Download Project Lifecycle Pro Evaluation Spreadsheet

    Click here to download the Project Lifecycle Pro Excel spreadsheet.

    Communications Management

    Project Lifecycle Pro (PLP) has dedicated functionality to identify stakeholders and project change impacts, as well as, plan the required communications. The project changes are organized by stakeholder and release to easily facilitate identifying the required communication and training. While change management is a major focus for PLP it does not yet have all the functionality of a learning management system (LMS) to catalog and track communications and training.

    Cost Management

    Project Lifecycle Pro (PLP) supports the creation of separate cost line items and then totals these costs by release, project or program. A baseline and current cost estimate are recorded so budget variances can be tracked. The costs are also categorized so you can differentiate expenses and capital expenditures. The automated flows which rollup the costs, can be cloned and modified to support any custom cost fields you may want to add. Duplicate functionality is also provided to record and rollup project benefits.

    Integration Management

    Integration Management is the process of coordinating the overall project and the different project management processes. This an area of strength for Project Lifecycle Pro (PLP). PLP supports different project record types so that you can customize the project phases, picklist values and various page layouts based on the type of project. PLP also supports the complete data captured in a project charter: scope, stakeholders, milestones, etc.

    PLP has three nice advanced features related to integration management. First, projects are dynamically routed for approval at the end of a stage based upon the specific sponsor and steering committee members assigned to the project. This eliminates the need to build a custom project approval routing for each project.

    Second, project dashboards are automatically filtered to the current user’s assigned projects. This eliminates the need to build custom dashboards for each user and to maintain the list of current projects in the dashboard filters. If you’ve ever built Salesforce dashboards, you know that filtering is handled at the individual report/component-level. This means that if you have ten components on a dashboard, the user will have to create a custom report for each component and maintain the project filter on all ten custom reports. The automated filtering avoids the explosion of custom reports and the maintenance nightmare of maintaining filters.

    Lastly, PLP has advanced security functionality where projects can be marked as public or confidential at the click of a button. All Salesforce users have read-only access to public projects. Only assigned team members can access confidential projects, and the project manager controls whether team members have read-only or write access to the project. Furthermore, access to project financials is controlled separately from the overall project so a team member can have access to the project but cannot view or edit financial data. Having this security architecture built into the foundation of the solution from the beginning is very important. This allows executives to use a single project management solution even for sensitive projects like mergers, acquisitions or improvements with staff reductions.

    PLP’s gaps are in the area of monitoring and controlling the project work. PLP doesn’t yet have a change order feature. It doesn’t yet have automated alerts to notify people of assigned or completed tasks. It also lacks functionality to enter and track actual time against a task.

    Procurement Management

    Procurement is not a current focus for Project Lifecycle Pro and therefore, it has limited functionality. With the detailed cost information, it does support the generation of a cash flow forecast. Also, vendor information can be added to the cost records to track vendor spend against a contract.

    Quality Management

    Project Lifecycle Pro (PLP) does not yet have any real quality control functionality. Providing testing and QA functionality to support software development is a focus of future releases. Testing functionality would consist of documenting acceptance criteria, test scripts and recording testing results.

    Resource Management

    Project Lifecyle Pro (PLP) has the ability to allocate resources to the project. However, PLP only allocates a person to the total project as a percentage of time. If you need to perform detailed resource allocations either by time periods (weeks, months, quarters) or based on hours by assigned tasks you should research PSA tools as this is a major area of focus. I hope to improve the resource allocation functionality of PLP in the future. As mentioned earlier, PLP does have advanced functionality for controlling people’s access to project data.

    Risk Management

    Project Lifecycle Pro (PLP) supports multiple risk records with associated mitigation plans. PLP users can even assign tasks specifically to a risk to track its resolution. PLP will be expanding risk management capabilities in future releases, but since the infrastructure is in in place, you can easily configure it to provide more detailed risk functionality.

    Schedule Management

    Project Lifecycle Pro (PLP) is not intended to be a scheduling tool, but is instead intended to integrate with a best-of-breed scheduling tool to provide a comprehensive project management solution. PLP uses the standard task object, with the intent that a user can view all their assigned tasks on the Salesforce home page regardless if the task is being generated from a project schedule or is created ad hoc directly in PLP. Integration with a scheduling tool involves implementing a flow that will synch tasks between the scheduling tool and the standard Salesforce task object. The popular Salesforce scheduling app Inspire Planner comes with this capability so can integrate easily with PLP.

    One nice feature of PLP is that tasks can be associated with both the project and its related objects. So you can associate a mitigation task with a risk, or a follow-up task to a requirement, etc. Yet, you can also report on all tasks within the project.

    Scope Management

    Project Lifecycle Pro (PLP) has a proper data structure to support project scope. Individual scope records are created and they can be categorized by people, process, technology and whether they are in or out of scope. Individual scope items can also be assigned tasks and Chatter conversations during the planning process. Finally, PLP has a scope metric based on the number of components to be built. This allows tracking the component count changes from the plan baseline as a proxy for scope variance.

    Stakeholder Management

    Project Lifecycle Pro (PLP) has been built to support change management. Separate stakeholder records are created and they can be associated to the planned changes so that communication and training can be planned. Department managers can also see upcoming changes because their departments have been identified as stakeholders, the stakeholders have been associated to changes, and the changes have been associated to release dates. This requires a complex many-to-many relationship which has been built into PLP’s data infrastructure.

    Definition of stakeholders can be limited to specific individuals through a dedicated permission set. This allows you to setup stakeholder gate keepers to ensure that stakeholders are being consistently defined and not duplicated. Maintaining a proper list of stakeholders is key to accurate reporting to support change management.

    In Conclusion

    If you are looking for a project management office (PMO) or project portfolio management (PPM) tool you should research Project Lifecycle Pro (PLP). It is ideal if you already have Salesforce licenses for most of your organization and recognize the value in a highly-configurable cloud-based solution. PLP will form the foundation of a custom project management solution for your company.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Cloud Coach Salesforce App Reviewed By a Project Manager

    Cloud Coach Salesforce App

    Cloud Coach Salesforce App

    The Cloud Coach Salesforce app is primarily a professional services application (PSA) with a robust project portfolio management (PPM) tool on top of it. I was most impressed by its nicely designed user interface.

    The Cloud Coach Salesforce app is reviewed against 200+ project management software requirements on a downloadable spreadsheet. Cloud Coach is scored overall and for each of the ten project management processes. This post provides a summary of the key strengths and weaknesses for each of the processes.

    Summary of Findings

    The Cloud Coach Salesforce app is primarily a professional services application (PSA) with a robust project portfolio management (PPM) tool on top of it. The first thing that jumped out at me while reviewing Cloud Coach is that the user interface is very well done. The screens are very well designed and implemented. Overall, Cloud Coach provides a good PSA solution for firms with fairly simple project plans. The PPM functionality would also be good for a company wanting to organize and track their internal capital investment and business improvement projects.

    While I believe Cloud Coach would provide a complete solution to a professional services firm with simple work plans, like a digital marketing or accounting firm, I believe it has gaps that would have to be supplemented for more technical work like construction or software development. I also don’t believe it provides a full solution for a company managing their internal capital investment and business improvement projects. That being said, Cloud Coach is a native Salesforce app, so it would be very easy to fill some of the gaps with new custom objects or by integrating with other Salesforce apps.

    When compared to the project management process as defined in the PMBOK it has a coverage of 63% which is pretty good considering its intended scope. It has coverage in all the processes, but this is primarily because it could be configured to to support the processes outside of its main functionality. The table below shows the coverage of each process as a percentage basis compared to full coverage.

    Cloud Coach
    Total Score51%
    Communications Management9%
    Cost Management68%
    Integration Management61%
    Procurement Management13%
    Quality Management17%
    Resource Management55%
    Risk Management83%
    Schedule Management56%
    Scope Management0%
    Stakeholder Management29%

    Overwhelmed trying to find the best PSA tool? Give me your functionality priorities and I will give you a shortlist of 3-5 PSA tools that best suit your needs. You can then focus your detailed assessments on only a few tools. Saves you weeks of research and demos.

    Cloud Coach Salesforce App Pricing

    The Cloud Coach Salesforce app has three tiers of pricing. First, it offers a free version called ‘Starter’. Second, it offers a second tier called ‘Enterprise’ for $59/user/month with a minimum purchase of 25 users, resulting a minimum annual spend of $17,700. The top tier is called ‘Ultimate’ and uses a site license of $2,500/company/month for a total annual spend of $30,000. Therefore, companies with more than 42 users would purchase the Ultimate package.

    For a comparison of the functionality provided in the three tiers, here is a link to a page on the Cloud Coach website: Cloud Coach Pricing. The Enterprise package provides the full PSA functionality. The Ultimate package adds the full PPM functionality.

    Communications Management

    Cloud Coach received points for their functionality to communicate the project status. Change management is not an area of focus, and thus they scored poorly related to change management communications and training.

    Their project status functionality is quite good. They have nice dashboards and stoplights for schedule and budget. They also incorporate Salesforce Chatter into the solution.

    Cost Management

    The Cloud Coach Salesforce app has a nice cost management solution with an excellent user interface. The only major gap I identified was an inability to sum costs by release. This is because Cloud Coach does not provide an ability to plan or manage releases within a project.

    One minor gap is the ability to differentiate budget costs and non-budget cost items. I found in the past that projects may be evaluated based on total costs including internal labor, but costs like internal labor are considered fixed and do not hit the project’s budget. Therefore, the project manager needs to be able to make these distinctions.

    Integration Management

    The Cloud Coach Salesforce app scored a whopping 79% on coverage for the integration management process. I only found three major gaps in their functionality. First of all, Cloud Coach doesn’t have the ability to capture detailed scope items. I find this a very important factor in communicating understanding of the project. This could be fairly easily rectified by creating a custom scope object tied to the project.

    Secondly, the Cloud Coach Salesforce app doesn’t have the ability to capture details about the systems being impacted by the project. This also extends to details required to make system changes like requirements. I find almost every project has a system component, and it is important to inventory all the new and existing systems impacted by the project.

    Finally, the Cloud Coach Salesforce app apparently lacks the ability to restrict access to confidential projects. All Cloud Coach users can view all projects. This could become a problem for an executive wanting to use Cloud Coach as their insight to all the company’s projects, but wouldn’t want the entire company to be aware of certain projects. Confidential projects could include potential mergers and acquisitions, or process improvement projects with significant staffing reductions.

    Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Cloud Coach quickly and thoroughly.

    Procurement Management

    Procurement is not a focus for the Cloud Coach Salesforce app and therefore, they have limited functionality. However, with their extensive cost management capabilities it should be fairly easy to tack on some procurement functionality.

    Quality Management

    Cloud Coach does not have any testing functionality. This would be a major gap for software development projects. This gap could be filled with a dedicated QA tool.

    Resource Management

    Cloud Coach has the resource management functionality needed for a PSA tool and it is easy to use. Time can be planned and tracked down to the task level. Customers can be billed based on time worked. The time entry system seems easy to use and has a nice feature where it will flag situations where a person worked an activity but didn’t record any time. Time cards can also be routed to managers for approval.

    I only noticed two major gaps related to resource management. First, it is rare that a systems project (especially an Agile project) plans resources down to hours per task. The planning is usually much higher-level like a percent of a person’s time allocated to a project for a specific period of time. I did not see any functionality to support this approach.

    The second major gap concerned project access. Like any Salesforce app an admin can universally control a user’s access to specific data fields. Meaning, you could give all users with a developer role read only access to cost data, but it would be the same across all projects. What I didn’t see in Cloud Coach was the flexibility to set access rights for an individual that varied between projects. So Joe only has read only access to one project because he’s a stakeholder, but Joe has edit access to a project he is working on.

    Risk Management

    Cloud Coach has robust risk management functionality. Risks can be logged as tickets associated to tasks and then can be reported at the project level. There is a nice risk matrix graphic that summarizes risks based upon probability and impact.

    The only gaps I saw could easily be addressed by adding some additional fields to the risk object. First, I didn’t see a way to associate a quantitative range to a risk. For example, an impact of $10K – $20K. Ideally, these values would be captured and summed to determine the amount of contingency required for the project. Second, strangely there weren’t any fields to record the risk mitigation or avoidance strategy or tasks.

    Schedule Management

    Cloud Coach has some good scheduling capabilities which should suffice as a PSA tool. It doesn’t have the full functionality a professional scheduler would need for a large technical program or a construction project. A couple of key features it has that many cloud-based scheduling tools don’t have are:

    • Task details displayed on the Gantt Chart page. There is a frame on the right which displays the task details for the task that is highlighted.
    • It will calculate a critical path.
    • It will re-schedule based on task dependencies. Meaning, it will push the start of downstream tasks out if you extend a preceding task.
    • It has a Kanban board and functionality I haven’t seen before where you can combine the Gantt chart phases with a Kanban board.
    • It can support at least four levels of tasks: phase, tasks at phase level, sub-phase, tasks at sub-phase level. I couldn’t confirm how many total levels of sub-phases it will support.

    The significant gaps are related to advanced features of a full-fledged scheduling tool and support for Agile projects. Most of the Agile gaps could be filled by installing the free Salesforce Agile Accelerator app.

    • It appears to only support Finish/Start dependencies. It does not support other types such as Finish/Finish, Start/Start and Start/Finish.
    • It doesn’t support lag on dependencies.
    • It doesn’t support Agile sprints or epics.
    • Cannot rank Agile cards/tickets in a product backlog.
    • Cannot create parent/child Agile cards/tasks.
    • Does not have an Agile burndown report.

    There were several gaps I could not confirm, so if these are important to you, you should investigate these more:

    • The number of sub-phase/task levels it will support.
    • Not sure if it will reschedule downstream dependent tasks based on a delayed actual completion date.
    • Not sure if you can assign multiple people to a single task or a team.
    • I didn’t see any examples where multiple preceding tasks were assigned to a single task. Therefore, I suspect it only supports one Finish/Start relationship.
    • There is a tab labeled ‘Project Dependencies’, I didn’t see it demonstrated but it may allow you to create inter-project dependencies which would be a nice feature.

    Scope Management

    The are only two scope-related features. One is the ability to group tasks under phases and sub-phases to create a work breakdown structure. The second, is to create and approve change orders. There is no other functionality to plan or track scope changes.

    Stakeholder Management

    Cloud Coach has a some neat stakeholder management features but it falls short of a full change management tool. It has the ability to identify individual Salesforce users and contacts as stakeholders and to plan their required level of engagement. It can even organize the stakeholders in a tree view. It also has a nifty RACI chart tool to assign responsibilities to the stakeholders. I’ve never used a RACI chart to define stakeholders before, but I assume it could be helpful in some cases.

    The biggest gaps I see in the Cloud Coach stakeholder management functionality are related to the overall change management process. There isn’t any functionality to identify change management impacts and to plan their timing based upon release or deployment dates. Therefore, communication and training plans cannot be created based upon the Cloud Coach data. Lastly, the system uses the Salesforce user and contact objects to identify individual stakeholders. In most cases, stakeholder planning is done at the group level and Cloud Coach doesn’t allow the definition of a stakeholder group. For example, an update to the SAP accounts receivable module will impact everyone in the accounts receivable department. For planning purposes I want to list the stakeholder as ‘Accounts Receivables’, I don’t want to have to list everyone in the AR department.

    Cloud Coach Salesforce App Scoring Methodology

    I’ve been evaluating all of the Salesforce project management software and sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. When I come across novel functionality in the software I add it to the requirements list. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totaled the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you.

    WARNING: Unfortunately, I wasn’t able to successfully load Cloud Coach into a sandbox environment to play with it myself. However, to assess the software I watched numerous demos and searched through their extensive knowledge base. I’ve noted in the spreadsheet when I was unsure of whether Cloud Coach supported the requirement.

    Cloud Coach Salesforce App In Conclusion

    The Cloud Coach Salesforce app has some very nice features and a great user interface. It definitely should be considered by professional service companies and any company looking for a project portfolio management tool. However, those attempting to build a comprehensive project management solution need to be aware Cloud Coach would only form part of their solution. Luckily, it is built on the Salesforce platform which would allow it to be easily integrated with other apps.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Milestone PM+ Reviewed by a Project Manager

    Milestone PM+ Salesforce App

    Milestone PM+

    Milestone PM+ is a Salesforce-based simple scheduling tool with some resource allocation and time entry functionality. A very limited free version is offered. There are better scheduling and PSA tools available on Salesforce AppExchange.

    Milestone PM+ is reviewed against 200+ project management software requirements on a downloadable spreadsheet. Milestone PM+ is scored overall and for each of the ten project management processes. This post provides a summary of the key strengths and weaknesses for each of the processes.

    Milestone PM+ Summary of Findings

    Milestone PM+ is primarily a project scheduling tool (i.e. Microsoft Project, Primavera) with some resource allocation and time entry functionality. Overall, this app falls far short of supporting all project management processes. Compared with a true scheduling tool like MS Project or Primavera it is missing some pretty basic functionality. There are also better Salesforce-native scheduling tools available. If you are a professional services firm interested in resource allocations and time entry, again, there are better Salesforce-native PSA tools available.

    When compared to the project management process as defined in the PMBOK it only has a coverage of 33%. It has coverage in all the processes, but this is primarily because it could be configured to to support the processes outside of its main functionality. The table below shows the coverage of each process as a percentage basis compared to full coverage.

    Miilestone PM+ Summary Scores

    Overwhelmed trying to find the best PSA tool? Give me your functionality priorities and I will give you a shortlist of 3-5 PSA tools that best suit your needs. You can then focus your detailed assessments on only a few tools. Saves you weeks of research and demos.

    Milestone PM+ Pricing

    Milestone PM+ has two tiers of pricing. First, it offers a very limited free version. Second, it offers a Premium version for $216/user/year up to 9 users. After 9 users, pricing for medium businesses with less than 250 employees is $2,064/org/year. They don’t publish their pricing for large businesses.

    Scoring Methodology

    I’ve been evaluating all of the Salesforce project management software and sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totaled the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you.

    Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Milestone PM+ quickly and thoroughly.

    Communications Management

    Milestone PM+ received some points because project status fields could be easily added to the project object to communicate status.

    Cost Management

    Milestone PM+ has basic functionality to capture costs. It captures budgets, as well as, actual costs.

    Integration Management

    Integration Management is the process of coordinating the overall project and the different project management processes. Milestone PM+ has some nice features in this area but is lacking a full solution. Projects can be grouped by both Programs and Portfolios. There are automated alerts when a task is assigned and a task is ready to be worked because the predecessor has been completed. Actual time can be recorded against any of the project objects: tasks, milestones, projects. It has robust functionality for documenting risks. And finally, it supports capturing issues.

    However, it also has some fairly large functionality gaps in this area. While projects can be grouped by program or portfolio, project metrics such as, costs and task completion do not rollup to the higher levels. There doesn’t appear to be any functionality to control project access for internal users, meaning, everyone can view all project information including, financial data. There is no way to document the detailed scope definition of the project. Projects cannot be routed for approval at the end of stage gates. And finally, while issues can be captured they are captured as separate custom objects and therefore, won’t be listed in a user’s home page tasks.

    Procurement Management

    Milestone PM+ doesn’t really have any procurement functionality. It could be configured to generate a cash flow forecast by adding a scheduled payment date and reporting against planned expenses.

    Quality Management

    Milestone PM+ doesn’t really have any testing functionality. It could be easily configured to add an acceptance criteria field to the task, which would serve as a guide for testing.

    Resource Management

    Milestone PM does have some nice resource management features. Resources are assigned to tasks. Hours and durations assigned to the task are used to calculate the person’s allocation. Allocations across all projects/tasks can be summed to show a person’s total allocation by time period.

    While the solution is good if you want to perform detailed labor allocations at the task level, there isn’t a way to perform high-level percentage allocations at the project level. In the Agile software projects I typically manage, it is rare to attempt to plan resources at the task level. As mentioned earlier, there is no way to limit user’s access to projects or to give them read-only access.

    Risk Management

    Milestone PM has robust risk management functionality. Risks can be logged as independent records and associated to tasks, milestones, projects and programs. Risks can be ranked. Mitigation and contingency plans can be documented.

    Schedule Management

    Milestone PM’s main function is project scheduling. It will serve your purpose if you have very simple project plans that are basically to-do lists. A nice feature for professional services orgs is that projects can be launched from Salesforce accounts or opportunities.

    Management PM+ schedules projects by first defining the project milestones and then tasks within the milestones. To-do lists can also be assigned to tasks. It will also roll up percentage complete to the milestone and project level. Project schedules can be viewed and modified in a Gantt chart.

    However overall, Management PM would be very frustrating to use for a professional project scheduler used to tools like MS Project or Primavera. The ability to modify the project schedule in the Gantt chart is very limited. It doesn’t have basic scheduling functionality like different types of predecessors (i.e. Finish/Finish, Start/Start, Start/Finish), re-calculating the schedule based on actual completion dates, freezing milestone dates, or calculating a critical path.

    The most frustrating feature for a project scheduler would be that it only supports two levels of tasks. You can only group tasks under a milestone and you cannot create parent/child relationships between milestones or tasks. This inability to create multiple levels of groupings could be worked around but would be frustrating.

    Scope Management

    The only scope functionality Milestone PM+ has, is the ability to create a work breakdown structure using the milestones. However, there is no functionality to state what is out of scope which can be one of the most important aspects of scope management.

    Stakeholder Management

    Milestone PM+ is not intended to be a change management tool, so there isn’t any functionality to identify organizational impacts and to identify impacted stakeholders.

    In Conclusion

    Milestone PM+ has some nice features and may be a good option for a PSA org with very simple projects. The base structure is in place, so it could be easily improved using Salesforce’s easy configuration features. However overall, I believe there are better Salesforce apps in its targeted functionality: schedule management and resource management. If you are a PSA org, look at some of the dedicated PSA apps on AppExchange. If you are looking for simply a project scheduling tool (i.e. Gantt chart) then consider Inspire Planner on Salesforce AppExchange or building an integration with MS Project or some of the new cloud-based scheduling tools.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Salesforce Agile Accelerator Review by a Project Manager

    Salesforce Agile Accelerator Review

    Salesforce Agile Accelerator is a native Salesforce solution equivalent to Jira, designed to support Agile backlog management and software development. Being a native Salesforce solution provides several advantages:

    • it can be integrated with other Salesforce data
    • it is highly configurable to suit your specific project processes
    • it can be easily automated using Salesforce Flow

    This Salesforce Agile Accelerator review consists of scoring Agile Accelerator against 200+ project management software requirements on an RFP-level fit/gap analysis spreadsheet which is available for download. Salesforce Agile Accelerator is scored against the ten project management processes. This post provides a summary of the key strengths and weaknesses for each of the processes.

    Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Salesforce Agile Accelerator quickly and thoroughly.

    Salesforce Agile Accelerator Summary Findings

    Salesforce Agile Accelerator is dedicated to helping Agile scrum teams manage their user stories and bugs. It is the core app of the Agile methodology in Salesforce as they use it for their Agile backlog management and delivery. Salesforce offers this app for free on the AppExchange.

    It provides similar functionality as Jira by Atlassian. For a full project management solution you would need to also implement a project scheduling tool (i.e. Microsoft Project or Inspire Planner) and a broad project management tool (i.e. Salesforce PMT or Project Lifecycle Pro).

    Overall, Salesforce Agile Accelerator compares very closely to Jira, which I have used quite a bit and love. However, when compared to the project management process as defined in the PMBOK it only has a coverage of 38% and no coverage in three processes. But this is to be expected because it is a specialty tool, not a broad project management tool. The table below shows the coverage of each process as a percentage basis compared to full coverage.

    Salesforce Agile Accelerator Pricing

    Pricing of Agile Accelerator couldn’t be better, it is free! This a tool Salesforce uses internally for their own Agile teams. Salesforce shares this internal tool for free on the AppExchange. As far as I can tell, Agile Accelerator doesn’t require any specific Salesforce license or service.

    Communications Management

    The only Communications Management functionality Agile Accelerator has is the ability to support Chatter conversations and to report basic project status. There is no project change management functionality.

    Cost Management

    Agile Accelerator does not have any capability to estimate or capture costs.

    Integration Management

    Integration Management is the process of coordinating the overall project and the different project management processes. Agile Accelerator’s main capability in this area is the grouping of of tasks into multiple levels: Teams, Themes, Projects, Programs and Portfolios. A major gap is the ability to define releases. It has a specialized tool to request off-schedule releases of bug fixes, but it doesn’t have the ability to define, plan and schedule normal releases. Salesforce must use a different tool for managing their two releases each year.

    Procurement Management

    Agile Accelerator doesn’t have any functionality to support procurement activities.

    Quality Management

    Agile Accelerator has some functionality focused on the testing of individual user stories and bugs. It has a nice feature where you can associate multiple acceptance criteria records with a user story. This is better than Jira, where you just note the acceptance criteria in a text field. You can also list the automated tests associated with the story.

    The big gap is that you can’t record the execution of tests and whether the acceptance criteria have passed testing. Though, it should be pretty easy to add this feature. It also doesn’t have any ability to create and execute test scripts.

    Resource Management

    Agile Accelerator assigns resources at a scrum team level. A project can contain multiple teams. A Salesforce user is assigned to the team with a standard role and a percentage allocation. There aren’t any standard reports to review resource allocations to determine if anyone is under/over allocated but these should be easy to build.

    The major gap is that there isn’t any security to control access to the particular teams or projects. As a standard user I was able to view all project information and to even change team assignments. This would be a major problem for a company that has sensitive or confidential projects.

    The resource allocation is a flat percentage and not associated with dates. So, a manager can’t review a resource’s allocation by week or month. Finally, there isn’t any labor estimating functionality other than assigning story points to stories.

    Risk Management

    Agile Accelerator doesn’t have any functionality to record or manage risks.

    Schedule Management

    Agile Accelerator’s sweet spot is scheduling Agile stories on a scrum team’s Kanban board. As I said earlier, the functionality in this area seemed to equal the functionality in Jira. Tasks can be grouped by themes and epics. Stories can be dragged and dropped to re-prioritize the product backlog. Stories can also be dragged and dropped within the Kanban board. It would be very easy to run a sprint planning meeting directly within the app.

    Agile Accelerator also has a very nice feature to capture inter-team dependencies. You can create a dependency record associated to the team which lists the story that has the dependency and the story that will deliver the dependency. Both teams have visibility to the shared dependency.

    The major gap is that Agile Accelerator doesn’t have any project-level scheduling tool to generate a Gantt chart with inter-task dependencies. Of course, Agile Accelerator isn’t intended to be a project scheduling tool.

    Scope Management

    Agile Accelerator doesn’t have the ability to capture the project scope you would typically capture in a project charter. The only relevant functionality is its ability to create a work breakdown structure through the breakdown of ‘Work’ (stories) using parent/child tasks.

    Stakeholder Management

    Agile Accelerator really doesn’t have any stakeholder management functionality. You can note the story owner and a few other key roles, but there isn’t any ability to capture the impacts on the organization and which groups will be impacted.

    Scoring Methodology

    I’ve been evaluating all of the Salesforce project management software and sharing the results to help others save time in making an informed decision. I started the evaluation as marketing research for the Salesforce project management app I built: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but I’ve attached the detailed Excel spreadsheet which you can use to perform your own analysis. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my thirty years of project management experience and experience evaluating project management tools for clients. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four points.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object, or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totaled the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you.

    In Conclusion

    Salesforce Agile Accelerator is a native Salesforce solution equivalent to Jira. Being a native Salesforce solution provides several advantages: it can be integrated with other Salesforce data, it is highly configurable to suit your specific project processes, and automation can easily be built using Salesforce Flow. So if you currently have Salesforce licenses and are looking for a customizable solution for your Salesforce backlog management and Agile development, you should evaluate Agile Accelerator.

    If you found this review of Salesforce Agile Accelerator useful, please leave a comment.

    Regards,

    Brian

    Additional References

  • Helpful Project Management Software Selection Spreadsheet

    Sumo wrestler using Edo Period project management software selection spreadsheet.

    A downloadable Excel spreadsheet with 200+ project management software requirements that can be used to perform side-by-side fit/gap analysis of six apps.

    Over the years, I’ve helped clients select project management software, and more recently, I was planning the build of my own Salesforce project management app called Project Lifecycle Pro. I thought I’d share the tool that I used so that it might help you make your own project management software selection. You should treat the list of requirements as a starting point. This is by no means an exhaustive list, but some of the key requirements I’ve dealt with in the past. Of course, you can download the attached scoring spreadsheet to add your own custom requirements and rank them by importance.

    Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate any project management software quickly and thoroughly.

    How to Use the Selection Spreadsheet

    The first tab in the spreadsheet contains instructions. You basically want to get the spreadsheet ready for scoring by updating the values in the Constants tab, cleaning up the requirements and assigning weights. When I start a software evaluation, I use a shorter general list of requirements to score a large number of software options using desktop analysis. The desktop analysis consists of reviewing the software’s website, video demos and potentially free trials I can setup myself. This analysis hopefully results in a shortlist of three software options. At this point, I reach out to the software companies to engage with their sales organization for more information. After developing a full list of requirements, I send the scoring spreadsheet to the various software vendors and ask them to score their own software. Of course, I have to validate their responses but allowing them to respond ‘Yes – As Is’, ‘Yes – With Configuration’ or ‘No – Not Available or Requires Customization’ with supporting notes seems to keep them pretty honest.

    I need to emphasize that I’ve never selected a software based entirely on the score on this spreadsheet. The scoring spreadsheet is really the starting point for a deeper conversation among the selection team. The scoring spreadsheet provides a good structure, and forces the team to consensus on priorities. But, the final selection is also based on pricing, support, security issues, usability and other factors.

    Process Breakdown

    I structured the requirements around the Project Management Institute’s (PMI)© project management process. The processes are outlined in the PM Book of Knowledge (PMBOK)©. I listed the standard project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my 30 years of project management experience and experience evaluating project management software for clients. I’m sure I missed some requirements and welcome any suggestions.

    The processes are:

    • Communications Management – Creating and distributing project communications and training.
    • Cost Management – Managing project costs and the overall budget.
    • Integration Management – To identify, define and co-ordinate project management processes to support the project.
    • Procurement Management – Managing the procurement of materials and services for the project.
    • Quality Management – Ensuring the quality of the project deliverables, primarily through testing.
    • Resource Management – To identify, acquire and manage project resources.
    • Risk Management – To identify, mitigate or avoid risks.
    • Schedule Management – To plan and create a project schedule.
    • Scope Management – To identify the project scope and manage adherence to the scope.
    • Stakeholder Management – To identify people or groups impacted by the project and and manage the associated changes.

    In Conclusion

    I hope you find this a useful starting point for your own project management software evaluation. If you find this scoring spreadsheet useful, please submit a comment. Also, I welcome additional requirements so this scoring spreadsheet can become more comprehensive.

    If you own Salesforce, please consider utilizing my app (Project Lifecycle Pro) and others which can be found on the Salesforce AppExchange.

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Salesforce PMT vs. Project Lifecycle Pro

    Salesforce Project Management Tool (PMT) vs. Project Lifecycle Pro

    This is a comparison of Salesforce PMT vs. Project Lifecycle Pro (PLP) which are both available on the Salesforce AppExchange. PLP is the app I recently built and I wanted to understand how PLP compared and plan future improvements. I thought I’d share my analysis to save others time in evaluating Salesforce project management app options. I’ll summarize my findings below and you’ll find a detailed Excel scoring sheet attached which you can use to perform your own analysis.

    If you are looking for Salesforce’s equivalent to a scheduling tool like Microsoft Project or Primavera, neither of these tools are for you. Salesforce PMT recently added a Gantt chart, but it is still buggy and lacks lots of basic scheduling functionality. PLP is intended to support all the project management processes except scheduling and is intended to integrate with a best-of-breed scheduling tool for a comprehensive project management solution.

    If you are a professional service organization (software development, consulting, accounting, engineering, etc.) wanting to manage your client projects, neither of these tools are for you. You should search the Salesforce AppExchange for PSA tools to find the several apps dedicated to this industry.

    Download PLP vs. Salesforce PMT Evaluation Spreadsheet

    Click here to add the PLP vs. Salesforce PMT Scoring Excel spreadsheet to your basket and continue reading. Visit the basket page to complete the download.

    Summary of Findings

    Overall, Project Lifecycle Pro (PLP) has much more functionality than Salesforce PMT and covers all the project management processes but Quality Management. There are four processes where Salesforce PMT doesn’t have any functionality. The table below shows the coverage of each process as a percentage basis compared to full coverage.

    PMT v PLP Summary Scores

    Pricing Comparison

    Pricing is a major differentiator between PLP and Salesforce PMT. PLP has a max single site-wide license of $10K/year, with discounts for small companies. PMT is free, however, it requires Service Cloud. If you need to purchase Service Cloud for PMT in addition to another Salesforce license, the minimum additional cost will be $300/yr/user. So if you have to purchase Service Cloud, PLP costs less for 33 or more users. If your users are already on Service Cloud, then PMT is truly free.

    Communications Management

    The only Communications Management functionality PMT has is the ability to communicate project status. However, PLP has dedicated functionality to identify stakeholders and project change impacts, as well as, plan the communications required. In other words, PLP has been built to provide change management support.

    Cost Management

    PMT does not have any functionality for recording or tracking project costs. In PLP, you can create separate cost line items and then total these costs by release, project or program. A baseline and current cost estimate are recorded so budget variances can be tracked. The costs are also categorized so you can differentiate expenses and capital expenditures.

    Integration Management

    Integration Management is the process of coordinating the overall project and the different project management processes. The two apps are fairly comparable in this process. PLP has a slight advantage because it supports different project record types so that you can customize the project phases, picklist values and various page layouts based on the type of project. Having functionality across more of the project management processes also means PLP will make overall integration and management easier.

    Procurement Management

    Neither of the two apps have significant procurement functionality. However, PLP has the ability to forecast cash flows by reporting costs by date. Also, vendor information can be added to the cost records to track vendor spend against a contract.

    Quality Management

    Neither of the two apps have functionality for testing or quality control. However, I hope to add software testing functionality in a future release of PLP. Testing functionality would consist of documenting test scripts and recording testing results.

    Resource Management

    Both apps have the ability to allocate resources to the project. However, PLP only allocates a person to the total project as a percentage of time. PMT allows allocation based on time periods (weeks, months, quarters). I hope to add the same functionality to PLP in the future. PLP does have more advanced functionality for controlling people’s access to project data. PLP can provide global read-only access to a public project. PLP can provide access to the project, but restrict access to sensitive project financial data.

    Risk Management

    PMT only has a single text field to record risks associated to the project. PLP supports multiple risk records with associated mitigation plans. PLP users can assign tasks specifically to a risk to track its resolution. PLP will be expanding risk management capabilities in future releases, but since the infrastructure is in in place, you can easily configure it to provide more detailed risk functionality.

    Schedule Management

    PMT captures isolated tasks and can display them on a Gantt chart. This is about the extent of its scheduling capabilities. As of October 2023 the Gantt chart is pretty buggy. Tasks aren’t being displayed on the correct day in the Gantt. I was having difficulty changing tasks, duration, start or finish dates within the Gantt. PMT’s Gantt is also missing basic scheduling capabilities:

    • Doesn’t support dependencies between tasks.
    • Tasks cannot be scheduled using durations.
    • Tasks don’t capture labor.
    • Tasks can’t be arranged in chronological order.

    PMT has a major flaw in that it uses a custom task object. That means that PMT tasks are stored separately from the standard Salesforce tasks. This means for a user to see all of their assigned tasks they must look in two different places: the Salesforce home page and the PMT dashboard.

    PLP is not intended to be a scheduling tool, but is instead intended to integrate with a best-of-breed scheduling tool to provide a comprehensive project management solution. PLP uses the standard task object, with the intent that a user can view all their assigned tasks on the Salesforce home page regardless if the task is being generated from a project schedule or is created ad hoc directly in PLP. Integration with a scheduling tool involves implementing a flow that will synch tasks between the scheduling tool and the standard Salesforce task object. The popular Salesforce scheduling app Inspire Planner comes with this capability so can integration easily with PLP.

    One nice feature of PLP is that tasks can be associated with both the project and its related objects. So you can associate a mitigation task with a risk, or a follow-up task to a requirement, etc. Yet, you can also report on all tasks within the project.

    Scope Management

    PMT only has a single text field to note scope of the project. PLP has a proper data structure where individual scope records are created and they can be categorized by people, process, technology and whether they are in or out of scope. Individual scope items can also be assigned tasks and Chatter conversations during the planning process. Finally, PLP has a scope metric based on the number of components to be built. This allows tracking the component count changes from the plan baseline as a proxy for scope variance.

    Stakeholder Management

    The only stakeholder management functionality PMT has is to record some key stakeholders such as ‘Owner’s Department’ and ‘Project Initiator’. PLP on the other hand, has been built to support change management. Separate stakeholder records are created and they can associated to the planned changes so that communication and training can be planned. Department managers can also see upcoming changes because their departments have been identified as stakeholders, the stakeholders have been associated to changes, and the changes have been associated to release dates. This requires a complex many-to-many relationship which has been built into PLP’s data infrastructure.

    Scoring Methodology

    I structured the analysis around the Project Management Institute’s (PMI)© project management process. This is outlined in the PM Book of Knowledge (PMBOK)©. First, I listed the project management processes and then the activities within each process. Finally, I developed a list of requirements related to each of the activities. The list of requirements is based upon my 30 years of project management experience and experience evaluating project management tools for clients. Of course, I’m sure I missed some requirements and welcome any suggestions.

    I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. Each requirement was rated as either:

    • Yes – As Is – Meaning, the requirement is met with out-of-the-box functionality. This rating is awarded four point.
    • Yes – With Configuration – Meaning the requirement can be met with minimal configuration or no-code updates. Since, Salesforce is highly configurable I used this rating for simple things like changing picklist values, adding a field to an existing data object, creating a report, etc. This rating is awarded two points.
    • No – Not Available or Requires Customization – Meaning the requirement cannot be met without significant investment of time or money. I assigned this rating if custom coding would be required, or a new custom data object or a new custom flow. This rating is awarded zero points.

    Finally, the scoring spreadsheet totaled the ratings by process to show how the apps compare by process. Therefore, you can assess the apps based on which processes are the most important to you.

    Download PLP vs. PMT Evaluation Spreadsheet

    Click here to download the PLP vs. PMT Scoring Excel spreadsheet.

    In Conclusion

    If you currently have Service Cloud licenses and you are looking for a very basic project management tool, then Salesforce PMT may be a good option for you. If you don’t have Service Cloud or are looking for a fully functioning project management tool, you should have a closer look at PLP.

    Regards,

    Brian

    Additional References

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Free Software Selection Process Template

    A Shogun Uses the Free Excel Software Selection Process Template

    Use this free Excel software selection process template to assess and score your software options. Perform side-by-side fit/gap analysis on seven apps. This tool is also known as a “software selection criteria template”, “software fig/gap analysis”, “software selection matrix”, or “software evaluation template”.

    I’m often asked by clients to assist them in selecting software packages. I was performing an assessment recently and I improved the template I’ve been using for years, so I decided I’d share it. This Excel software selection process template is used for scoring the various software options based on how they meet your requirements. I’ve simplified it a bit and I’ve structured the requirements into the standard Agile format.

    Here is the Excel software selection process template which you can download for free. It should be pretty self-explanatory, but the first tab contains instructions and you can keep reading below if you’d like more details

    Software Selection Process Template – Concept

    The basic concept is pretty simple. You list your software requirements or Agile user stories and then each software is assigned a score based on whether they can meet the requirement. I’ve built several different ways to view the scores, so you don’t have to depend upon only the total score. Your software selection team will then use this score, the price and other factors to make a final recommendation

    Software Selection Process Template – Instructions Tab

    The first tab in the Excel spreadsheet contains line-by-line instructions on using the decision matrix. In the ‘Constants’ tab you’ll enter your custom values and weights. In the ‘Requirements’ tab you’ll list the requirements and then score the individual software packages. The total scores are then summarized on the ‘Scoring’ tab.

    Software Selection Process Template – Constants Tab

    In the Constants tab you define the processes which will be used to group requirements. You also define the weights you’ll assign to various responses to calculate an overall score. I haven’t locked any cells in this template so you can customize as you wish, but if you change the ‘Priority’ or ‘Meets Functionality?’ values the formulas totaling the scores will be broken.

    Software Selection Process Template – Requirements Tab

    This tab lists your requirements for the software. I’ve broken the typical Agile user story into its three elements so it is much easier to read hundreds of requirements in a single sitting. This is also where you assign a process grouping for each requirement (i.e. security, reporting, etc.) and assign a priority ranking. Assigning the priority rankings is usually a team activity with giving the greatest deference to the specialists for each of the processes.

    I typically use this decision matrix twice in the software selection process. The first time I’m creating a short list of software using a critical subset of requirements. I list the most important requirements or broad processes and then score the software myself based on reviewing the software’s web pages and standard demos. I am usually aiming for narrowing down the software candidates to three packages which I’ll ask to participate in a formal request for proposal (RFP) and custom demo.

    The second time I use this decision matrix is during the formal RFP process with the short list of three software candidates. The team completes the full list of requirements and scores them all. I then send the decision matrix spreadsheet to each vendor in the RFP (removing the other vendor’s names) and ask them to respond to each requirement in the ‘Functionality Available?’ and ‘Comments’ columns. The team then reviews the vendor’s responses for accuracy. Finally, I paste all the vendor’s responses into a master version to score across all vendors.

    Software Selection Process Template – Scoring Tab

    The relative scores of the software are calculated automatically on this tab. There are three views. The Percentage of Required Functionality Met, allows the team to assess the software based on how many of the required requirements are met out-of-box (as-is) versus with configuration. The Total Score, allows the team to assess the software based on a total numerical score. The total score is broken down by required versus option requirements and by process.

    Finishing the Software Assessment

    The software score from the decision matrix tool is only one factor the team uses in making a final recommendation. The license price is of course one of the main considerations. In addition, implementation costs can vary widely. The team must also consider the level of support required. Lastly, most teams will place a high value no the look and feel of the software.

    Conclusion

    I hope you find this Excel software selection process template useful for scoring software options. It can be a lot of work to pull all of this together, but going through this formal process has several advantages. It reduces the risk that you’ll purchase a software package that is missing some critical functionality. It facilitates getting the select team to reach a consensus. And finally, it documents the rationale for the team’s final recommendation.

    If you find this software selection process template useful or have suggested improvements, I’d really appreciate hearing from you! It gets tiring posting things to the black hole of the Internet without getting any feedback.

    Regards,

    Brian

    Additional Reference

    Detailed Comparison of Salesforce Project Management Apps

    Build a Remarkable Salesforce Project Management Platform

    Project Charter Guide and Free Templates

    Agile User Story Template

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Now a Proud Member of Pledge 1%

    Springman Consulting is now a member of Pledge 1%. Pledge 1% encourages early corporate philanthropy. My wife (Toni) and I are pledging our time to Mel’s Diner. Mel’s is a food mission that was started in our neighbor’s garage. It now serves 800 meals a week using volunteer labor and food donated by local grocery stores and restaurants (shout out to Harris Teeter, Whole Foods and Chick-fil-A).

    Toni already works on Mel’s full-time coordinating the volunteers and the food pickups. You wouldn’t believe the amount of food which is donated each week. There is so much of it, it can’t all be cooked by Mel’s Diner so lots of it is being distributed to other food missions and charities in Charlotte.

    Pledge 1% has a large community of corporate philanthropists supporting each other. If you would like to join click the logo above to be taken to the pledge page.

    Regards,

    Brian Springman

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • The Unvarnished Truth About Project Lifecycle Pro’s (PLP) Technical Design

    Samurai telling the truth

    The technical details of Project Lifecycle Pro (PLP) for the reader who is Salesforce and IT savvy. The target audience is a Salesforce admin/developer, or an IT manager/analyst that is exploring building Salesforce-native project management capabilities within their company. Particularly, if management is interested in a consolidated view of projects or are interested in establishing a project management office (PMO). I’ll discuss the technical details of how PLP fits into an enterprise-wide project management solution and how it relates to other apps. I’ll also discuss PLP’s broad customization options. Lastly, I’ll make an argument for PLP’s price to value.

    Contents

    What is PLP and What It Isn’t

    PLP is intended to form the foundational custom project objects for an enterprise-wide project management solution. It was built with the intent to handle internal improvement projects like: six sigma projects, product development, mergers & acquisitions, re-engineering efforts, capital improvements, etc. It was also built with a heavy focus on supporting the IT system aspects of these projects, so it will support: custom development, package installs and system upgrades. It was also built to allow customer’s to heavily customize it for their project management process and to integrate with existing apps or future PLP add-on applications to expand project management-related capabilities.

    It is not a scheduling tool. Scheduling and creating work plans is only one aspect of project management and there are already plenty of existing tools. I don’t have any intent on re-building a Primavera, MS Project or any of the Salesforce-native tools like Inspire Planner or TaskRay. I do plan on building standard integrations with scheduling tools in the near future so that users can view all their assigned tasks within a single location in Salesforce.

    It is not a professional services automation (PSA) tool. If your business is providing services to clients at an hourly rate (i.e. consulting, engineering, architecture, etc.), and you want to manage these client service projects then PLP is not for you. There are already several Salesforce-native solutions which specialize in serving this industry: CloudCoach, Certinia are some examples.

    What is Under the Hood

    PLP consists of 22 custom objects, 14 custom tabs, 60+ custom flows, standard dashboards and reports. At the core is a Master Project object with master-detail or lookup relationships to related objects. Related objects are items like team members, milestones, risks, releases, requirements, components, impacts, etc.

    PLP has been built with a data architecture and automation to support administrative functionality which is critical for a robust enterprise-wide solution:

    • Easy Project Sharing – Rather than project managers having to be the owner of a project record and manually sharing access to the project, they can control access through some simple checkboxes. A single click and the project is marked public or confidential. Every Salesforce user has read-only access to a public project. To access a confidential project record and its related objects a user has to be added as a project team member. Project team members can be granted read-only versus edit rights with the click of a button.
    • Separate Sharing of Project Financials – In my experience, companies don’t want broad access to project financials. They don’t want to broadly share some costs or sensitive benefits like labor reductions. This requires that the financials objects are separate from the Master Project object and related through a lookup with separate sharing automation. This allows only certain project team members access to financials, and they can be granted either read-only or edit rights.
    • Standalone Project Dependencies – To manage dependencies between projects, project managers from both the supplying and dependent projects need access to the dependency record. This requires the dependency object to be related to both projects, yet have separate sharing automation so both project managers can access the dependency record though they may not have full access to both projects.
    • Flexible Rollup Capabilities – PLP supports planning at three levels: program, project and release. Therefore, the functionality is required to rollup financials and other project metrics to all three levels. However in my experience, project managers often don’t have all details in early project planning and want to use general estimates rather then exact summations from detailed records. This requires that the rollup functionality can be turned on or off. Therefore, automations have been built which can be manually controlled by a checkbox and are automatically updated as records are updated or added. Automated rollups have been designed to handle up to 10,000 records which should far exceed the requirements of any single project.
    • Associating Tasks to Projects – A custom field has been added to the standard Salesforce task object, so it can be assigned to a PLP project. Automations had to be built to assign the master project to a task when a task is created under and associated with a project’s related object.

    Reporting and Dashboards

    Extensive work was done so that PLP customers would have a functioning set of reports and dashboards right out of the box. Report views have already been built for every custom object, so users can self-serve to build custom reports and don’t have to submit an IT ticket get a report view built. Sixty-plus reports are provided with the install to support the project management process and dashboards.

    Three standard dashboards are provided with the app. These dashboards are customized for the project manager, sponsor and product owner roles. A nifty feature is that the dashboard content is automatically filtered for active projects where the user is assigned the particular role. For example, a project manager only sees data for their active projects. No need to manually update all the filters on the dashboard’s underlying reports to add/remove projects as projects are started or completed.

    Customization Options

    Like all Salesforce-native apps, PLP is highly customizable. I’ve being doing project management for over twenty years and know that every company has their own twist on project management. Therefore, we’ve built PLP with this in mind.

    Custom Fields and Page Layouts

    Of course, you can add your own custom fields to all of PLP’s custom objects. This is going to be most likely in the Master Project object, where you have your own custom meta data you want to track on projects. Like always, you can also customize the page layouts.

    Custom Project Types

    You can also add your own project types and project phase definitions. You simply need to add a custom report type to the Master Project object and use the Salesforce phase functionality to associate it with the report type. Once you have the custom report type, you can also customize dropdown lists or page layouts based on the project type.

    Custom Rollups

    In the case of rollup automations, we’ve allowed customers to clone the standard flows and customize them. This is in case you add a custom financial field or other project metric which needs to be rolled up to the project, release or program level. You can clone the standard rollup flows, and modify them to include the custom fields. You would then deactivate the standard flow.

    Scheduling Tool Integration

    We plan to build standard integrations with scheduling tools, but until then customers can fairly easily build their own integrations. In the case of a Salesforce-native scheduling tool, you simply need to add a PLP Master Project lookup field on the scheduling tool’s project object. This will allow you to relate the schedule to the PLP project.

    You can also then build automations to duplicate the scheduling tool tasks as standard Salesforce tasks associated to the PLP project. This will give users a single view to all other their assigned tasks in PLP and Salesforce. Just be aware, that in most cases the users will have to have a scheduling tool license to view the tasks that are sourced from the scheduling tool.

    For external scheduling tools, you’ll need to associate the PLP project ID and Salesforce user IDs to the schedule and then import the schedule tasks with this ID. You can either utilize APIs or periodically upload the data.

    Price to Value

    The standard price for PLP is $10,000 per year per company. There are discounts for small businesses and nonprofits. This is 5-10x less than what it would cost to build the same functionality yourself, depending on whether you use internal developers or a Salesforce consulting firm. Sure, you could build the project object and related objects fairly easily, but the automated flows are a different story.

    A site license is used because it best suits the intent of providing a single enterprise-wide solution for all projects. Anyone can submit a project idea. Anyone can view public projects. Anyone can participate on a project team. Anyone can run reports on project data. Most other Salesforce-native project management apps are using a seat license model, and they require a license for anyone viewing project data or assigned a task. This can become expensive very quickly. Overall, the site license caps the cost as your company grows and promotes wide adoption.

    The cost is also a pittance when compared to the amount even medium-sized companies spend annually on projects. It requires only a fraction of a percent in productivity gains to justify the spend. It is also a reasonable cost for ongoing support and enhancements.

    Conclusion

    Project Lifecycle Pro has the data architecture and automation required to form the foundation of an enterprise-wide project management solution. It supports advanced sharing and rollup functionality that project managers need. It is also highly customizable to fit your company’s specific project management process. For more technical details, review the admin manual in the links below. Please contact me with any additional questions.

    Additional Resources

    Detailed Comparison of Salesforce Project Management Apps

    Admin Manual

    AppExchange Listing

    Test Drive

    Professional Results With Salesforce Project Management App

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Springman Consulting is Now a Salesforce ISV Partner

    Springman Consulting has joined the Salesforce ISV partner program to create project management applications on the Salesforce cloud platform. The first application is Project Lifecycle Pro (PLP) and is now available on the Salesforce AppExchange.

    Project Lifecycle Pro is a Salesforce project management app enabling the planning, management and reporting of a company’s projects through the entire project life cycle. PLP supports the people, process, and technology aspects of a project.

    Springman Consulting hopes to use PLP as the foundation for building a suite of project management tools for the Salesforce community. The tools will leverage Springman Consulting’s decades of project management experience and the security and configurability of the Salesforce cloud platform.

    For more information, check out the Salesforce AppExchange listing or the Project Lifecycle Pro homepage.

    Free trials are also available on the Salesforce AppExchange.

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • ChatGPT – Equivalent to a Lazy Intern

    ChatGPT – Equivalent to a Lazy Intern

    ChatGPT is impressive, but it is also extremely lazy and inaccurate. It is about as useful as a lazy intern! It has a tendency to simply make things up (i.e. lazy). This is called ‘hallucinations’. There is also a tendency to ‘drift’ or get more inaccurate over time. Think of a young child taking everything it sees on the Internet as gospel.

    I’m Impressed

    Wow! I know ChatGPT is currently popular and I don’t want to rehash old news, but I have to say I’m excited. People who know me know that I don’t get excited easily. I’m excited because after my first experience I’d say ChatGPT is equivalent to a lazy intern. That doesn’t sound like high praise, but I’m saying a computer is equivalent to a living breathing human being with several years of college. That’s impressive even though the computer lacks some of the initiative and motivation we all want in a good intern.

    Brainstorming Possible App Names

    I needed to brainstorm some names for a new application and I was trying to think of someone I could call. I then realized this was the perfect opportunity to try ChatGPT. The most impressive aspect was its recognition of conversational prose. The only thing which indicated I was chatting with a computer were the incredibly fast responses. ChatGPT handled my loose language and poor grammar without batting an eye.

    What follows is my exchange with ChatGPT. You can continue to read deeper into my boring blog post or you can try ChatGPT for yourself. It only takes a few minutes to sign up here: https://chat.openai.com/

    Initial List

    I started by opening a chat with my lazy intern and asked them for names for a new project management application. Apparently, my intern had never brainstormed before and returned only one idea until I asked for ten more.

    Ask ChatGPT for application names

    I’d now trained the intern to provide ten ideas when brainstorming. Note I didn’t have to specify I wanted ten ideas again.

    Incorporate “Full Project Lifecycle”

    ChatGPT ideas for full project lifecycle

    Evoke Emotion

    Kudos to the intern for not correcting my grammar. I meant to say “evoke” rather than “invoke”. But were they now screwing with me? Really, “ProjectGenius” or “ProjElevate”?

    ChatGPT names which evoke the concept of quality

    Please Shorten

    They have now lost interest and are just going through the motions. They were probably planning their spring break between answering my chats. I asked them to shorten some of my favorite names.

    Shorter versions of favorite name options

    “Full Life” Varations

    Next, I asked them to emphasize the theme of “full life”. I thought it would be obvious I was looking for variations of the names I most liked. It is clear they just googled synonyms for “life” and stuck “Proj” in front of them. They were probably too busy making a TikTok video.

    Names using synonyms for life

    Struggles with Symbolism

    I then asked them to be less literal. The intern didn’t really understand the intent of the symbolism, they just regurgitated my example of a tree.

    ChatGPT incorporates tree into names

    Yang?

    In a moment of insanity, I suggest incorporating the term “Yang”. But did I have to do all the work? This intern could have suggested some relevant symbols. It was like pulling teeth.

    ChatGPT Names Based on Yang

    Sincere Response

    I thanked the intern even though I still didn’t have a final name. At least, they generated some ideas. Their response was appropriate, it almost sounded sincere.

    Thanks ChatGPT

    Check Availability

    Then I realized someone must check domain and trademark availability of these names, and it wasn’t going to be me! I could narrow down the list first, but hey, the intern needed something to do. Of course, the lazy intern wasn’t about to spend an hour typing names into ICANN WHOIS. Besides, it was after five o’clock.

    I wasn’t amused when they told me how to do it myself. That will have to go in their review.

    Ask ChatGPT to check domain and trademark availability

    No, You Do It!

    “Okay smart ass, go ahead and write a script to check the domain availability”, is my response. What they sent was complete garbage. They obviously didn’t even run it once. There isn’t any ICANN status value of ‘available’, they completely made that up.

    Python script for checking domain availability
    ChatGPT provides useful guidance on using the Python script

    Won’t Test

    “Okay intern, how dare you send me a script that you didn’t test!”, is what I screamed at my laptop. I told them to test it, and they tell me they haven’t learned how to do that yet. Then they start back peddling telling me the Python script “is an example” and that I have to fix it myself!

    Like any Gen Z they assume anyone over 40 is technically incompetent. They suggested they don’t need to check “google.com” or “amazon.com” using the script because they know those are already taken. To add insult to injury they reminded me that I need to have an internet connection!

    ChatGPT can't test

    Conclusion

    Well, that was the end of my interaction with the “intern” ChatGPT. I’ll definitely throw them a bone now and then and ask for simple things, like brainstorming ideas. I’ll also continue to be polite and keep my criticisms to myself because I’m sure that in a few months I’ll be working for them!

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

  • Managing Your First Software Project

    The first in a series to help you manage your first software project, written by a thirty-year project management veteran.

    You are an up-and-coming superstar in your company and thus, you’ve been assigned to lead your first software project. Maybe, it is upgrading a financial system package, building a new website, or selecting and implementing a new ERP system. It could be almost anything. While you are a great manager and really know the business, you don’t know how to install or build computer systems. You will obviously have some help, but if you are going to manage the project you need to understand what is going on.

    I’ve been helping managers like you run large software projects for nearly thirty years. In this and a series of related posts, I’ll be sharing my experience and giving you the background you’ll need to manage your own project. This post will be an initial overview and starting point advice. I’ll be adding links to other posts covering specific aspects of managing projects.

  • Software Project Roles
  • Software Environments
  • Conclusion
  • Additional Reference
  • People, Process and Technology

    All projects have a people and process component and in this modern age 99% of them also have a technology component. Your primary role will be to manage and coordinate all three of these components to make the project a success.

    People

    What do I mean by “People”? I mean getting the people in the company to support your project or to at least use the software. Until the androids take over, this will also be the hardest part of the project. People are set in their ways and have their own agendas which may not include the extra work your project will cause.

    Consultants use the term “Change Management” to encompass the people aspects of a project. This usually just boils down to training and communication in most projects. In more complex projects this could include designing new positions, adjusting bonus incentives, layoffs or staffing new offices. Whole books have been written on Change Management and I’ll provide more details in other posts, but for this overview just remember that you can build the best software yet it is worthless if people don’t use it. Let’s use COVID 19 as an example. A revolutionary vaccine with the capability to save millions of lives was developed in record time. Yet, a huge level of effort  had to be expended to convince people to take it. The vaccine was developed in a year, but I’m writing this three years after the vaccine was developed and people are still debating it.

    Process

    What does “Process” entail? This refers to the business aspects of the project, and more simply the business process in which the project is changing. For example, the business process scope could be: financial reporting, customer service, distribution, warranties, etc. Your project will be improving this process in some way and will ultimately increase the business’ profit. In the simplest projects, this involves defining the scope and business case.

    An example of scope would be domestic distribution of customer orders in North America, but not international shipments. This is the area where your project will focus, including a rationale for why you are excluding certain processes. Maybe North American shipments are handled in SAP, while international shipments are handled in a custom system developed by your freight forwarder. If the biggest opportunity lies in North America, it makes sense to simplify by only working on SAP for now. While the international shipments can be addressed in the future by another project.

    The business case is simply what benefits will the business owners get for spending the money on the project. How much will the project cost and how much will profit increase? There are projects, like regulatory compliance, which don’t have a direct impact on profits other than avoiding fines or keeping the owner out of prison, in which case the business case is: to keep the owner out of prison.

    In complex process efforts, the business processes or procedures are being redesigned. The way people will do their work is changing. This involves detailed process modeling, documenting new procedures and redesigning performance metrics.

    Technology

    What is meant by “Technology”? In general, it is the thing being built or modified. This is most often software, but could also be a new COVID-19 vaccine. However, I’ll focus on projects building or modifying software since I don’t know anything about inventing vaccines.

    The computer systems will be referred to as “IT”, “systems”, “software” or “hardware”. You will most likely have help from your information technology (IT) department with much of this work. But you don’t want to be blindly leading the technology aspects, entirely dependent on the IT group. You need a basic understanding of how software is developed and implemented, especially so you understand what the People and Process aspects of the project need to do to support the Technology work.

    I cannot emphasize enough that this is the most important component of the project, this is where value is being added. The People and Process components are the supporting players. Therefore, an efficient project is going to focus on making the software developers as productive as possible. If developers don’t have fingers on keyboards then value isn’t being created. If the new computer system doesn’t work, then all the process changes and training are for naught.

    When IT projects go awry a lot of blame is usually leveled at the developers for sloppy coding or being too slow. This is rarely the case. In most cases it is a systemic issue about how the project was managed. System requirements were late or sloppy. Training was poor or non-existent. Testing was poorly designed. The list goes on, but it boils down to the project manager (e.g. you) didn’t do a good job of feeding the developers what they needed and didn’t manage the supporting People and Process components properly.

    Software Development Life Cycle

    All software projects go through the same basic process: Plan, Analyze, Design, Build, Test, Deploy. There are variations depending on whether you are installing existing software or doing custom development, but the basic process is consistent. You will only be performing the Plan Phase once but you’ll be repeating the other phases for each release. I’ll create a post on the details of each of these phases but here is a summary.

    Plan

    The Plan Phase is pretty obvious, you are planning the project and making high-level directional decisions before performing detailed analysis. Some of the key decisions are:

    Analyze

    The Analyze Phase for the first release on large projects can take several months, especially if you have to select the off-the-shelf software you want to purchase. For small projects doing custom coding or using existing software this phase can be only a couple of weeks. The key deliverables for the Analyze Phase are:

    Design

    The Design Phase is focused on software design. All the business and process design work has already been done in the Analyze Phase. The phase is extremely short for small projects making changes to existing software. Software development is so quick these days, it is often easier to build something and review it for input rather than spending a ton of time designing it. If you are building from scratch on a large project the main deliverables are:

    Build

    The Build Phase is the fun phase. The team actually starts building custom software or configuring off-the-shelf software. The Agile software methodology is applied in this phase to build the software quickly and efficiently. You should assume you will be using the Agile approach, as this is the de facto approach for all modern software projects. As manager of the project, you should expect to see working software coming out of you systems development team daily with formal demos every two weeks.

    Test

    The Test Phase should overlap with the Build Phase and wrap up with formal user acceptance testing. As soon as something is built it should be tested by the person who wrote the requirement. So this level of testing should be an ongoing real-time process within the team. Once the build is complete for the release, you should hold formal user acceptance tests with the end users to make sure all the requirements were understood properly. Once end users can get their hands on the software they will always come up with new requirements or bugs. It will be your job to decide whether these new requirements or bugs must be addressed for the first release or can be pushed to a later release.

    Deploy

    The Deploy Phase covers all the activities required to put the software into use. Key deliverables are:

    If your project has multiple releases, you now repeat the Analyze, Design, Build, Test and Deploy phases for the next release. To be efficient, phases for each release should overlap. Business Analysts should start analysis for release two during the Design Phase of release one. Developers should be building release two during the Test Phase of release one.

    Software Project Roles

    Hundreds of people can work on a large software project, and the various responsibilities can be numerous but they basically boil down to a few key roles. Here is an overview of these key roles:

    Software Environments

    A key concept that managers struggle with on their first software project are the many software environments. Think of the environments as different snapshots of the software in time. Different companies use different names but they typically all use four environments for the same functions:

    Some key environment concepts you need to understand as manager of the project are:

    Conclusion

    I’ve given you an overview of the key subject areas for managing a software project. Of course, we’ve just scratched the surface. I’ll be adding more posts on these various subjects to flush out some of the details. Remember your role will be representing the business and ensuring the project goals are achieved. If you assemble a good team, you’ll have the help you need to execute the details correctly. But hopefully I’ve armed you with a enough so you can speak a common language with your expert teammates.

    Additional Reference

    Project Charter Guide and Free Templates

    Save Time with Free Excel Software Decision Matrix

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

    Subscribe
  • Build a Remarkable Salesforce Project Management Platform

    Salesforce Project Management

    Using Salesforce project management apps opens up a wide array of options for automation, customization and consolidated project reporting. I was recently helping a client use Salesforce for project management and was greatly impressed with the capabilities of Salesforce as a development and business process modeling (BPM) platform. Customer relationship management is Salesforce’s specialty, but the architecture they’ve built can be leveraged for all sorts of solutions. Here are my thoughts on Salesforce project management capabilities.

    Using Salesforce Project Management for Scheduling

    If you own Salesforce, you should consider using Salesforce for project management. First, there are several scheduling tools on the Salesforce app exchange. I liked Inspire Planner because it had the most robust scheduling capabilities, but there is also TaskRay and other scheduling tools. All of them have a scheduling tool at the core, but bundle other functionality like Kanban boards and resource management. None of them have the advanced features of a MS Project or Primavera, but those advanced features, like resource load leveling, are only going to be used by professional schedulers. These scheduling apps will suit the needs of 99% of your users. Most offer free sandbox trials so you can select the best fit.

    Utilizing a native Salesforce scheduling app has several advantages:

    • Tasks assigned in the schedule can be assigned and completed by users in their Salesforce task list. They don’t need to access the project schedule.
    • The schedule is saved as Salesforce data, so it can be used easily for reporting. If you utilize standard milestones in your project plans, you can create summary reports which pull the key milestone dates directly from the schedule.
    • Standard project tasks can be linked to automation within Salesforce, like forms for data entry and prompts for document uploads.
    • Salesforce’s ease of configuration can be utilized to customize data fields, reports and dashboards.
    • You don’t need to maintain separate user lists for assigning tasks, as you would in an external tool.

    The benefits of a project manager being able to assign a task in the project plan and then not have to follow up with the assigned user is a huge time saver. When the task is assigned, it will land on the person’s standard Salesforce task queue. When the person completes the task it will automatically update the status of the task on the schedule, so the project manager has visibility to completed and past due tasks. No more exporting the project schedule to Excel or a PDF to share it with others. No need to email people to alert them to an assigned task. In fact, alerts for past due tasks can be automated using Salesforce’s Flow tool.

    There is also a huge benefit to the people assigned the tasks: they have a single list of assigned tasks across all projects which they can sort chronologically. A person can easily be working on multiple projects and also have ad hoc tasks assigned from their managers. They don’t need to track all the demands on their time separately, it is now all their Salesforce task list.

    Using Automated Salesforce Project Management

    Every project management office (PMO) I’ve seen has to spend a lot of manual time consolidating status reports and key milestone dates across all projects. If you can tell project managers to include the key reporting milestones as standard tasks, these summary reports can be completely automated. The key is the standard task ID. You can create a standard task ID objects in Salesforce which standardizes key dates like: project approval date, end of analyze phase, first release date, and end date, etc. This list of standard task IDs can then be added as a lookup field on the project schedule, so the project manager can assign the standard task IDs to their custom tasks in their project schedule. This allows the project manager to designate which task in their custom schedule corresponds to the standard task used for reporting.

    Assign standard task IDs to the project schedules allows building automated reports and workflows. The system knows that if it needs to report the first release date for a project it queries the project schedule for the end date associated to standard task ID ‘1.10.01 – First Release Date’. In addition, all the standard milestone dates will be immediately updated on all the various summary reports if the project is re-scheduled. Everyone has visibility to the new dates at the same time. Automated alerts can even be built to notify certain individuals if specific milestone dates shift. Note, publishing updated milestone dates based on a schedule change can be problematic but I’ll address in a separate detailed post.

    I’m most excited about how the use of Salesforce and standard task IDs provides the ability to blend the forecasting capabilities of the project schedule with business workflows. If a user is supposed to capture specific data as part of a standard task, a custom form (e.g. screen flow) can be created and linked to the standard task. When the user opens the associated assigned task, they can be presented with a link that opens the appropriate form. A link to a standard procedure can also be embedded in the task. The process I worked on was very document-intensive so users were presented with the existing documents they needed to reference to complete the task, as well as, the user was prompted to upload documents they needed to create as part of the current task.

    Tying process flows to the schedule also allows the schedule to be simplified. Rather than listing all the tasks required for an activity on the schedule, the project manager just lists the overall activity and assigns it to the person with the first task. The workflow is then kicked off which manages and assigns the individual detailed tasks.

    Using Salesforce to Capture Project Data

    There is a lot more to project management than scheduling tasks and workflows. There are planning, estimating, and reporting processes among others. These non-scheduling processes can also be supported by Salesforce for they consist mainly of capturing and reporting data. The decision you need to make is where to store this data. I recommend either building your own project objects in Salesforce or using a Salesforce app with a site-based license. If you expand the popular Salesforce scheduling tools to store and report project data then every one who views that data must have a seat license for the scheduling app. This can get expensive quickly.

    I recommend implementing a core project management solution for the data storage and reporting functions and then integrating this solution with other specialized apps for scheduling, estimating, etc. If you don’t want to build your own core Salesforce project management solution, two options you should investigate are the Salesforce Project Management Tool (PMT) and my app Project Lifecycle Pro.

    PMT is built by Salesforce Labs and is free. The only catch is that it uses Service Cloud cases for documenting project issues. This means that users will need a Service Cloud license which would add considerable cost if you don’t already have Salesforce Service Cloud.

    Project Lifecycle Pro was released in the Fall of 2023 and I’m quite proud of it. It uses a site license to encourage broad use within your company at a reasonable cost. It supports all the people, process and technology aspects of a project. It also has advanced features for data access, dependency management, estimating and dashboard reporting. You can get free demos and other information at the AppExchange listing here: Project Lifecycle Pro.

    In Conclusion

    To summarize, if you are involved in the 99% of projects that don’t require the advanced features of a MS Project or Primavera schedule, and you already own Salesforce, you should consider building or enhancing your project management solution on Salesforce. Go to the AppExchange and search ‘project management’ for a list of more than 300 Salesforce project management apps. Download their free trials to get a feel for their capabilities.

    Regards,

    Brian Springman

    Additional Information

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.