I’ve met several people at networking events that are interested in coding using AI. I thought I’d create this post that I could share with them and future friends.
I’m going to be lazy and write these instructions a little differently. Instead of writing detailed step-by-step instructions I’m just going to to list topics which can be prompted to AI to provide the details (i.e. “How do I install Claude Code?”)
I’m also going to focus on the tools I use rather than providing all options. Again, readers can always prompt their favorite AI tool for alternatives.
Let’s get started…
Claude Code (CC)
I pay $100/mo for the Claude Max plan because I’m doing a lot of coding. The Pro plan is $20/month. You can pick the plan that is right for you.
I started just using the free Claude prompt tool and manually copying code back and forth. Claude Code will make the changes directly to your code base for you so you don’t need to copy and paste.
Visual Studio (IDEs)
Visual Studio pre-dates AI coding and is simply a text editing tool designed to make coding easier. All code is stored as text files with different extensions: .py, .md, etc.
Visual Studio is free, and is an industry standard. You can install a Claude Code (CC) extension in Visual Studio so you can use CC there. But be warned some CC commands aren’t supported in the extension and must be executed in the terminal window (/agents).
I’m using it less and less as I do more directly in the terminal with Claude Code but I still find it useful.
Your Terminal
The terminal is simply where you give your computer commands. On Windows machines this is also known as ‘Command Prompt’. You can also open a terminal window within Visual Studio.
Bash
Bash is the language you use to give your computer commands in your terminal. On Windows machines you can also use PowerShell, however, I’ve found CC does a better job of writing Bash commands. CC will give you the Bash commands to run.
Bash has to be installed and is free. CC will walk you through it.
Git
Git is a free version history tool for your code. It allows you to take snapshots (commits) of you code so you if you screw something up you can return to an early snapshot.
It also allows you to isolate code changes into branches. This allows you to build a certain functionality in an isolated branch and only merge it to your ‘main’ codebase once it is working. This same branch functionality allows several developers to work on the same project simultaneously.
Git is a steep learning curve, but you only need to know the basic commands and can tell CC to execute them so you don’t need the exact syntax memorized.
Git is also the industry standard, every developer knows/uses Git.
GitHub
The free online/cloud version of Git. You ‘push’ your Git code up to GitHub so you can share it with others, or so you don’t lose all your code if your hard drive crashes.
GitHub is also where you can find open source code shared by other developers.
Open Source Code
Have you seen a trend with everything being free? The developer community is one large fraternity with everyone helping each other. Before I start building something I ask CC to search GitHub for existing open source code that someone has shared, which we might be able to use.
Just make sure you comply with the license terms. These are the terms the developer has defined for use. For example an MIT license means you can do anything you want. Other licenses only allow personal use.
Stack
This is the coding languages, database and architecture you are going to use. Just ask CC to plan the project and provide you with the best stack. Examples, would be using Python as the language and AWS or Google as the cloud provider.
Local vs. Cloud
A key design decision. If your code is only going to be used by you and doesn’t need to be always on, then you can just keep the code on your local computer.
If the code is going to interact with others or be always on, then it needs to be on a server that is on the internet and always on. So you need to ‘host’ with a company which provides servers (AWS, Google Cloud, Azure, etc.)
Cloud Hosting
If you need the cloud, then your big boy choices are AWS, Azure, Google Cloud or Supabase. Vercel, Netlify, or Railway are simpler options for beginners. CC will help you make this decision.
Even though AWS is the choice of large enterprises, I still use it as a solopreneur because I know it from building enterprise solutions. CC also can execute and build the AWS components from your terminal after you install the AWS CLI.
If you use AWS, be careful with costs. It charges you based on what you use. If you accidentally build a loop consuming tons of resources/tokens you are going to get a whopping bill.
I don’t have any experience with the others.
Databases
One of the key design decisions CC can help you make is what type of database to use to store your data. The database can simply reside on your local computer or with your cloud or web host.
Commit Hooks
You can setup free tools that check your code when you perform a Git ‘commit’ (i.e. snapshot). These tools will look for security vulnerabilities and proper coding. You set them up to run automatically when you run a Git commit. CC will automatically fix any problems they find.
Project Scaffold
A ‘project’ is simply a folder on your computerthat holds your code. When you start it is blank, you can ask CC to setup the sub-folder structure (scaffold) for the type of coding you are doing: Python using Claude Code.
Agents
These are simply prompts that you use lots. For example, I have agents that audit my code for specific mistakes I find CC makes.
CC can also create its own agents so for a large code build you can have 5-6 agents running simultaneously all working on different functionality.
Skills
These are special instructions that you can build for CC. These supplement Claude’s existing training. Think of Trinity in the Matrix downloading the knowledge of how to fly a helicopter.
For example, I was a building a WordPress website with a specific template. Claude hadn’t been trained on the specific syntax of that template so I was getting all sorts of errors. Each time I fixed the error, I added the syntax to a skill so Claude wouldn’t make the same mistake again.
Claude.md
You should have a Claude.md file in every project. This provides the context/requirements of the project and CC will can continually refer to it.
Also, you should have a global Claude.md file that has instructions for all projects (not project specific). This file is stored at ~.claude\CLAUDE.md and loads at the beginning of every project session along with the project-specific Claude.md. An example of what should be in this global file is the need to properly handle null values.
Website
Most of your solutions will need a user interface and the default is a website where you interact through an Internet browser. You’ll need CC’s guidance on how you should build the website. In either case, CC can help you build it.
Low Code Websites (CMS)
There are all sorts of low-code website tools like WordPress and Webflow which allow non-coders to build websites and manage content. With the ability to custom code with AI, paying the extra for low-code doesn’t make any sense.
However, it is useful to not have to use CC every time you want to make a small change or add some content. This where the CMS (content management system) aspect of these tools add some value.
This is why I use WordPress. Because it allows easy content management but is open sourced and free. It also has the option for custom code, so I can use CC to build custom pages or functionality with WordPress.
Custom Websites
You don’t need to use the low code website tools, you can build a website completely from scratch using CC. If this is what you want to do, then you should ask CC about React and Next.js.
Environments (Dev, QA, Prod)
If you’re building a true commercial solution, you’ll need to be able to make improvements without screwing up the live version being used by customers.
This is where multiple environments come in. This is only relevant if your building on a sever (AWS, etc.). You have a Dev environment/account where you can build, a QA for testing and Prod which is stable and is used by your end customers.
Secrets and API Keys
Secrets are things like passwords. API keys are the passwords used when computers talk to each other. You’ll need this information stored on your local computer but you need to make sure they are never posted to the Internet (i.e. GitHub).
If you ask, CC will direct you on how to handle secrets and API keys safely.
Step-by-Step vs. Autonomous Coding
I started AI coding by giving the AI little bits of functionality to build and then creating the full app step-by-step. I have since switched to autonomous coding where I spend about an hour planning the entire app with CC. Once I’ve approved the planning document I tell CC to spin up multiple agents to build the app and then let it run. It can then take 3-4 hours to build and I can focus on other things.
Claude Commands
Open your terminal and type ‘claude’ to launch Claude (once installed). Then type ‘/’. This will give a list of all the available Claude commands.
/remote-control
Before I kickoff a long build I use the Claude command ‘/remote-control’. This allows you to link your current Claude session on your computer with the Claude app on your phone.
I can then leave my desk and run errands or garden during the hours Claude is building. If Claude has a question, the question pops up on my phone. I answer it and keep Claude working. It also shows me when Claude is done.
Stripe
If you are going to sell things, then you should use Stripe.
Once you have an account setup you can create products and pricing. Stripe then gives you the code to post a buy link on your website.
If you are using WordPress, you can also use WooCommerce to create a website store integrated with Stripe.
Conclusion
Well, that is all I can think of at the moment. I’m sure I missed some things. Please reach out to me and let me know if I missed something. Also, let me know if you found this helpful.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
BigTime Software is a professional services automation (PSA) tool with extremely robust time and expense reporting functionality. It also has a very nice user interface which makes it easy to navigate through a lot of detailed functionality. There are four product levels and the highest level with their Foresight module is required for broad PSA functionality across cost, resource and schedule management. It worked well in my free trial, however, there are worrisome customer reviews around financial system integration and support which I was not able to assess.
BigTime Software was reviewed against 200+ project management software requirements on a downloadablespreadsheet. BigTime 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.
Customized PSA Tool Shortlist
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.
BigTime scores among the top of PSA tools I’ve reviewed that are not Salesforce apps. While several Salesforce-based PSA tools edge it out on functionality, it has extremely strong functionality in time and expense management and the invoicing of the resulting times and fees. There is a huge amount of flexibility in customizing rates and the invoice type for individual projects.
Its highest end subscription with the Foresight tool has resource management capabilities on par with all the leading tools. It will definitely meet all the needs of a small firm. Dedicated resource managers in large firms may have issues with some of the resource management gaps.
The scheduling tool is sufficient and has some unique features I like. However, it has one major gap that will not support complex projects: it only supports two levels of tasks. Meaning, you can only create tasks, and one level of subtasks within a task. Now, it does also support task checklists which can be considered a third level.
BigTime Pricing
I find it pretty annoying that BigTime Software has four subscription levels and non-transparent pricing for the upper level. This will just increase the complexity of your evaluation and require negotiating custom pricing. The published prices are in line with other PSA tools. Here is the pricing as of this post and a link to their pricing page:
Essentials – $20/user/month. No resource management, project budgeting or custom reporting.
Advanced – $35/user/month. Adds a client portal and custom reporting. No resource management.
Premier – $45/user/month. Adds project budgeting, multi-level approvals and simple resource management.
Foresight Connect – Custom pricing. Full functionality with robust resource management.
Evaluate BigTime Quickly
Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate BigTime quickly and thoroughly.
Cost management is one of BigTime’s biggest areas of strength. It has very detailed and flexible time and expense tracking capabilities.
Strengths
Planned Budget – Create a planned budget and track actual hours/fees against the plan.
Custom Fields – You can create an unlimited number of custom fields to support your unique cost management process.
Non-Billable Tasks – With a click of a button mark a task as non-billable and it won’t be invoiced to customers.
Enter and Approve Time and Expenses – Employees enter their time and expenses and they are routed for approval prior to being invoiced.
Supports Multiple Billing Types – Time & Material, Progress/Milestone, Fixed-Fee, etc.
Overtime Rates – Can assign 5 standard rate types to an employee. This enables you to easily bill overtime rates.
Generate Invoices & Track Payments – Many PSA tools require integration with financial systems to actually generate invoices and track payments. BigTime has this native functionality.
Integration with Financial Systems – You can integrate BigTime with your existing financial systems for basic accounting, time & expense reporting or invoicing.
Weaknesses
No Daily/Weekly Rates – Only supports hourly rates. Daily and weekly rates have become popular within professional services firms.
Lacks Earned Value Metric – Without an earned value metric, BigTime doesn’t support advanced project forecasting capabilities like: cost performance indicator (CPI) and estimate at completion (EAC).
Doesn’t Pre-Populate Timesheets – This is the only timesheet gap I found. Some PSA tools will pre-populate a user’s timesheet with the tasks that were scheduled for that week. Speeds time entry and serves as a reminder to enter time for all tasks.
Can’t Enter Time for a Completed Task – When testing, I wasn’t able to enter time against a completed task. Users will have to remember to enter all time prior to marking a task as complete.
Integration Management
BigTime’s integration management is about average when compared to other PSA tools.
Strengths
Custom Fields – You can create an unlimited number of custom fields to support your unique project meta data and status reporting.
Project-Specific Access – Only employees assigned to the project team can view the project. Allows you to use BigTime for confidential projects.
Weaknesses
Automated Stop Light – BigTime automatically calculates the project stoplight status (red, yellow, green) based on factors like overdue tasks and budget performance. Some might find this valuable, but as a project manager I would find it annoying not to rate the project manually based on my overall assessment.
No Issues Log – Doesn’t support documenting and assigning project issues.
No Programs or Portfolios – BigTime does not rollup individual projects into a single program. It also doesn’t support grouping projects into portfolios for joint reporting.
No Change Orders – With all of BigTime’s budgeting functionality it is surprising that it doesn’t support change orders.
Procurement Management
BigTime is unique for most PSA tools that you can capture vendor spend. While BigTime’s procurement management wouldn’t support a construction project it should be sufficient for most professional services firms.
Strengths
Vendor Spend – It tracks vendor expenses and thus, you can track vendor spend.
Resource Management
BigTime’s resource management functionality is robust and will work well for small and medium-sized firms. However, dedicated resource managers at large firms may prefer other PSA tools for their user interface and additional functionality. Also remember, the highest-end solution must be purchased for full resource management functionality.
Strengths
Allocate Resources by Project – When planning projects, an employee can be allocated for X hours per week to a project. This means you don’t have to have all tasks identified with hour estimates to initially plan the project.
Plan Labor by Role/Skill – You can plan resource demand by role/skill rather than by individual.
Separate Access to Financial Data – You can control a user’s access to project financial data like budgets and rates. However, the access is universal not project specific.
Softbook Resources – Can soft book resources so when matching people to demand you know which people are already formally assigned to a client versus those that are just penciled in.
Track PTO – Very few PSA tools have the ability to track employees time off and where they stand against their allowable PTO.
Weaknesses
Resource Management Dashboard – It may be subjective, but I didn’t like the design of the resource management dashboard a resource manager would use to fill demand as much as ones on other PSA tools.
Doesn’t Forecast Demand from Sales Pipeline – BigTime is at a little of a disadvantage in this area compared to the Salesforce-based PSA tools. There isn’t an ability to generate a long term resource demand based on the services in the sales pipeline.
Can’t submit or Publish Resource Openings – Project managers can’t submit a specific resource request. Employees can review openings and submit themselves for the work. Now project managers can add a task assigned to a role to their projects which then needs to be assigned, so this a nuanced issue.
Schedule Management
The schedule management functionality is sufficient for simple projects. There are some unique innovations that I liked. However, as a professional project manager it would be difficult for me to plan projects with only two levels of tasks. This seems to be a key differentiator among PSA scheduling tools: unlimited task hierarchies versus limited task hierarchies (2-3 levels).
Strengths
All Predecessor Types and Lag– Supports all types of predecessors: finish/finish, finish/start, start/start and start/finish. Also supports defining lag for predecessors.
View All Assigned Tasks – Employees and project managers can view all tasks across multiple projects. Can also post tasks to your personal calendar.
Fixed/Unfixed Duration Scheduling – Many PSA tools don’t support fixed/unfixed duration scheduling where you can control whether the duration changes if you add/subtract resources on a task. However, the approach is different from other tools because there isn’t a duration field. This might be confusing to PMs used to other tools.
Add Custom Fields – You can add an unlimited number of custom fields to the tasks. This will allow you fill gaps, such as, Agile fields like: story points and acceptance criteria.
Assign Multiple People to a Task – Not all PSA tools support this feature.
Task Alerts – BigTime has two very useful task alerts. One when a person is first assigned a task. Another to the task owner when a dependent task has been completed so the task can now be started.
Activities – This is unique functionality I haven’t seen on many other PSA tools. A project manager can assign a person an ‘Activity’. This is a task associated with the project but not part of the schedule. This would be useful for ad hoc tasks like ordering lunch for a meeting which you don’t want junking up the schedule.
Weaknesses
Duration Scheduling Approach – This is a nit, because BigTime does support fixed/unfixed duration scheduling where you can control whether the duration changes if you add/reduce resources on a task. But it doesn’t have a duration field, it just uses the start/finish dates, which may be confusing to PMs used to other tools.
Lacks Single View of Tasks/Activities/Checklists – There are separate views for a person to see their assigned tasks, activities and checklists across all projects. It would be best if there was one chronologically-ordered consolidated list.
No Kanban Board – If you are an Agile development shop, BigTime probably isn’t the best tool for you. Or, you’ll need to use their Jira integration.
Lacks Mass Assignments on a Project Template – While BigTime has project templates it doesn’t allow the creation of a template where the task is assigned to a role. It also doesn’t allow mass update of the project task assignments by defining which person will fill the role.
Unsupported Processes
The following project management processes aren’t supported by BigTime. Except for the risk management, most PSA tools don’t support these process either:
Communication Management
Quality Management
Risk Management
Scope Management
Stakeholder Management
Customer Reviews
BigTime has favorable reviews on the majority of the review sites. However, it has a concerning 2.8 stars on Google, but this is from only 12 reviews.
BigTime appears to have one significant security gap:
No Session Timeout – The user is not logged out after a certain amount of inactivity.
App Scoring Methodology
I’ve been evaluating all of the project management software and sharing the results to help others save time in making an informed decision. The evaluation is based on 200+ standard requirements I’ve documented across the software I’ve reviewed. You can purchase the software evaluation scorecard (fit/gap analysis) I used for this review. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.
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
I believe small/medium businesses that aren’t on Salesforce are going to find BigTime a viable option as their PSA solution.
Enterprise Salesforce customers are going to find a better solution in several of the Salesforce-native PSA tools. In addition to some broader functionality, these tools will be more customizable being on the Salesforce platform.
Remember, to get all the functionality outlined in this review you need to purchase the Foresight solution which is the most expensive solution. Also, you should research the criticisms cited in the online reviews. I highly recommend you get a free trial before purchasing any software.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Kantata OX
Kantata OX (Mavenlink) should be on the software short list of any large company buying a cloud-based PSA tool. It is expensive, with a minimum purchase of 50 seats so it is not ideal for small companies. You can also consider it for a PMO or project management solution if resource management and scheduling are high priorities. However, its lack of risk management and limited stakeholder management are going to be issues for most PMO applications.
In this post, Kantata OX is reviewed against 200+ project management software requirements. Kantata OX is 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.
Customized PSA Tool Shortlist
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.
The Kantata OX app is a cloud-based professional services automation (PSA) tool. It was previously named Mavenlink.
Kantata OX should not be confused with Kantata SX which is a separate solution built on the Salesforce platform. Kantata SX was formerly named Kimble, and I have a separate review of SX.
Kantata OX has a strong amount of professional services automation (PSA) tool functionality, and therefore should be included in anyone’s assessment of cloud PSA tools. It has excellent resource management functionality and good scheduling capabilities, which are the main focus of PSA tools. Its cost management features are also quite robust.
However, OX should only be considered by companies that don’t use Salesforce. SX scores better than OX so it should be considered for anyone using Salesforce. SX also has more customization options since it is a Salesforce app.
OX’s broad functionality also makes it an option for an internal project management office (PMO) tool. However, I believe most PMO shoppers will find gaps in risk management and stakeholder management, while the schedule management capabilities are solid but could be stronger for complex projects.
Download Kantata OX Evaluation Scorecard
Click here to download the Kantata OX Excel spreadsheet, where Kantata is scored against 200+ project management requirements.
Kantata OX doesn’t publish standard pricing plans 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, 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 $35K – $66K.
Communications Management
Kantata OX has basic functionality to communicate project status. However, it doesn’t have robust change management-related functionality around scheduling and tracking communications or training.
Weakness: Limited Stakeholder Communications
It lacks the ability to document and track the communications required for each stakeholder group, which is important for change management.
Weakness: Lacks Change Management
Like many PSA tools, it was not built with a focus on change management. There isn’t sufficient functionality focused on identifying stakeholders and the training or communications they require.
Cost Management
Cost Management is one of the processes in which Kantata OX excels. It appears to be very focused on planning and measuring project profitability, which 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. It will also track invoices and customer payments.
Strength: Cost Metrics
It has numerous metrics to measure the project’s financial performance: utilization, profit margin, and earned value analysis.
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 essential for cost control.
Integration Management
Overall, Kantata OX has decent integration management functionality, scoring. It supports change orders and has good project access controls. The main weaknesses are the 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 for approval. This functionality is essential for proper scope management.
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 robust functionality to support estimating and documenting a business case. It has lots of cost management functionality, but limited 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.
Procurement Management
Kantata OX has modest procurement management functionality. It provides basic vendor tracking but lacks some more advanced procurement capabilities.
Quality Management
This is one of Kantata OX’s weaker areas. Like many PSA tools, it is not focused on software development firms. It basically doesn’t have sufficient functionality focused on testing processes or software quality assurance as part of project.
Resource Management
Resource management is Kantata OX’s greatest strength. This makes it an excellent choice for professional services firms focused on optimizing resource utilization.
Strength: Resource Demand and Capacity
You can create very detailed resource demand forecasts by skill and then assigned named or unnamed resources. The tool provides excellent visibility into resource capacity and availability.
Strength: Resource Analytics
It provides strong analytics around resource utilization and performance. You can easily track billable time, non-billable time, and bench time to optimize resource efficiency.
Strength: Project Access
It has detailed functionality for controlling project access. Team members can be given specific access levels to various components of the project. The ability to make projects confidential is important for sensitive projects.
Risk Management
Risk Management is one of Kantata OX’s biggest gaps. This is a significant limitation for organizations looking for comprehensive project management capabilities.
Weakness: No Risk Register
The lack of a formal risk register is a significant gap. You can’t properly document, track, and assign risks to be mitigated.
Weakness: No Risk Analytics
It lacks the ability to analyze and quantify risks, limiting your ability to prioritize mitigation actions.
Schedule Management
The scheduling tool in Kantata OX is good. It supports multiple task levels, dependencies, and critical path analysis. From a pure scheduling point of view, it only lacks some advanced constraints and automatic rescheduling based on actuals. Most of the other gaps are related to features you would want for IT development.
Strength: Gantt Chart
The Gantt Chart functionality is solid, supporting:
Multiple levels of tasks
Dependencies
Critical path analysis
Task assignments
Weakness: IT/Agile Schedule Management
It lacks several pieces of scheduling functionality which a systems development project would use:
Robust sprint planning
Dedicated user stories
Agile epics and themes
Burndown reports
Scope Management
Kantata OX lacks scope management functionality. While it has some basic work breakdown structure capabilities through its task management, it lacks formal scope management features.
Weakness: Lack of Detailed Scope Documentation
It lacks the ability to document a detailed list of the scope by people, process, and technology like would exist in a project charter.
Weakness: Limited Scope Change Tracking
While it supports change orders from a cost perspective, it doesn’t have robust functionality to track scope changes specifically.
Stakeholder Management
Stakeholder management is among Kantata OX’s weakest areas. 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 stakeholder role.
Weakness: Limited Stakeholder Analysis
It lacks the ability to perform detailed stakeholder analysis, including identifying stakeholder groups, their needs, and influence.
Weakness: No Change Impact Assessment
There’s no functionality to document the impact of the project on different stakeholder groups and plan appropriate change management activities.
Kantata OX 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 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.
Kantata OX In Conclusion
Kantata OX should only be considered by large companies not using Salesforce. Large Salesforce customers should consider Kantata SX.
The 50 seat minimum and high cost put Kantata OX out of reach for small companies. The minimum annual license cost will be $35K.
You can also consider it for a PMO or project management solution if resource management and cost tracking are high priorities. However, its gaps in risk management and limited stakeholder management are going to be issues for most PMO applications.
I wanted to share my latest project which is relevant to both people searching for a project management tool and DIYers interested in building AI tools.
I decided this old dog needed to learn AI. Rather than take a course, I thought I’d learn by building my own custom AI chatbot from scratch. Sounds crazy, but I learned this is within reach of almost anyone with just a little bit of technical experience.
I loaded all my website’s existing reviews of project management tools into a vector database on the cloud. Then I built a WordPress plugin to handle the user interface for the chatbot. Here is the finished product: Project Management Tool Chatbot.
Here are the main things I learned:
Anyone can program using AI coding tools like Claude or ChatGPT.
Building a chatbot is incredibly cheap.
The chatbot can easily be designed to provide accurate responses without hallucinations.
The chatbot build consists of three main steps: prepping the data, loading the data into a vector database, building the user interface.
Anyone Can Program Using AI Coding Tools
I have some technical experience but I haven’t programmed in over twenty years, and never in the modern languages. I was able to code in PHP and javascript without any experience using the AI tool Claude.
This project required building about ten java scripts. First, scripts to scrape data from my website, transform it and then load it via an API to a vector database. Next, I had to build scripts as part of the WordPress plugin.
The amazing thing is that I was able to build all of this, and yet if you put a gun to my head I couldn’t write a single line of java script on my own. It is like I’ve built a symbiotic relationship with Claude. I learned how to guide and nudge it, but I didn’t have to learn any of the coding syntax.
Building a Chatbot is Cheap
My only expense so far has been a monthly subscription to the AI chatbot Claude for $20/month. I only needed this because I was bumping up against Claude’s daily volume limits. A smaller project could have been done with the free version of Claude.
I will incur costs for the Pinecone vector database and calling the OpenAI large language model (LLM). But these costs are pay as you go, and ridiculously cheap. Each time someone submits a question to my chatbot, I’ll be charged about two cents after I exceed the monthly allotment for the free plan. The chatbot will have to become incredibly popular for me to incur more than a few dollars a month in costs.
Chatbots Without Hallucinations
Everyone who has used ChatGPT has gotten a crazy answer that ChatGPT has simply made up. These are called hallucinations. But a custom chatbot (also known as a RAG model) doesn’t have these issues.
When a user submits a question to my chatbot my personal knowledgebase is searched on the vector database. Matching blocks of text (called context chunks) are returned with a percentage match score. I set how good a match is required to use a returned block of text. In testing my chatbot, about an 82% (B minus) is the sweet spot.
The blocks of text which clear the quality hurdled are then sent to the OpenAI LLM. However, the LLM is instructed to answer only using the provided text. It doesn’t tap its training data and it doesn’t hallucinate. The LLM is only used to summarize and format the response based on the text from my knowledgebase.
Building a Chatbot in Three Steps
The first step is to pull your data and transform it into JSON files. I had to build scripts to chop my blog posts and scoring spreadsheets into blocks of text and format them as JSON.
The second step is submitting the JSON files to a vector database. I chose to use a cloud-based database called Pinecone. I simply submitted the files to Pinecone and it ‘embedded’ the data. Embedding means it calculates a vector score for the chunk of text. But this isn’t the three-dimensional vectors you learned in high school. These vectors have 1,500 dimensions.
Step three was building a user interface for the chatbot. I’m a big fan of the WordPress opensource model, so I built a WordPress plugin which I could simply insert on any page of my website. The plugin manages a four-step process:
1. Collects the user prompt and submits it to Pinecone’s API to be embedded into a vector and matched.
2. Filters out low-quality text chunks returned by Pinecone. If there aren’t any high-quality text chunks, tells the user it can’t answer the question.
3. Submits the high-quality text chunks to the OpenAI API.
4. Displays the natural language response received by OpenAI.
Conclusion
I hope my experience will encourage you to build your own AI chatbots. I actually found it pretty fulfilling and a great learning opportunity. Next I’m going to build my first AI agent. I’ll keep you updated on how that goes.
If you have interest in the WordPress plugin I built for this project, I’m selling it for a nominal price of $30. You can find more details here.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Jira is a the market-standard Kanban board tool. I use it on all my projects. It is great for managing small Agile teams. However, it is just a Kanban board tool and is not a comprehensive project or program management tool.
Jira is reviewed against 200+ project management software requirements on a downloadablespreadsheet. Jira 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.
Evaluate Jira Quickly
Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Jira quickly and thoroughly.
I love Jira. I use it on all my projects and consider it the best Kanban board tool available. It is ideal for managing the user stories and releases for software development by small teams. If you are looking for a Kanban board, Jira should be on your short list.
While I use Jira for managing the user stories within the development team, I have to use other tools for project scheduling and cost management. Jira is just a Kanban board and sprint management tool. This is the reason for its low overall score when scored against all the project management processes.
Jira Pricing
Jira is free for the first 10 users, so you can get up and running immediately. Beyond 10 users it has three tiers of pricing:
Standard $7.16/user/month
Premium $12.48/user/month
Enterprise – Custom Pricing
Most companies are only going to need the Standard plan. You will only need to move up to Premium or Enterprise if you have a large program with multiple projects. You will find all the information about the differences between the plans here.
Integration Management
Jira has some limited integration management functionality. But it is not intended to be a program management coordination tool.
Strength: Project-specific access controls
Only team members added to the individual project can access the project. You can control each team member’s level of access: edit or read only. This is controlled at the individual project level, so a team member can have edit rights on one project but only read only rights on another project.
Strength: Issue management
I track project issues directly on the Kanban board. I start the title of the card/issue with “ISSUE: “. I also create a custom label for issues so that they can be filtered. Finally, related subtasks can be created for each issue. Having the issues directly on the working Kanban board is much more effective than having them squirrelled away in a separate issues log.
Weakness: Lack of status reporting
You’ll have to perform your project status reporting in another tool. While Jira, has many helpful reports for managing the sprint or release build, it doesn’t allow you to capture overall project health with supporting comments to share with management.
Weakness: Can’t add custom fields to projects
While Jira allows adding custom fields to issues/cards, it doesn’t allow adding custom fields to the project object. This would solve a lot of its integration management shortfalls. For example, you can’t add a custom status field.
Quality Management
Jira doesn’t score very well overall in Quality Management but that is a little misleading. While I need to use a dedicated testing tool for user acceptance test scripts and execution, I use Jira for all the unit and acceptance testing on my projects.
Strength: Can add acceptance criteria
I add a custom field to list the user story’s acceptance criteria as bullet points. When the unit tests or acceptance tests (within the team, not end user acceptance testing) are run, the results are captured as a comment noting which acceptance criteria passed and which failed. Screenshots of the test evidence are attached as files to the user story.
If any acceptance criteria fail, the user story is kicked back to the ‘Build’ column of the board and is re-assigned to the developer.
Weakness: Doesn’t support user acceptance testing
I don’t use Jira for formal user acceptance testing. This is because I need to be able to create formal test scripts, assign those scripts to specific testers and to be able to track the test results through multiple performances of the test. For this, I often use a tool like Quality Center.
Resource Management
Jira doesn’t have any resource management functionality other than controlling people’s access to the projects. It lacks basic functionality to view team member assignments and workload. It does have report to show total hours assigned to a person, however this is the absolute total and is not broken down by time units (i.e. day, week or month) so it is basically worthless.
Strength: Project-specific access controls
Only team members added to the individual project can access the project. You can control each team member’s level of access: edit or read only. This is controlled at the individual project level, so a team member can have edit rights on one project but only read only rights on another project.
Weakness: No resource allocation metrics
You cannot view a person’s total assignments or even assign a percentage of their time to a particular project.
Risk Management
You can add custom fields to the issues/cards to perform risk management. You can even create a unique ‘risk’ issue/card type. So with a little configuration you can manage your risks right on the Kanban board versus on a separate risk log.
Strength: Assign tasks to risks
If you create an issue/card for a risk, you can then create and assign subtasks to address the risk.
Schedule Management
Jira is a great Kanban board so scores well related to Kanban board functionality in Schedule Management, however, it is not a scheduling tool and fall short in this area.
Strength: Manage releases and sprints
Very few scheduling tools support the management of releases and sprints. Jira does this very well. You can assign user stories to a sprint and to a release. It is then very easy to track progress towards completion of the sprint or release.
Strength: Schedule user stories
Not all Kanban boards support assigning start or end dates to user stories. Even fewer support assigning labor hours. Jira supports all of this.
Weakness: Lacks most core scheduling functionality
As I’ve said, it is not a scheduling tool. While I use Jira to coordinate the team’s daily activities, I must use another tool like MS Project to manage the project’s schedule. I manage the user stories in JIRA, but then roll up to the sprint or deliverable/component level in the project schedule. The project schedule also contains all of the non-build tasks such as user acceptance testing, training and communication.
Here is a list of typical core scheduling functionality Jira lacks:
Task dependencies
Baselines
Milestones
Critical path
Gantt chart
Constraints
Effort-based scheduling
App Scoring Methodology
I’ve been evaluating all of the 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 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
Jira is my go to Kanban board tool for projects. However, it must be used in conjunction with other tools to manage the entire project management process. I highly recommend it as a Kanban board solution.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Trello is a Kanban board tool built by Atlassian who also built JIRA. It is a very functional Kanban board, but lacks any true project management functionality.
Trello is reviewed against 200+ project management software requirements on a downloadablespreadsheet. Trello 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.
Download Trello Scoring Spreadsheet
Click here to download the Trello Excel spreadsheet.
Trello is a nice Kanban board tool, but that is it. Which leaves me confused, because Trello and JIRA are both owned by Atlassian. JIRA is also a Kanban board but with more advanced functionality at an nominal increase in price ($2.48/month). I couldn’t find any functionality offered in Trello that isn’t offered in JIRA.
Unless, you simply can’t stomach the additional $2.48/month I don’t see any reason anyone should use Trello rather than JIRA. I cannot fathom why Atlassian wants to support both tools.
Like most tools, Trello lacks any dedicated change management functionality. Thus, there isn’t any functionality related to training or communication. You could track communication tasks on cards or checklists. It does have embedded AI functionality which could be used to draft communications.
Strength: AI Writing Assistant
There is an embedded AI writing assistant on the cards. You can invoke the AI writing assistance when writing the card description. It has standard commands such as:
Change tone
Summarize
Make shorter
Fix spelling & grammar
Etc.
Of course, you can do the same thing in an external AI tool and paste the results in the card.
Cost Management
Trello doesn’t have any cost management functionality.
Integration Management
Trello has very limited integration management functionality because it doesn’t have project or program data objects. You could define a board as a project, but you cannot create custom fields at the board level to track things like board status. You could create dedicated cards to track things like issues and change orders.
Weakness: No Project Status Reporting
There is no way to report on project status. There is a dashboard for boards but it only shows card counts in various categories.
Procurement Management
No procurement management functionality.
Quality Management
No quality management functionality other than ability to add custom fields to cards to record acceptance criteria and automated test numbers.
Resource Management
The only resource management functionality revolves around controlling access to the project. If you define a board as a project, only people you invite can access the board. When you invite people to the board you can give them edit or read only rights.
Risk Management
While Trello doesn’t have any dedicated risk management functionality you could create a card for each risk and categorize them as risks by using either a list or label. You wouldn’t be able to track probability or impact of the risks because these would be risk-specific custom fields, and Trello applies custom fields to all cards on the board.
Schedule Management
Trello is not a scheduling tool, it is basically just a Kanban board. There are some slight scheduling aspects in that you can assign a start and due date to a task (i.e. card), however there isn’t any scheduling functionality to schedule tasks based on predecessors or available labor.
Strength: Kanban Board
The Kanban board has a nice graphical interface and is easy to use.
Strength: Multiple Views
You can view the cards/tasks on the board in multiple views, such as: timeline and calendar.
Strength: Checklists
You can add a detailed checklist to a task/card. The checklist items can be assigned resources and dates.
Weakness: No Real Scheduling Functionality
Does not support:
Predecessors/dependencies
Constraints
Effort-based scheduling
Duration-based scheduling
Critical path
Baselines
Weakness: No Real Labor Tracking
You could create some custom fields on the tasks/cards to track planned and actual labor hours. However, there aren’t any reports to easily report on planned and actual labor at a project level.
Scope Management
There isn’t any dedicated scope management functionality but you could create dedicated cards to record the project scope.
Stakeholder Management
Trello doesn’t have any dedicated stakeholder management functionality. You could create individual cards on the board to record things like: a list of stakeholders and the steering committee.
Trello 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 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
If you are looking for a good Kanban board tool, you should evaluate JIRA also offered by Atlassian. I would only consider Trello if you don’t need JIRA’s added functionality at an additional $2.48/user/month.
JIRA should absolutely be your choice if you are doing Agile software development. If instead, you are a small business doing simple projects then you could save a little bit of money using Trello.
You could also save some money by integrating JIRA and Trello. Use JIRA for your software development, but use Trello for everything else. Atlassian offers an integration between the two.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
PK4 TimeTracker is good choice for setting up a timesheet process in Salesforce. Besides capturing work time it will also capture PTO, and expenses. Invoices can be generated using rates specific to a customer or project.
However, there are several gaps that do not make it a good choice for a professional services firm that also requires full-featured schedule, cost and resource management functionality.
In this post, PK4 TimeTracker is reviewed against 200+ standard project management software requirements on a downloadablespreadsheet. PK4 TimeTracker 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.
Download PK4 TimeTracker Evaluation Spreadsheet
If you are in the process of selecting a time tracking tool, save a lot of time in evaluating PK4 TimeTracker. This is a RFP-level fit/gap analysis of PK4 TimeTracker. The spreadsheet can also be used to perform a side-by-side comparison of other tools.
PK4 TimeTracker actually consists of four apps: web app, mobile app, browser extension and a Salesforce app. This review is focused on the Salesforce app for tracking time and managing projects within Salesforce. Within the app there are four add-ons which relate to project management: project management, PTO, invoicing and expenses. This review includes all of these add-ons.
App Pricing
PK4 TimeTracker has different seat license pricing per app, with a minimum package price of $1,500/year:
Salesforce Users – $18/user/month
Salesforce Admin – $30/user/month
Web User – $10/user/month
Mobile/Chrome/Jira/Slack – $7/user/month
The add-ons are an additional cost:
Project Management – $15/user/month
Invoicing – $30/user/month
Expense Management – $2/user/month
PTO Management – $3/user/month
Project Management and Invoicing licenses are only required for the people actually working in those add-ons so project managers and accounts receivable. Also note that Salesforce users get access the other apps: web, mobile, chrome, etc. So the total cost for the functionality reviewed here for a Salesforce user would be:
Like most tools, other than being able to track planned communications in the schedule and using Salesforce Chat, PK4 doesn’t have any significant communication management functionality.
Cost Management
PK4 has strong functionality around recording people’s time and generating invoices. However, it doesn’t have functionality for planning the project budget and tracking against the budget.
Strength: Time Entry and Approval
This is PK4’s primary functionality. Users are able to enter their time and expenses which are then routed to their manager for approval.
Strength: Invoicing
Projects can be invoiced directly in PK4 using an add-on. The invoicing functionality includes the ability to track payments against the invoice. The invoices can bill customers for both time and expenses.
Strength: Project-Specific Rates
PK4 creates an assignment record which is a combination of a resource record and project. This allows you to capture a specific billing rate for a specific resource on a specific project. This ensures you are invoicing the customer at the contractually agreed rate.
Weakness: Managing the Project Budget
PK4 does not have functionality for creating a project budget and then tracking actual hours and expenses against the budget. This would be a major gap for a professional services firm.
Weakness: Only Hourly Rates
It only supports hourly rates. It does not support daily or weekly rates which are popular with professional services firms.
Integration Management
PK4 TimeTracker doesn’t have any integration management functionality worth mentioning. You could create fairly easily create status reporting functionality by adding custom fields to the project object.
Weakness: Lacks Status Reporting
There isn’t any functionality out of the box for reporting project status. However, you could create some of this functionality by adding custom fields to the project object.
Weakness: No Issues Log
PK4 doesn’t have an issues log or the ability to create change orders.
Weakness: Lacks Project Access Controls
This would only become an issue for customers that used the project management add-on, but PK4 doesn’t appear to have any project access controls. This means that anyone with the project management add-on license could view/edit any project.
Procurement Management
Like most project management tools, PK4 TimeTracker doesn’t have any procurement management functionality.
Quality Management
Like most project management tools, PK4 TimeTracker doesn’t have any quality management functionality.
Resource Management
I would say that PK4 has a minimum foundational level of resource management. The tasks are assigned resources and hours and then resource allocations can be viewed by day/week/month. The resource allocation view isn’t nearly as good as some of the advanced PSA tools.
Strength: Manages PTO
I’ve found that very few of the project management and resource management tools manage PTO (vacation, sick days, etc.). PK4 allows you to budget the PTO for a resource and then track their PTO consumption against that budget.
Weakness: Can’t Plan by Skill or Role
The biggest gap in PK4’s resource management is the ability to plan resources by skill or role. Most resource management tools allow the creation of a need by skill/role and then matching that against the availability of people with that skill/role. PK4 doesn’t have the ability to define or assign skills/roles to a person. It also doesn’t have the ability to generate resource need requests.
Weakness: Can’t Allocate a Person by Percentage
All of PK4’s resource management is performed at the task level. A level of effort is assigned to the task and that gets allocated to the resource. In the early planning stages of a project, I find it much more practical to simply assign a person at a percent of their time to a project.
Weakness: Can’t Soft Allocate Resources
It is useful to resource managers to be able to soft allocate resources. This means allocating a resource to a future project, but knowing whether the assignment has actually been confirmed or begun. This gives them flexibility to re-assign soft-allocated resources if necessary.
Weakness: Tasks Not Pre-Populated on Timesheet
Many timesheet tools pre-populate a resource’s assigned tasks to their timesheet so they simply have to enter the time worked. This makes it more likely a resource does not forget to record time against a task.
Risk Management
No risk management functionality.
Schedule Management
I would classify PK4’s project management add-on as more of a task list than a scheduling tool. It lacks most of the functionality that a professional scheduler would expect.
Strength: Can View All Assigned Tasks
PK4 users can view all their assigned tasks across all projects in one central location.
Weakness: Tasks Aren’t Scheduled or Summarized
When creating tasks in the Gantt chart I noticed two strange behaviors:
When you assign a dependency to a task, it doesn’t affect the start date of the task. You create the linkage but the downstream tasks are not rescheduled to comply with the dependency.
When you indent a task to create a child task, the parent task does not become a summary task. It is unchanged. This means you can have a child task with a longer duration than the parent.
Weakness: No Baselines
You cannot take a baseline of the schedule and then measure performance against the baseline.
Scope Management
No scope management functionality.
Stakeholder Management
No stakeholder management functionality.
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 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
Unsurprisingly, PK4 TimeTracker’s strength lies in timesheet reporting. It should be considered by any company needing basic timesheet reporting. There are four pieces of functionality which differentiate it from many of the other Salesforce time tracking tools:
Can track expenses.
Can track PTO.
Can bill based upon project-specific rates for a person.
Generates invoices.
Professional services firms will find it lacks the advanced resource management they need, and should look to dedicated PSA tools (Kantata, Certinia, etc.). Professional schedulers and project managers will find the project management add-on insufficient to schedule anything but the simplest projects.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Project EMC2 is a free project management tool available on the Microsoft App Store. It is geared towards managing software projects and contains good task, requirement, risk and issues management functionality. It is available as a desktop or cloud-based solution.
Project EMC2 is reviewed against 200+ project management software requirements on a downloadablespreadsheet. Project EMC2 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.
Download Project EMC2 Scoring Spreadsheet
Click here to download the Project EMC2 Excel spreadsheet.
Project EMC2 would be a great option for a nonprofit or small business wanting to organize their IT and business improvement projects. It has a good task management tool. The tasks are supported by risk and issue management functionality. I really like that you can add supporting action items to all the objects like: project, risks, issues, tasks, etc.
Project EMC2 uses a waterfall approach and is intended for small to medium-sized companies with projects focused on human resource, business or system changes (i.e. implementations, reorganizations and process improvements).
It is not intended for large organizations with more than 100 projects or that have the following requirements:
Complex financial tracking
Complex performance requirements
Inventory control and scheduling
Automation and integration with enterprise systems
Automated workflows
Real-time interfaces
It also would not be a good option for construction projects or professional service firms. The scheduling tool does not have the advanced functionality required for a complex construction project. It lacks the cost and resource management functionality a professional service firm would require.
Project EMC2 Pricing
The desktop app is completely free! There is a small hosting fee for the optional cloud-based services. The cloud-based services require a user’s profile to be verified for access to project files, and provide in-use warnings if another user is editing the file.
Scoring Methodology
I’ve been evaluating 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 my own project management app: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but you can download the Excel spreadsheet used for the evaluation 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 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.
Communications Management
Project EMC2’s communications management functionality is focused on generating and distributing status reports to a list of stakeholders. In fact, the information tabs are designed to facilitate status meetings. The project manager just visits each tab from left to right and ensures the review checklist on each tab is accomplished.
Cost Management
It does not have any cost management functionality. So you won’t be able to control project costs or generate invoices for professional services.
Integration Management
Project EMC2’s integration management functionality is primarily limited to documenting decisions, issues and status reports.
Strength: Decisions and Issues
It has good functionality for documenting project decisions and issues. I especially like that you can assign action items to the decisions and issues.
Weakness: Project Access Rights
The options to control project access are limited to if a project team member can see all project tasks or just their own. However, you cannot control if the user has read/write access. It is sometimes useful to give project sponsors or other managers read only access to the entire project.
Weakness: Summary Project Status
Project EMC2 lacks project stoplights for status that are found on most other tools. This allows you summarize the project’s status as either green, yellow or red. This is helpful for a manager perusing the status of multiple projects.
Procurement Management
It doesn’t have any procurement management functionality, which is key functionality for construction projects.
Quality Management
Project EMC2 has strong and unique acceptance criteria functionality. However, Project EMC2 is not a test management tool. You’ll have to supplement it with other tools to document and track test scripts.
Strength: Acceptance Criteria
Project EMC2 supports documenting a list of individual acceptance criteria per requirement. You can even mark when an individual acceptance criteria has been met. This is a rare feature among project management tools.
Resource Management
It lacks the detailed resource assignment functionality a professional services firm requires to manage people’s time on multiple projects. It does have some basic functionality to assign people and stakeholders to the project.
Risk Management
Project EMC2 gets almost a perfect score in risk management! The only thing it lacks is the ability to create a detailed quantitative risk matrix. But to be honest, I’ve never found detailed quantitative risk matrices very useful.
Strength: Action Items Associated to Risks
Even some of the most popular project management tools don’t support the creation of action items for individual risks. Project EMC2 allows you to create specific mitigation steps or follow up tasks for each risk.
Schedule Management
I would classify Project EMC2 as a task management tool rather than a scheduling tool. It does support some advanced scheduling like dependencies in a limited functionality. However, it doesn’t have the breadth of scheduling features you would find in a Microsoft Project or some of the other popular cloud-based project management tools.
Strength: Assign Tasks to External Users
Since it is free, it would be ideal for a project coordinating tasks with multiple parties. You can assign tasks to people outside your organization at no additional cost. The feature to limit visibility to a person’s own task assignments would allow you to limit an external users view of the entire project, in case some tasks are sensitive.
Strength: Focus Filter Tool
Project EMC2 has a unique focus filter that can be applied to task and other lists to declutter the view. It hides items that are complete, canceled, inactive, far-future dated, etc. in a single click.
Weakness: Scheduling Functionality Gaps
Here is a list of the scheduling functionality it lacks, which are fairly common among scheduling tools. These are usually only required for complex or large projects, so they may not be a issue for you.
Doesn’t support all dependency types. Only supports Finish/Start dependencies.
Doesn’t support lag between dependencies.
Limited work breakdown structure. You are limited to a four levels of the schedule: phase, goal, activity, action item.
Doesn’t support effort-based scheduling. Meaning, the duration of the task doesn’t vary based on the number of people assigned to the task.
Weakness: Agile Functionality Gaps
While you can write the Project EMC2 requirements as user stories with acceptance criteria, it lacks functionality that most Agile/Scrum projects would expect.
No Kanban board
No backlog
No epics or themes
No sprints/releases
Scope Management
It doesn’t have any scope management functionality.
Stakeholder Management
Project EMC2 is unique in by offering a stakeholder engagement matrix. Most project management tools don’t offer any stakeholder or change management functionality.
Strength: Engagement Matrix
When you assign stakeholders to the project you can assign them a value from an engagement matrix. The engagement matrix determines how engaged the stakeholder should be on the project based on their influence and their interest in the project.
In Conclusion
If you are a looking for an inexpensive IT project tool, you should consider Project EMC2. You should especially consider it if its three key differentiators are important to you:
Ability to assign action items and mitigation steps to risks.
Ability to list and track detailed acceptance criteria for requirements.
Ability to assign action items to all project data objects.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Scrum master, get over yourself. That goes for project managers too. You are the least important person on the project, so act accordingly.
I know of what I speak. I’ve been running IT and consulting projects for over 30 years and definitely have been full of myself during my career. Eventually, I realized that while I was “in charge” as a project manager and getting paid high fees as a consultant, I was actually the least valuable and most replaceable person on the project.
Realize Your Lack of Value
I once had a young scrum master working with me on a large IT project. This scrum master was constantly complaining about “IT” not delivering code quickly enough and there being too many bugs. I finally sat them down and made two points:
There is no “IT” and “Business” or us versus them. This is one team, all focused on a common goal. Everyone on a football team either wins or loses together. If the project fails, management isn’t going to sift through the rubble to figure out what went wrong. They are going to simply fire the coach.
And on this football team, you’re the water boy. It is a software project. The only time value is being added is when developer’s fingers are on their keyboards writing code. Value isn’t being added in standups or sprint planning meetings.
Let’s dive into the concept of “value-added” a bit more. The concept of value-added tasks comes from lean manufacturing, and means those tasks that add value to your customers. On a software project the end customers are the users/purchasers of the software. Imagine you gave a customer the choice of buying two identical software packages: Expensive and Cheap. Expensive Software is twice the cost of Cheap Software but had a great scrum master, whereas Cheap Software had a lousy scrum master. Would the customer pay more for Expensive Software? Of course not.
Therefore, the scrum master and their tasks are non-value added. The Japanese lean manufacturing experts would consider them waste, to be studied and eliminated where possible. Hear that scrum master? You’re waste.
Add Value Not Anger
Now before you go crying into your Starbucks latte, lucky for you there is a second customer on software projects. That customer is the sponsor or company management paying for the project. They are willing to pay for a scrum master if they can add value by building the software better, faster and cheaper. Does the sponsor care how well the sprint planning meeting is run? Of course not, the sponsor only cares about results.
So how do you build software better, faster and cheaper? Well, you don’t do it by being full of yourself and being an angry task master. I was at an Agile conference presentation with two young scrum masters sitting in front of me. During the Q&A, one of them raised their hand and asked “If the developers on my project keep missing deadlines or don’t complete all the user stories in a sprint, how do I punish them?”
The speaker was stunned. The speaker eventually answered that the scrum master’s role wasn’t to punish the developers, but to address the process issues that were affecting the developer’s efficiency. The young scrum masters were baffled, they simply asked the question again. They didn’t get it. Don’t be like them.
Can you imagine being a developer with twenty years of experience being called lazy or incompetent by a twenty-something scrum master that has never written a single line of code? Trying to explain the technical issues causing the delay is probably a complete waste of time because the scrum master won’t understand them. If you were the developer, would you be motivated to build software better, faster and cheaper or would you be angry?
Be Supportive
If your job is dependent upon building software better, faster and cheaper you’d better treat the only people actually building the software pretty well. Your role is to support them, not to whip them. And usually, supporting them involves rolling up your sleeves and taking the grunt work off their plate so they can focus on coding. This usually isn’t the type of work a glamorous full-of-themselves scrum master is willing to do. It requires some humility and a willingness to learn. Here are some examples:
Help test. Testing is the best way for you to learn the software and to understand technical issues. You’ll also start to learn when a developer truly did screw up on something simple, like a null exception error. Not so you can punish the developer, but so that you can understand if they need additional training.
Take on simple administrative tasks. Developers can end up spending a lot of time on administrative tasks, especially to support testing. Many of these are easily learned tasks, that don’t matter if you screw up the first time because it is the test environment.
Add testers to the test environment
Upload test data to the test environment
Edit JSON files or other files for testing
Review user stories. Review user stories for quality. Are they complete and easy to understand? Are the acceptance criteria detailed and complete?
Off load reporting and configuration. Can you or someone else take on configuration tasks so the developers can actually code? Can someone else write reports?
Try to code. Get on the Internet and take some classes on coding using a simple language like HTML or Python. Build a little program/web page and spend hours de-bugging it because it isn’t working. This will give you some appreciation of what developers go through.
Buy them lunch. Don’t buy them lunch so that they can eat and work at their desk. Buy them lunch to be nice.
Acknowledge You’re Replaceable
Eventually, you’ll also realize that no one is irreplaceable on a project. As I mentioned earlier, if the project goes south the easiest thing for management to do is to try assigning a new scrum master. If you were a manager trying to get onto the golf course, would you want to stay late to listen to a scrum master explain all the issues that caused the project to fail? No, you’re just going to replace them and hope the new scrum master can fix the issues.
I can speak from experience because I’ve been replaced twice in my career. The first time, I was caught up in a layoff at a large consulting firm. I’ll never forget me marching into my exit interview with a well organized folder of my ongoing activities like sales leads and presentations. The partner didn’t even look at the list. There wasn’t anyone left to pick up my work even if it mattered. I was going to walk out of that office and no one was even going to notice I was gone.
The second time, I was having difficulties getting the product owner and a contractor to stick to the schedule. I made the mistake of escalating the issue rather than dealing with it myself. In the end, they didn’t replace the product owner or contractor, they replaced me for not being able to run my project smoothly. The project ran fine without me.
Over and Out
So get over yourself and become a better scrum master. Be humble: you don’t add value directly to the software and you’re not irreplaceable. Be supportive: do whatever it takes to make the team productive.
If you get over yourself, you’ll get your project over the finish line. And, the project sponsors will be over the moon.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
The Basecamp project management tool is a low-cost, beautifully-designed, cloud-based, to-do list and Kanban board. It would be ideal for a small IT development team. However, it is lacking the project management functionality required for a large or complex project.
This post reviews Basecamp against 200+ project management software requirements on a downloadablespreadsheet. Basecamp 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 relevant processes.
Basecamp is a niche project management tool. It would be ideal for a small IT development team, or other type of creative team. Its greatest strengths are:
Low cost. It uses an affordable site license.
Beautiful and simplistic user interface. The design is very clean and inuitive.
Basecamp’s greatest weaknesses are:
Very limited customization options. You cannot build dashboards or reports. You cannot add custom fields to existing objects.
Lacks a Gantt chart scheduling tool.
While it would be ideal for a small Agile team, it lacks standard Agile/Scrum management functionality, such as, story points, burndown charts, sprint planning, epics, etc.
Basecamp Pricing
Basecamp’s pricing is great! While most competing products use a user license model, Basecamp uses a single site license model. This means your costs don’t grow as your business grows, and you don’t have to manage costs by limiting people’s access to the projects.
The site license is $299 or $349/month depending upon whether you pay annually or monthly. That is a max cost of $3,588 to $4,188/year.
For the smallest companies (less than 20 users), there is an option to pay $15/user/month for employees with free guests.
App Scoring Methodology
I’ve been evaluating 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 my own project management app: Project Lifecycle Pro. I’m doing my best to give a unbiased review, but you can download the Excel spreadsheet used for the evaluation 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 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.
Download Basecamp Scoring Spreadsheet
Click here to download the Basecamp Excel spreadsheet with 200+ project management requirements.
Basecamp is not a training management system or intended to support change management so it has limited functionality in this area. However, it does have a chat and message board.
Strength: Message Board Options
When you post a message to the project’s message board you have several advanced options:
Which project members can view the message: all members, specific people, anyone with visibility to the project, or the client.
Messages can be scheduled.
Comments can be closed.
Strength: Client Access to Chats
You can select whether or not your clients will have access to the project chat.
Cost Management
Basecamp doesn’t have any cost management functionality. However, it does integrate with a large library of tools which provide timesheet and invoicing functionality. Basecamp Integrations
Integration Management
Basecamp is missing most of the integration management functionality you would need for managing a large project or program. However, Basecamp is intended for small projects and teams.
Strength: Client Project Access
It has very advanced features to customize the client access to the project information. You can control overall access to the project, as well as, access to the individual tools (schedule, messages, cards, etc.) and in some cases access to the individual records within the tools.
Weakness: No Issue Record Type
It doesn’t have an ‘issue’ record type in order to track and assign tasks related to a project issue. You could work around this by placing “ISSUE:” at the beginning of the card or to-do name. Or you could create card tables specifically for issues. However, this is less than ideal when trying to provide visibility to open issues for project team members and the project sponsor.
Weakness: Doesn’t Group Projects into Programs or Portfolios
This makes sense as it is intended for small teams, but this would be a major weakness for a large organization trying to run a large initiative.
Procurement Management
No procurement management functionality.
Quality Management
No quality management functionality, except the possible ability to use cards as user stories and use card steps to capture acceptance criteria.
Resource Management
No resource management functionality other than defining the team members and controlling their access to the project. No way to allocate people’s time across multiple projects or to measure utilization. Professional services firms would find this to be a major gap.
Risk Management
Basecamp doesn’t have any specific risk management functionality. However, you could work around this to some degree by adding “RISK” to the names of to-dos or cards. But you still wouldn’t be able to capture the risk probability or impact. It would also be difficult to report risks to the team, stakeholders or sponsor.
Schedule Management
Basecamp’s scheduling capabilities seemed geared towards a small Agile IT development team. It has a nice Kanban board. Cards and to-dos can also be assigned an owner and a due date. However, this is about the extent of its scheduling capabilities. It doesn’t have a Gantt chart or allow for scheduling dependencies.
Strength: Kanban Board
The Kanban board is well designed and very easy to customize the columns to fit your development process.
Strength: External Resources
Because Basecamp uses a single site license and is cloud-based, external resources can be treated just like internal resources on the project. You just invite the external resource to the project with an email, they setup their password and they now have access.
Weakness: No Gantt Chart or Dependencies
The lack of a Gantt chart and the ability to create dependencies between tasks is going to make Basecamp a bad choice for complex or standardized projects. The main issue is the lack of the ability to reschedule easily. If a date slides on a complex project, you need the remaining tasks to be reschedule automatically based on dependencies. If you use a standard project template, you want to update the start date and automatically update the task dates.
Weakness: Can’t Plan or Track Task Effort
There isn’t any capability to assign labor estimates against tasks to support resource management, or to support time and expense budgeting.
Weakness: Missing Agile Management Tools
While Basecamp appears ideal for a small Agile IT development team, it lacks many of the tools used to manage Agile teams. You can’t assign story points to cards. It doesn’t have a burndown report. You can’t assign
You can’t assign story points to cards.
No burndown report.
You can’t assign epics or themes to cards.
Scope Management
No scope management functionality.
Stakeholder Management
No stakeholder management or change management functionality.
In Conclusion
If you have small creative teams looking for a simple collaboration tool, Basecamp is a good fit given its low cost and excellent design. If you have large or complex projects, or if you have a strict Agile methodology for IT development you should consider other tools.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
This Microsoft Project review is for the web version: Microsoft’s Project For The Web (PFTW). MS Project for the Web is a very light cloud-based project scheduling tool. It should only be considered by the most cash-strapped businesses already using Microsoft products. This is because, it has very limited collaboration, resource and cost management functionality and only costs slightly less than implementing the integrated Microsoft Project Pro and Project Online solution provided in Plan 3. Detailed Review of Microsoft Project Online and Pro.
If you aren’t currently a Microsoft customer and only need a simple project management tool, you should consider the other cloud-based tools which are sprouting up like mushrooms after a spring rain. Comparison of Project Management Tools.
Still reading? In the rest of this Microsoft Project review, Microsoft Project For The Web is reviewed against 200+ project management software requirements on a downloadablespreadsheet. The software 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.
Evaluate Microsoft Project for the Web Quickly
Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Microsoft Project for the Web quickly and thoroughly.
The only benefit of PFTW relative to Microsoft Project Pro and Online, is that PFTW would be much easier to setup. However, it lacks any reporting or collaboration functionality so you’d probably have to setup the reporting in PowerBI and the collaboration on a SharePoint site. However, PFTW doesn’t integrate with SharePoint like Project Online and PFTW projects are completely separate from Project Online. It would make much more sense to create your projects on Project Online since it is included in the Plan 1 license package with PFTW. I’m left scratching my head as to why Microsoft even built PFTW?
To simplify, if you want a simple Microsoft project management solution buy the Plan 1 license but build your projects on Project Online and ignore PFTW. This will give you the option in the future to purchase Plan 3 licenses for only your project managers in the future so they can use Project Pro for detailed scheduling and then synch the schedules with Project Online.
Pricing
PFTW is included in all the Microsoft Project license plans. The cheapest plan (Plan 1) is $10/month. It includes PFTW and Project Online Essentials. However, these two tools aren’t integrated. Meaning, if you create a project on PFTW it will not appear in Project Online and you can’t use Project Online’s collaboration functionality for the project.
You will need a license for each project manager creating project schedules and either a Microsoft 365 ($6 – $22/user/month) or Plan 1 license for everyone assigned tasks or needing to view the project. The reporting is very limited in PFTW so you would probably also need Power BI ($10 – $20/user/month) to perform any project reporting.
If it were me, I’d purchase Project Plan 3 licenses for my project managers and admins at $30/user/month. Projects would be built on Project Pro and synched to Project Online. Plus I’d also purchase PowerBI licenses for them ($10 – $20/user/month). This gives them a suite of products and functionality for a project management solution:
Power Automate – To automate project processes.
SharePoint – To create project sites.
Project Pro – To create detailed and advanced project schedules.
Resource Management – To manage company resources across projects.
PowerBI – Create advanced project reports and dashboards.
I’d then purchase Microsoft 365 licenses for everyone else who will be assigned tasks or needs visibility to the projects. You’d only be spending an additional $20/user/month for a handful of project managers and admins, yet gain so much more functionality. Microsoft Project Pricing
Cost Management
PFTW doesn’t have any native cost management functionality. However, you could add custom fields to the tasks to captured planned and actual costs at a task level and then rollup the totals to the project.
Integration Management
All the integration/collaboration functionality resides in Project Online, PFTW lacks any real integration functionality. It does have one small feature where you can set goals and associate tasks to the goals.
The main gap in integration management is that PFTW doesn’t allow the creation of project-level custom fields. Therefore, you can’t capture project health, status, description, etc.
Resource Management
PFTW doesn’t have any resource management functionality other than controlling access to the project. All the resource management functionality resides in Project Online.
Risk Management
You cannot create a risk log in PFTW. The risk log functionality resides on SharePoint project sites which are only integrated with Project Online.
Schedule Management
Schedule management is the only bright spot for PFTW. It is a decent cloud-based scheduling tool. However, it does have some major functionality gaps when compared to a real scheduling tool like Project Pro.
Strength: Full Dependency Functionality
PFTW supports all dependency types (Finish/Start, Finish/Finish, etc.) and lag/lead added to a dependency. It also supports multiple dependencies on a single task. Many cloud-based scheduling tools only support finish/start dependencies, and some don’t support lag/lead.
Strength: Supports Agile Projects
PFTW has a good Kanban board and you can assign tasks to a sprint. This supports creating a product backlog on the Kanban board. You can also add custom fields to the task for agile data like: story points and epics.
Weakness: Doesn’t Reschedule
I created a simple project plan with tasks linked by dependencies. I was shocked when I moved the finish of the first task to complete earlier and the downstream task’s start dates didn’t move up in the schedule.
Weakness: No Effort-Based Scheduling
You can define the effort for a task, but PFTW will not use this for scheduling purposes like Project Pro. PFTW only uses fixed duration scheduling. For example, if I assign a 40 hour task to one person the duration should be 5 days. However, if I assign a second person to the task the duration should drop to 2.5 days. PFTW doesn’t support this type of scheduling, the duration will not change.
Weakness: No Constraints
PFTW doesn’t support constraints like: Must Finish On, or Must Start On.
Microsoft Project Review Methodology
I installed the free trial of Plan 3 and then created projects in Project Pro, Project Online and PFTW to understand the differences in functionality.
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
There isn’t much left to say. As I stated earlier, I’m baffled as to why Microsoft even built Project For The Web when they already had Project Online and Project Pro. If you have to save $20/user/month on project management licenses for your project managers, then maybe it is time to clear out the bank account and head for Brazil. Please let me know if you enjoyed this Microsoft Project review in the comments.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Microsoft Project review of the Plan 3 version. MS Project Plan 3 is an integrated solution combining MS Project Online (cloud) and MS Project Professional (desktop app). It has one foot in the clouds for collaboration and one foot firmly on the mountaintop of a professional scheduling desktop app. It is a powerful combination for roping in those difficult projects.
Microsoft Project review of Plan 3 is based upon 200+ project management software requirements on a downloadablespreadsheet. MS Project 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.
Evaluate MS Project Plan 3 Quickly
Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Leankor quickly and thoroughly.
Microsoft Project Plan 3 is the default project management tool for professional project managers. The exceptions are:
Large and complex construction projects, such as, construction of a nuclear power plant. Then the default is Primavera.
Professional services firm’s projects. In most cases, these firms should consider a comprehensive PSA tool, such as, Kantata, Certinia or Microsoft Dynamics 365 Project Operations.
Note the key condition: this is a tool for professional project managers. It is not intuitive and is not a quickly implemented cloud-based tool like Asana, Wrike or Smartsheets. It will require a Microsoft administrator to set it up and maintain it. Therefore, you should consider other tools if:
You are just looking for a simple task list tool and don’t need powerful scheduling functionality.
You don’t have professional project managers who know Project Professional. Or you don’t want to have to train your staff on Project Professional.
You are not currently a Microsoft customer. The solution is designed to integrate with other Microsoft tools, such as, SharePoint and Teams. Therefore, it won’t make much sense if you are using other office or collaboration tools.
Microsoft has several project management offerings. This is a review of the integrated Project Online and Project Professional solutions sold as Microsoft Project Plan 3. Plan 3 includes three solutions: Project for the Web, Online and Professional. I did not include Project for the Web in this review because it is an independent tool that does not integrate with Online or Professional, so I will review it in a separate post. The other offerings which I hope to review in the future are:
Microsoft Planner Plan 1 – A simple task list tool. Basically, Project Online without Project Professional.
Microsoft Project Plan 5 – Plan 3 with added functionality:
Advanced resource management
Submission and management of project ideas
Dynamics 365 Project Operations – Similar to a professional services automation (PSA) tool that integrates project management with sales, marketing and finance functions.
On-Premise Project Solutions (non-cloud)
Project Standard 2021 – Basically a lite version of Project Professional without resource management or the ability to synch with other tools for collaboration.
Project Professional 2021 – Basically, the same desktop scheduler provided in Project Plan 3 but with a perpetual license rather than a subscription.
Project Server – Basically, Plan 5 but without timesheet functionality.
I’ve split the scoring into three results. The ‘combined’ score evaluates an integration solution of Project Online and Project Professional. The scores for Project Online and Project Professional provide guidance on the functionality available if you only implement one of the solutions.
Microsoft Project Plan 3 Pricing
MS Project Plan 3 is $30/month. You will need a license for each project manager creating project schedules and every resource manager responsible for assigning people to projects. This license also includes Power Automate for building workflows and SharePoint for creating project sites.
In order to collaborate on projects you will also need the following licenses:
To view projects and to view/edit tasks users will need either a Microsoft 365 ($6 – $22/user/month depending upon the plan) or Microsoft Project Plan 1 license ($10/user/month).
The reporting is limited in Plan 3 so you probably will need Power BI license for users that will create reports ($10 – $20/user/month depending upon the plan).
So a company with one project manager (also report writer), one Salesforce administrator and 20 project resources would have an annual spend of about $3,000. Microsoft Project Pricing.
Communications Management
Microsoft Project is primarily a scheduling and resource management tool. Like most project management tools it doesn’t have any functionality targeting change management or communication.
Cost Management
Project has good functionality for budgeting costs and tracking actuals. However, it lacks invoicing functionality a professional services firm would require. For invoicing functionality, research Dynamics 365 Project Operations.
Strength: Report Budget Manually or as Rollup
You can set a manual budget value early in the project when plans are not finalized. You can then later rollup the costs from the individual tasks when the project is fully planned.
Strength: Overtime Rates
Project is one of the rare tools that supports overtime rates for resources.
Weakness: No Invoicing Functionality
While you can define a resource’s price and cost per hour and then total the planned and actual cost, you cannot actually create and track invoices. You’ll have to feed the project data to another invoicing system.
Weakness: No Project-Specific Rate Cards
Rate cards created for a resource are enterprise wide. You can create five different rate cards for a resource, however you can’t create rate cards specific to an individual project.
Integration Management
I’m very underwhelmed with Project’s reporting and dashboards. I believe the intent is to build the reports and dashboards in Power BI, but that is a separate license.
It does have very good project issue and risk management functionality. However, be aware that all of this functionality is contained on SharePoint so you need to synch Project Online to a SharePoint project site.
Strength: Issues and Risks
You can log issue and risk details. You can also assign tasks to the issues or risks. However, all of this functionality resides in the SharePoint project site as add-on apps. The SharePoint project site is synched to Project Online.
Weakness: Reporting and Dashboards
While the reporting in Project Professional for the project manager’s use is excellent, the collaborative reporting you would need in a PMO or for management is lacking. You’ll need to build these capabilities in Power BI and post the reports or links on the SharePoint project site which is synched to Project Online.
Procurement Management
No functionality to speak of other than planning and tracking material/labor costs in Project Professional.
Quality Management
No testing functionality.
Resource Management
Project Online allows the creation of enterprise resources that are shared across projects. The resources are scheduled within Project Professional. The enterprise resource utilization and demand can be tracked across all the projects.
Strength: Submit Resource Requests
Project managers can submit resource needs to a resource manager to fill.
Weakness: Resource Planning by Skill
Project lacks good functionality to plan resource needs by skill. You will have to configure project to support skill planning, and then it won’t be as good as some of the dedicated PSA tools.
Weakness: Resource Allocation Timeline
The basic functionality is available to view a resource’s allocation and availability on a timeline. However, the functionality is lacking when compared to the dedicated PSA tools.
Risk Management
All the risk management functionality you should require. Be aware that all of this functionality resides in a SharePoint addon app, on the SharePoint project site that is synch to the Project Online project.
Schedule Management
All the great project scheduling functionality resides in Project Professional. You can build schedules in Project Online but the functionality is limited and the user interface is clumsy.
Project Professional has all the scheduling functionality anyone should ever need.
Strength: Full Dependency and Constraints
Project Professional supports all dependency types (finish/start, finish/finish, etc.) and constraints (Must Start On, Must Finish On, etc.). Very few of the cloud-based scheduling and PSA tools support all dependency types. Even fewer support all the constraint types.
Strength: Effort-Based Scheduling and Load Leveling
Almost none of the cloud-based and PSA tools support effort-based scheduling. This means the end date is determined by the amount of work required and the number of resources assigned. For example, if you have 40 hours of work and assign one person, it will take 5 days. If you assign two people it will take 2.5 days.
Load leveling is an automated scheduling tool where you tell Project to schedule all the tasks so resources are not over allocated. For example, if you have a fixed duration task with 40 hours of work and have a single resource assigned who is also assigned another 40 hour task at the same time, you’ll have an over allocation of 40 hours. When you run the load leveling, Project will move the task end dates out a week so the resource has 80 hours to complete 80 hours of work.
Strength: Reschedule Based on Actual Finish Date
Few of the cloud-based tools support rescheduling dependent tasks based on the actual finish date. Most tools only have one finish date (no planned and actual), and may also assume the finish date is the day the task is marked complete.
Project tracks both the planned and actual date and then will re-schedule the dependent tasks based upon the actual finish date.
Weakness: No Tasks Checklists
Project does not support creating a checklist for an individual task, like some of the other tools. This can be helpful in providing guidance to the users and competing the overall project plan simpler.
Weakness: Coordination with External Team Members
Project does not have the ability to assign a task to an external resource and allow the external resource to update the task without a Microsoft license.
Scope Management
No scope management functionality worth mentioning.
Stakeholder Management
No stakeholder management functionality worth mentioning.
Scoring Methodology
I installed the free trial of Plan 3 and then created some sample projects in Project Professional which were synched with Project Online. I spent hours trying to synch the Project Online project to a SharePoint project site but was unable to ever make this work. I tested most of the functionality listed on the evaluation spreadsheet myself, but also reviewed Microsoft demos and support documentation.
I gave all processes and requirements equal weights, but you can adjust the scoring weights in the 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 is the spreadsheet used to score the app:
In Conclusion
Microsoft Project Plan 3 should be on your shortlist of possible project management tools if:
You have professional project managers that need full scheduling functionality.
You are already a Microsoft customer.
You should skip Microsoft Project if:
You only need a simply task management tool.
You are scheduling very large construction projects.
You are a professional services firm that needs advanced resource management and invoicing capabilities.
If this Microsoft Project review was helpful please leave a comment.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
This Wrike Salesforce integration review examines the Wrike functionality provided by integrating Wrike with Salesforce. The Wrike Salesforce integration provides the following functionality: synching tasks, posting Salesforce data to Wrike and building cross-app workflows. This is a supplemental post to the detailed review of all Wrike functionality.
Evaluate Wrike Salesforce Integration Quickly
Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Wrike Salesforce Integration quickly and thoroughly.
Wrike provides multiple standard integrations with Salesforce. They boil down to three main integrations:
Share or sync Wrike tasks on Salesforce. You can either view Wrike tasks on associated Salesforce objects (i.e. opportunities, accounts, etc.), or you can synch Wrike and Salesforce tasks.
Post Salesforce data to Wrike folders or projects. You can create an association between a Wrike folder or project and a Salesforce object. This will result in the Salesforce object’s data being posted to Wrike. An example would be associating a Salesforce opportunity to a Wrike folder and posting the opportunity stage or revenue estimate.
Create cross-app workflows. You can create automated workflows which are triggered in Wrike but update Salesforce objects or vice versa. For example, you could create a workflow where marking an opportunity in Salesforce as ‘won’ triggers the creation of project via template in Wrike.
Here is Wrike’s overall project management functionality score which is based on the Wrike detailed review post.
Wrike
Total Score
53%
Communications Management
14%
Cost Management
32%
Integration Management
52%
Procurement Management
13%
Quality Management
25%
Resource Management
79%
Risk Management
75%
Schedule Management
71%
Scope Management
44%
Stakeholder Management
29%
Wrike Salesforce Integration Options
The following are the integration options supported by Wrike. Of course, you could always build your own integration with tools like Zapier.
Salesforce
Provides one-way integration of data between Wrike and Salesforce.
Place a Wrike task widget on any Salesforce object’s lightning record page. You can add the widget to both standard and custom objects. Now the Wrike tasks associated with the Salesforce record are displayed on the Salesforce page. The Wrike tasks displayed in Salesforce can only be viewed in Salesforce (not updated). However, you can click on a displayed task and it will open a Wrike tab to make updates.
Post Salesforce object data to a Wrike folder or project. For example, you could post the opportunity stage or revenue to a Wrike project.
Salesforce via Wrike Sync
This is a synched two-way interface built in Unito. You can sync opportunities, contacts, cases or tasks. The main use case would be to sync Wrike tasks to the Salesforce task object. This would allow Salesforce users to create and update Wrike project tasks within Salesforce.
The Unito solution also includes automation so that you can create Wrike tasks based on the status of Salesforce objects. For example, create a Wrike task when a Salesforce opportunity reaches a particular stage.
Wrike Integrate
Wrike Integrate allows you to integrate Wrike with hundreds of other apps including Salesforce. These are basically cross-app record-triggered workflows. If a record is created/updated in Salesforce the workflow will create/update a record in Wrike and vice versa. Some examples are:
Opportunity won in Salesforce, create a project from a template in Wrike
New case in Salesforce will create a Wrike task
There several prebuilt Salesforce integrations to choose from:
Salesforce
Salesforce CPQ
Salesforce Marketing Cloud
Zuora for Salesforce
Wrike Salesforce Integration Pricing
Pricing is going to vary based on the type of integration and Wrike does not publish these prices. There are also minimum package requirements.
Name
Wrike Requirements
Salesforce Requirements
Wrike Price
Salesforce
Business, Enterprise or Pinnacle Account
Enterprise or Unlimited
$0
Salesforce via Wrike Sync
None
None
Contact Wrike or Unito Sales
Wrike Integrate
None
None
Contact Wrike Sales
Review Methodology
Unfortunately, I wasn’t able to get the Wrike/Salesforce integration to work. I had the required Salesforce and Wrike test environments but when I installed the Wrike widget in Salesforce I got the following error: “You are logged in to a different Wrike account than the one used to configure the integration. Please contact your SalesForce administrator.” This makes no sense, since I only had one Wrike account. I couldn’t find any documentation concerning this error.
Therefore, this review is based on:
My attempt to install the integration and going through the setup process
Reviews of Wrike documentation and demos
Reviews of integration posts on the Internet
Here is the spreadsheet used to score all of Wrike’s functionality:
In Conclusion
There are several options to integrate Wrike with Salesforce. These will allow you to build some of the professional services automation (PSA) tool functionality available in native Salesforce tools. Such capabilities as, creating a standard onboarding workplan in Wrike when a Salesforce opportunity is won.
The integrations would also allow you to store your project meta data in Salesforce and just use Wrike as a scheduling tool.
If you found this Wrike Salesforce integration review helpful, please leave a comment.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Wrike Pinnacle is reviewed against 200+ project management software requirements on a downloadablespreadsheet. Wrike Pinnacle 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.
Download Wrike Pinnacle Evaluation Spreadsheet
Click here to add the Wrike Pinnacle Excel spreadsheet to your basket. Visit the basket page to complete the download.
Wrike has come a long way since I first used it several years ago. It has a very functional and robust scheduling tool which is better than most cloud-based tools. Probably, not good enough for large complex construction projects, but good enough for regular business and IT projects.
Wrike Pinnacle also has budget and resource management functionality. However, this functionality isn’t robust enough for a professional services firm looking for a professional services automation (PSA) tool. There are better dedicated PSA tools on the market with much more extensive functionality. Best Salesforce PSA Tools.
Wrike has major gaps in its out-of-the-box functionality. However, it is so flexible that the gaps can be filled through configuration so Wrike got lots of partial credit in the scoring process. For example, it doesn’t have dedicated risk management functionality. But it scored well in this category because it offers a template than can be used to build a risk log, which is the equivalent of a risk log in a spreadsheet. Just be aware that to achieving the full functionality will require considerable configuration work.
Wrike Pricing
Wrike has five pricing plans. This review was based upon the highest priced plan: Pinnacle. Below is a summary of key differences between the plans for full details see: Wrike Pricing Comparison. I couldn’t find any rumors of Enterprise or Pinnacle pricing on the Internet, so you’ll have to contact Wrike.
The main takeaways are:
Almost every company is going to need a Business plan or above
Wrike requires an Enterprise plan to get basic security features. Any large IT org isn’t going to allow implementation without these:
Minimum password requirements
Multi-factor authentication
User audit reports
Single sign-on (SSO)
Controlled admin permissions
If you are a professional services organization using Wrike as a PSA, then you will need the highest priced plan: Enterprise
Almost everyone in your organization will require a Wrike license if they are being assigned Wrike tasks. Wrike does offer a Collaborator user type that is free but limited and intended for external users such as, contractors and clients. A Wrike plan comes with a free number of Collaborator licenses: 20 or 15% of paid licenses, whichever is greater. Collaborators can:
View projects and folders shared with them
View and update tasks assigned to them
Plan
$/User/Month
Key Differentiators
Free
$0
1) No Gantt/Timeline view 2) No automations 3) No custom fields 4) No dashboards or reports 5) No resource management
Team
$9.80
1) Custom fields 2) Gantt/Timeline view 3) Dashboards 4) Automations 5) No reports 6) Max 25 users
Business
$24.80
1) Group projects into portfolios 2) Reports 3) AI functionality 4) Custom task types (bugs, user story, etc.) 5) Approvals 6) Basic resource management 7) Salesforce integration
I performed this evaluation using a free trial of Wrike Pinnacle. I also reviewed Wrike demos and documentation. Finally, I reviewed online reviews and comments for any user insights.
I’ve been evaluating all of the 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 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 tools compare by process. Therefore, you can assess the tools based on which processes are the most important to you.
Download Wrike Pinnacle Scoring Spreadsheet
Click here to download the Wrike Pinnacle Excel spreadsheet.
Like all the project management tools I reviewed so far, Wrike doesn’t have any significant communications functionality. If you have a large initiative that requires managing a large amount of communication or training, you’ll need to research learning management systems (LMS).
Cost Management
Only Wrike Pinnacle has any out-of-the-box cost management functionality. You can create custom fields on the other plans to track costs.
While Pinnacle will capture hours and billing rates, Wrike doesn’t have the ability to issue invoices. I’ve given Wrike partial credit to track invoices, because you could create the equivalent of an invoice tracking spreadsheet in a folder, but this is a far cry from the functionality found is best-of-breed PSA tools.
Strength: Optional Rollups
The custom cost fields you create on the tasks can be rolled up to the project. A nice feature is that you can turn the rollup on or off. This is useful early in a project. You can manually enter a high-level cost estimate for the project before you have all the individual cost line items identified. Later, you once you have the details you can allow the automated rollup. This ensures that any reporting against the rollup field is always accurate.
Strength: Project Specific Rate Cards
The billing and costs rates can be varied per project. This is key if you want to use Wrike to sum billings, to be used in another system to create the invoice.
Strength: Pre-Populated Timesheets
A team member’s timesheet is automatically pre-populated with any completed tasks. This serves as a reminder to enter their time and not miss a task.
Weakness: Doesn’t Generate Invoices
While you can capture and sum the hourly billing data, Wrike doesn’t have any functionality to generate an invoice. Wrike does have standard integrations with common accounting systems, so you should be able to pass Wrike data to your accounting system to generate invoices.
However, many of the best-of-breed PSA tools do have native invoicing functionality and can create different types of invoices: fixed fee, T&M, etc.
Weakness: Doesn’t Handle Expenses
I couldn’t find any expense management functionality. This would be a huge gap for a professional services firm that needs to bill clients for expenses. Team members can’t enter expenses on their timesheet and submit for approval.
Weakness: No Daily or Overtime Rates
Wrike only supports standard hourly rates. It does not support billing based on daily rates, which is fairly popular in professional services firms. It also does not support billing extra for overtime.
Integration Management
With configuration, Wrike has strong overall integration management functionality. You should be able to build good status reports and to easily collaborate. The only major gap I found was the inability to manage programs.
Strength: Detailed Project Access Controls
You can control access rights individually by project. You can make projects public or confidential. Also, you can assign edit vs. read-only rights to team members.
Finally, you can control access to financial data. So a team member can access a project, but not be able to see financial data like the budget or billing/cost rates for resources. However, if you create custom cost fields to track costs, they will be visible to anyone with access to the project.
Strength: Custom Fields at the Project Level
When you create a custom field you designate which objects it should be used on:
Tasks, projects and folders
Projects and folders
Just projects
This gives you the flexibility to create whatever project meta data fields you want. For example, you could add a ‘Project Health Comment’ or ‘Project Path to Green’ to be included in the status report.
Weakness: Doesn’t Support Programs
Wrike allows projects to be grouped in folders. You can then perform consolidated views and reporting against the folder. I consider this portfolio functionality. It doesn’t support program functionality since it doesn’t have programs as their own entity type. Therefore, you can’t define a program, define a team or set a budget for a program.
Procurement Management
Wrike like all the rest of the PM tools I’ve reviewed, doesn’t have any procurement management functionality to manage contractors and purchases.
Quality Management
Wrike doesn’t support any quality or testing functionality out-of-the-box. You could build the equivalent of test scripts in spreadsheets but this is a far cry from the functionality of a true quality tool.
Resource Management
Wrike provides the ability to view consolidate resource assignments and to record time on timesheets in the Business Plan and above. The Pinnacle plan is required to:
Define and assign job roles
Create budgets based on staffing and rates
Measure utilization
Strength: Soft Book Resources
Resources can be soft booked by either role or individual using the ‘Resource Bookings’ feature available with the Pinnacle plan. This allows the resource manager to see open resource requests by role, and also when resources have been tentatively assigned so that they can be re-assigned if necessary when balancing workloads.
Strength: Resource Allocation by Project
Wrike’s ‘Resource Booking’ feature allows people to be assigned at the project level. Many PSA tools only assign resources at the task level. This is an issue in the early planning stages of a project, and on internal business/IT projects where effort won’t be estimated to the individual task level.
Weakness: Can’t Forecast Demand Based on Sales Pipeline
The ‘Resource Booking’ process used to forecast demand by role is a manual process. Many other PSA tools can associate a standard project template’s roles to opportunities in the pipeline to create an automated forecast. In Wrike, you would have to manually create a booking for every role in every opportunity in the pipeline.
Risk Management
Wrike provides a standard risk template (RAID Template) to log all risks within a space. You can also add custom fields to this template to match your risk management methodology. However, this is equivalent to using a spreadsheet for a risk log/matrix. This poses issues for reporting and resolution which I note below.
Strength: Assign Tasks to Risks
Many tools lack the ability to assign tasks to a risk. Often, a project manager is going to want to assign and track task such as, investigations or mitigation steps. In Wrike, you can create subitem tasks for any of the risk records.
Weakness: Can’t Associate Risk to a Project
The provided risk template works at the space level, and therefore if you have multiple projects in a space you won’t be able to tell which project a risk pertains to. I know this sounds crazy, but I couldn’t figure out how to do it. I think it is a limitation of Wrike not be a relational database. You can ‘related’ the risk record to a project record.
You could create a custom field to manually enter the name of the project or select from a custom dropdown list. However, this isn’t the same as relating to the project record and could eventually cause reporting issues.
Schedule Management
Wrike has strong scheduling functionality. It has better functionality than most of the other cloud-based scheduling tools. The gaps it has are shared by most of the other cloud-based tools:
Only supports one constraint type: Start No Earlier Than
Doesn’t support effort-based scheduling
Doesn’t support automated load leveling
Doesn’t reschedule based on actual completion date
It does have a few odd gaps, which aren’t a high priority but are usually standard with other tools. I’ll comment on these below.
Strength: Dependencies and One Constraint Type
Wrike supports all dependency types (SF, FS, SS, FF), lead/lag, multiple predecessors and the Start No Earlier Than constraint.
Strength: Inter-Project Dependencies within a Folder
I’m not sure if this is a strength, I’ll let the reader decide. If you consolidate multiple projects into a folder, you can assign inter-project dependencies within the folder view. However, I believe it would be rare for a folder to contain projects run by different project managers. Therefore, you wouldn’t define inter-project dependencies for projects managed by different project managers.
Weakness: Doesn’t Support Releases
You can’t create a release record with meta data and associated records, such as, user stories. This is a large gap for IT projects. You could work around this partially by grouping your tasks/user stories under a parent task that represents the release.
Weakness: Can’t Assign a Task to a Team
You can assign tasks to multiple people, but you can’t assign a task to a predefined team, and then have a member of that team work the task from a queue.
Weakness: No % Complete for Tasks
This gap seems odd to me, but you cannot record a % complete for a task. You can only calculate a % complete for a project based on several options (% completed tasks, % completed hours, etc.). If your tasks are short than this shouldn’t be a problem. However, if your tasks are large this could have implications for accurately calculating the Cost Performance Index (CPI).
Scope Management
By adding some custom fields, you could create a decent scope management solution. One big plus, is that Wrike has a standard template and forms for handling change requests.
Stakeholder Management
By adding some custom fields and custom folder templates you could build the equivalent of a stakeholder management solution in spreadsheets. You won’t be able to do advanced company-wide reporting like you could do with a relational database, but it should suffice for all but the most complex change management efforts.
In Conclusion
I was expecting to slam Wrike in this review because I hated it when I used it a few years ago. However, it has come a long way and I’ve scored it higher than Asana or Smartsheet (Comparison of Project Management Tools). It appears to have more flexibility in the definition of custom fields than the other two tools and therefore is more configurable.
While I can see Wrike being a good tool for a small organization or a simple project process, I feel its architecture will limit it for use in larger use cases. It feels very similar to Asana and Smartsheet, like it is a user interface on top of spreadsheets and not a true relational database. I worked with a client that had outgrown Smartsheet and I feel many companies may eventually outgrow Wrike.
Professional services firms should not make a purchase decision until first evaluating some of the dedicated PSA tools, such as: Kantata, Certinia, Cloud Coach. These tools have much broader and robust PSA functionality than Wrike.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
The Asana for Salesforce integration tool is reviewed against 200+ project management software requirements on a downloadablespreadsheet. Asana for Salesforce 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.
Download Asana for Salesforce Fit/Gap Scoring Spreadsheet
Click here to add the Asana for Salesforce Excel spreadsheet to your basket for FREE. Visit the basket page to complete the download.
I can’t come up with a use case for integrating Asana with Salesforce rather than either using a native Salesforce project management tool, or a professional services automation (PSA) tool that integrates with Salesforce. If you have already made an investment in Asana and wish to integrate with Salesforce it might make sense.
However, the latest review on the Salesforce AppExchange from August 2022 states that the Asana for Salesforce integration app is critically broken. There isn’t any reply to the review from Asana, and I was unable to confirm because my Asana free trial doesn’t support the integration. However, other online reviews were not kind to Asana for Salesforce. Asana did deploy a new release in October 2023, but there haven’t been any new reviews since then. I’ve listed other integration alternatives in a later section of this post.
Asana for Salesforce Pricing
Asana for Salesforce itself is free, but it is only available for Asana Enterprise which is the highest-priced license. Asana does not publish a standard price for Enterprise, but the Internet claims it varies from $44 – $49/month/user. Must purchase a full year for a minimum of 5 seats, with minimum increases in blocks of 10.
Minimum annual cost would be $2,640. Annual cost for 50 users will be $29,040.
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 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: I was unable to install Asana for Salesforce myself, because the Asana free trial does not support the integration. I was unable to confirm the review that the app is critically broken. I did review all of the available documentation, demos and online reviews.
Here is the spreadsheet used to score the app which is the score for Asana functionality if it included integration with Salesforce:
Download Asana for Salesforce Fit/Gap Scoring Spreadsheet
Click here to download the Asana for Salesforce Excel spreadsheet for FREE.
There are other vendors offering Asana/Salesforce integrations and you can always build your own with Zapier or Unito. But to my earlier point, why would you integrate Asana to Salesforce when there are better native options.
Also, the Asana for Salesforce integration doesn’t actually synch Asana and Salesforce tasks. Instead, the Asana tasks are listed within an Asana Lightning Web Component on the Salesforce screen. This means that Salesforce users will have to reference both their Salesforce tasks and Asana tasks separately. Using one of the vendors should allow you to actually synch to the Salesforce tasks, as I’ve seen this done in the past.
Here are vendors claiming to offer Asana/Salesforce integration:
See my full review of Asana for details about the Asana tool functionality. I’m going to list here the additional functionality you will gain by integrating with Salesforce.
Project Plans for Salesforce Cases
Several forum posts mentioned Salesforce customers creating Asana project plans for individual Salesforce cases. The Salesforce users will be able to view and update the Asana tasks through the Lightning Web Component.
Forecast Resources Based on Sales Pipeline
If you create a standard Asana project from a template with tasks assigned to a skill or role for specific Salesforce opportunities, you could create a future resource forecast based on the sales funnel. This would all have to be custom configured because the Asana resource management tool only supports planning based on individual not based on skill/role. Or you could implement a PSA tool that already has this functionality built.
Create Project from Opportunity Status
You can create an automated process to create an Asana project from a standard template whenever a Salesforce opportunity reaches a certain status. This is a common feature also supported by PSA tools.
Automatically Create an Asana Task or Project
You can create a record-triggered flow in Salesforce that will create either an Asana task or project when certain criteria are met. The Salesforce Flow simply calls a provided Apex class. There are two Apex classes for use:
Create an Asana project
Create an Asana task
Of course, you could also create a record-triggered flow in Salesforce that would simply create a Salesforce task.
Measure Asana Goals in Salesforce
If your Asana project has a sales goal, you can measure progress towards the goal in Salesforce and then display the current sales in the Asana goal. This is done by connecting a Salesforce report to the Asana goal. The Asana goal simply displays the total value for the Salesforce report.
In Conclusion
Integrating Asana with Salesforce only makes sense if you are already heavily invested in Asana. If you are looking to create or upgrade your project management solution you should consider other options. There are several native Salesforce scheduling tools that are better and cheaper than Asana. If you need to integrate Asana with Salesforce then you probably should consider a professional services automation (PSA) tool.
If you insist on integrating Asana with Salesforce, then CAUTION using the Asana for Salesforce tool as it may have a critical bug. You need to contact Asana Sales to get a trial setup in a sandbox so you can confirm whether it is actually working. If not, you should evaluate the other integration tools listed above.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Asana is reviewed against 200+ project management software requirements on a downloadablespreadsheet. Asana 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.
Download Asana Fit/Gap Scorecard
Click here to add the Asana Excel spreadsheet to your basket and continue reading. Visit the basket page to complete the download.
Asana is one of the project management lite cloud-based tools that have been popping up like mushrooms for the last few years. It is a nice-looking collaboration tool for simple projects. However, it could not be used by a professional project scheduler on complex projects.
After using it, I sense that it is really just SmartSheets with a prettier user interface. The ‘projects’ are really just sheets with some custom scheduling functionality. They aren’t tables in a relational database, which limits Asana from being a robust tool. The ‘projects’ can be bastardized by hiding existing fields and adding custom fields to make almost any spreadsheet list you want.
1) Can create projects and tasks 2) Can’t access the following key functionality: i) Timeline/Gantt view ii) Forms iii) Dashboards iv) Task dependencies
I signed up for the Asana free trial and built my own project. I also reviewed Asana demos and documentation. Finally, I reviewed various forums on the Internet for customer insights.
I’ve been evaluating 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 you can download the detailed Excel spreadsheet 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 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 is the spreadsheet used to score the app:
Download Asana Fit/Gap Scorecard
Click here to download the Asana Excel spreadsheet.
Asana doesn’t contain any change management or training functionality to speak of. You can communicate within the project team using a message board. If you have any significant volume of training or communications you’ll need a learning management system (LMS).
Asana doesn’t have any real budget, cost or expense management functionality. You can create custom cost fields on the tasks and have them roll up to the project. But, this is a far cry from a true cost management system.
Asana also lacks any invoicing functionality. So if you are professional services firm, you should consider a dedicated professional services automation (PSA) tool.
As a collaboration tool, Asana does have some decent integration management functionality.
Strength: Goal Statements
Asana is one of the rare project management tools that provides any functionality to document the business case. You are able to document the project goals, supported by sub-goals. This allows you to explain the project purpose to the team and stakeholders, as well as, track achievement of the goals.
Strength: Robust Project Security
The project manager has lots of control over access to the project:
Projects can be made public or confidential.
Users can be given read-only or various levels of edit rights.
External users (i.e. clients or vendors) can be given limited access to the project.
Strength: Status Reporting
You are able to publish a status report and it is displayed along with a history of the earlier status reports. There is even an AI feature which will supposedly draft the status report for you. I wasn’t able to see this in operation because my test project didn’t have enough history, but if your status reports are so cut-and-dried that AI can produce them, then maybe you shouldn’t be creating them in the first place.
Weakness: External Access to the Project
Providing a client or vendor access to the Asana is pretty much an all-or-nothing option:
If you give the client access to the project, they can view all tasks and all project information. This would include internal comments, internal tasks and any financial information.
You can block the client from seeing the project information by only giving them access to specific tasks. Then they can’t see any project information, just the tasks they are assigned. However, now they won’t be able to see the basic progress of the project.
Procurement Management
Asana doesn’t have any real procurement management functionality and it would be difficult to build. If you are capturing costs on the tasks records, you could also capture the vendor’s name and create summary reports.
Quality Management
Asana doesn’t provide any quality management (i.e. testing) functionality and it would be difficult to build.
Resource Management
Asana has some very basic resource management functionality which they call “workload management’. This functionality isn’t robust enough for a professional services firm. Because, it is based entirely on rolling up labor estimates for individual tasks it probably isn’t ideal for a company’s internal PMO, where that level of planning is rarely required.
Weakness: Only Task-Level Allocations
As a program manager on large company’s internal improvement projects, I rarely attempt to assign labor to individual tasks and use these for resource planning. Instead, I estimate at a deliverable level and then allocate people based on a percentage of their time. For example, John Smith is allocated to Project X for 50% of his time from March 1 – June 30. Asana does not support this approach.
Weakness: Can’t Plan Labor by Role/Skill
Asana doesn’t support:
Assigning standard skills to resources
Planning staffing based on required skills rather than individuals
Submitting resource requests based on skill
Risk Management
There isn’t any risk management functionality. You could create a separate project risk register by creating a new project, entering the risk under the ‘Task’ field and adding some custom fields. This is equivalent to the old approach of creating risk registers in Excel. There are several problems with this:
The risk register isn’t linked to the project in any way other than the name
You can’t create tasks related to investigating or mitigating the risks and tied directly to the risk
The Asana scheduling tool is very simplistic. It would drive a professional project scheduler that has used Primavera or Microsoft Project nuts. You could not use it for complex projects like construction projects or large IT programs. It is basically a to-do list with a few added features.
Asana is fairly unique in that is allows creating task automations. However, you can only build workflows or rules using standard pre-defined triggers and standard fields. You can’t build workflows or rules with custom fields or custom conditions.
Strength: Inter-Project Dependencies
The good news is that Asana has the rare capability to create dependencies between tasks in different projects. The bad news is that Asana’s approach is screwy and very limited:
It only supports a finish/start dependency
It doesn’t allow you to define lag, but gives you an option to either keep lag constant or vary it when a predecessor’s schedule changes
Strength: Assign Tasks to External Resources
You can assign a task to a vendor or client that doesn’t have Asana and they can update the task without an Asana license. This is a nice feature that isn’t supported by all tools.
Strength: Recurring Tasks
You can create recurring tasks without having to copy and paste multiple times. This is a feature only supported by a few tools.
Weakness: Limited Dependencies
As I stated above the approach to dependencies is pretty strange. It almost looks like a last minute workaround because they couldn’t get a standard approach to dependencies to work. Here are the issues:
Only supports Finish/Start. Doesn’t support the others: Finish/Finish, Start/Start or Start/Finish.
Can’t define or edit lag. The lag is set when you create the start and finish dates of the tasks with a dependency. There is a project setting which sets your preference for maintaining the lag or adjusting the lag when you change the due date of predecessors.
Doesn’t support constraints and doesn’t use a default ‘Start as Early as Possible’ constraint. Because of the lag approach, if you create a dependency it won’t automatically reschedule so the second task starts as soon as the predecessor is completed.
You can’t define or view the duration other than setting start/finish dates. However, when a dependent task slips it appears to maintain the original duration.
Weakness: Doesn’t Support Effort-Based Scheduling
Most advanced tools allow you to use fixed duration or fixed effort scheduling. Meaning if you add a second resource do you want the duration to remain the same or do you want to be cut in half? Asana only seems to support fixed duration scheduling. This isn’t unusual for these project management lite tools.
Weakness: Can’t Assign Multiple People to a Single Task
Well technically you can, but Asana simply creates a separate duplicate task for each person you add. To make it worse it copies the effort so if you have a task that takes 10 hrs and you assign a second person you now have an estimate of 20 hours.
Scope Management
Like most of the tools I’ve reviewed, Asana doesn’t have any functionality for recording scope. You could add some custom fields to the project to track some scope information. You could also create a custom change request form and change request log to track scope changes.
Stakeholder Management
Like most tools, Asana doesn’t support any functionality for defining project stakeholders and change impacts to plan change management activities. You could add some roles to project team members to document the sponsor and steering committee members.
In Conclusion
You probably guessed I’m not a big fan of these cloud-based project management lite tools. It is a step backwards to thirty years ago when I was managing projects in Excel spreadsheets. But if you are looking for a simple collaborative to do list, then Asana is worth considering. You should definitely evaluate both Asana and Smartsheets, to see which you prefer based on your particular requirements.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
I couldn’t find any key differentiators to distinguish Arrow PSA from the other leading Salesforce PSA tools. While Arrow PSA has the basic features required of a PSA tool it doesn’t have the breadth of functionality of other options.
Arrow PSA Salesforce app is reviewed against 200+ project management software requirements on a downloadablespreadsheet. Arrow 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.
Customized PSA Tool Shortlist
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.
Unfortunately, I couldn’t find any key differentiators to distinguish Arrow PSA from the other Salesforce PSA tools, and its functionality isn’t as extensive as the other tools. If you are considering implementing a PSA tool, I suggest you consider one of the tools in this blog post: Best Salesforce Project Management PSA Tools. If you still would like to explore Arrow PSA, continue reading for a detailed review and also download the free trial from the AppExchange listing.
Arrow PSA Pricing
Standard pricing is $40/user/month. This pricing is equivalent to other Salesforce PSA tools. You will need to purchase a license for anyone who must update project tasks and enter time. So the total cost could be considerable if you have lots of people working on projects.
Evaluate Arrow PSA Quickly
Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Arrow PSA quickly and thoroughly.
None of the Salesforce PSA tools have dedicated change management/communication functionality. Arrow PSA is the same. You will need to build some custom solutions or implement a training management system (TMS) if you want robust communications management functionality.
Cost Management
Arrow PSA has some nice invoicing features and I like that it captures project costs as related records that rollup to the project budget.
Strength: Customer/Project Specific Invoicing
There are multiple invoicing options and you can vary the invoicing approach by customer/project:
Time & materials
Templated invoiding
Retainer invoicing
Billing event invoicing
Manual invoicing
Fixed fee
The billing event invoicing option allows you to define a milestone task that will automatically generate an invoice when the task is completed. Ideal for progress-based invoices.
It also allows you to define a specific rate card for each project.
Strength: Detailed Budget Line Items
You are able to define detailed individual budget line items and these then rollup to the total project budget. Instructions are even provided on how to customize the rollup rules to suit your needs.
The one odd thing is that a date field is not provided on the budget item record. This can be easily rectified by adding your own date field and then you can create cash flow forecasts.
Weakness: No Daily or Overtime Rates
Daily or weekly rates are popular in consulting and software development, however Arrow PSA only supports hourly rates. It also does not support the charging of overtime rates.
Weakness: Can’t Track Invoice Payments
While there is good functionality for issuing invoices, there doesn’t appear to be any functionality to track invoice payments. Perhaps, Arrow PSA assumes tracking of payments will be done in the company’s accounts receivable system.
Weakness: Timesheet Alerts and Tracking
Many of the timesheet alert and tracking features which are standard functionality in other PSA tools are missing from Arrow PSA. These are alerts like unsubmitted timesheets, or complete tasks without time assigned, etc. Building such alerts for yourself would not be a very large effort.
Integration Management
Arrow PSA has a lot of the components needed for integration management, but I wasn’t overly impressed with the standard dashboards and reports provided with the app. Of course, this being Salesforce you can fairly easily build your own dashboards and reports.
Strength: Forecast of Revenue and Costs
The standard dashboard has a some good charts summing the forecasted revenue and costs across the projects.
Weakness: No Project-Level Security
All of the security and permissions are controlled at a global level through permission sets. Therefore, you cannot vary permissions at the individual project level. This would prevent you from make a project confidential if it was sensitive. It also prevents you from giving resources edit access to one project and read only access to another project.
Weakness: No Status Stoplight
Having a visual representation of the project status (red, yellow, green) is pretty standard functionality. Arrow PSA doesn’t support this. However, it would only be a medium-sized effort to close this gap for yourself.
Weakness: Doesn’t Support Programs
Arrow PSA does not allow you to group projects into programs and then rollup all the financials to the program. This is would not be an easy gap to fix, because you’d have to build the rollup capabilities.
Procurement Management
The same as most PSA tools, Arrow PSA doesn’t really have any procurement management capabilities.
Quality Management
The same as most PSA tools, Arrow PSA doesn’t really have any quality management functionality around testing.
Resource Management
Arrow PSA has the basic resource management capabilities of all PSA tools. It does lack some bells and whistles found in other tools.
Strength: Mass Reassignment of Resources
Arrow PSA offers a feature where you make a mass update to all assign project tasks when you replace one person with another. This is a big time saver.
Weakness: Doesn’t Support Percentage Allocations
This probably isn’t a major gap for professional services companies, but it would be a major gap for the types of internal projects I work on. You can’t simply assign a person to a project as x% of their time. You have to assign them to specific tasks with defined work efforts. This is much more detailed planning than is necessary on most of my projects.
Weakness: No Resource Requests
While the resource management tool would allow a resource planner to see tasks not assigned to a person, Arrow PSA doesn’t allow project managers to submit specific resource requests like other tools.
Risk Management
Arrow PSA gets kudos for having separate risk records. However, it is missing the ability to assign tasks to address the risks and fields to quantify the risks.
Weakness: Missing Risk Measures
It is missing fields on the risk records to capture probability and severity which are used in a typical risk matrix. This should be easily added.
Weakness: Can’t Assign Tasks to Risks
You could assign standard Salesforce tasks to the risk records by adding the task action to the page layout. However, this would present challenges for reporting as the tasks would be associated with the risk ID and not the parent project ID.
Schedule Management
I ran into lots of issues when testing the Planner tool, which is Arrow PSA’s version of a Gantt view. It has been designed to deliver lots of the standard scheduling functionality but I was running into several bugs. It could be my misunderstanding of how to use the app, but if you are considering Arrow PSA you should test these issues yourself.
One strength is that it has been designed to support a version of constraints. However, I couldn’t get it to function properly.
The Kanban board has a unique feature where a user can enter the % of work complete right on the ticket. However, the Kanban board also has a major gap in that you can’t reorder tickets within a column.
Strength: Earliest/Latest Start and Finish
Arrow PSA has the fields to define a version of constraints: earliest/latest start date and earliest/latest finish date. However, when I entered these values they didn’t actually affect the dates on the Planner tool, so you should test this functionality for yourself.
Strength: Enter % Complete on Kanban Board
A user can use a sliding scale to enter the % complete directly on the Kanban ticket.
Weakness: Planner Bugs
I came across the following bugs when testing the Planner (i.e. Gantt) tool. This could have been user error on my part, so you should test these for yourself:
Finish date not calculated correctly based on duration. I changed the duration on a task starting 5/24 and it did not change the finish date from 5/31.
Planner dates out of synch with task dates. The same task shows different values in the Planner view and the task record.
Planner dates out of synch between start/finish columns and the bars on the Gantt.
Lags on dependencies weren’t calculating correctly.
Got an error when attempting to create a task in the Planner tool.
Doesn’t support Lightning Web Security in the Spring ’24 release. Arrow tells me they are fixing this soon. You can work around this by changing an org setting.
Weakness: Can’t Reorder Kanban Tickets
I couldn’t reorder the task tickets within a column on the Kanban board. This is critical functionality for my Agile teams. The product owner is setting priorities by placing the most important tickets at the top of the columns.
Scope Management
Arrow PSA doesn’t have the ability to capture detailed scope line items. It does have the ability to capture additional budget line items that are incremental to the approved budget.
Stakeholder Management
The same as most PSA tools, Arrow PSA really doesn’t support any change management functionality and therefore doesn’t have much functionality for managing stakeholders.
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 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 is the spreadsheet used to score the app:
In Conclusion
While Arrow PSA has the basic features required of a PSA tool it doesn’t have the breadth of functionality of other options. I also couldn’t find a unique function that would differentiate it from the other tools and make it the best tool for a market niche.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Smartsheet is reviewed against 250+ project management software requirements on a downloadablespreadsheet. The review is conducted with the intent of using Smartsheet as the scheduling tool integrated with a Salesforce project management solution. The problem is, I couldn’t come up with a valid use case for such an integration. There are better options available.
Download Smartsheet Evaluation Spreadsheet
Click here to add the Smartsheet Excel spreadsheet to your basket and continue reading. Visit the basket page to complete the download.
I cannot come up with a business case where a current Salesforce customer should consider integrating with Smartsheet for a Salesforce project management solution. I was interested in writing a review of a Smartsheet/Salesforce integration because a previous client had been using such an integration before I helped build a replacement. I thought there might be a business case for a small firm, but there isn’t.
Business Case 1: PSA Tool
There are two basic options to integrate Smartsheet with Salesforce for project management. The first would be to automate the creation of a Smartsheet project when a Salesforce opportunity reaches a certain stage. In other words, you want to create the project from the Salesforce opportunity. This business case would arise in a professional services firm (i.e. architect, accounting, software development, etc.). The project would be managed in Smartsheet once the opportunity was sold.
This business case is the same as a professional services automation (PSA) tool. There are several native PSA tools built on Salesforce which have much better and broader functionality than Smartsheet. See my review of the best Salesforce PSA tools. There are also several non-native Salesforce PSA tools that integrate with Salesforce and have much better functionality than Smartsheet. Therefore, the business case for this type of integration doesn’t appear to be valid.
Business Case 2: Project Scheduling Tool
The second integration option, is to purchase or build a native project management functionality on Salesforce supplemented with the Smartsheet project scheduling tools. Again, there are several native scheduling tools built on Salesforce which have better scheduling functionality than Smartsheet. See my review of the best Salesforce scheduling tools. There are also several external scheduling tools which have much better scheduling functionality than Smartsheet, such as, Microsoft Project. Therefore, the business case for this type of integration doesn’t appear to be valid.
Smartsheet Pricing
Smartsheet offers standard pricing for their basic model at $25 per user/month with a minimum purchase of three users. However, apparently a full featured solution would be much more expensive. To achieve the functionality that was evaluated you would have to purchase the following on top of the standard license. Pricing for these modules is custom, but I’ve included unofficial price citations I found on the Web. You’ll need to contact Smartsheet Sales to confirm this pricing:
Control Center – $20,000/year plus a install service fee (3 developers for 3 months at $150/hr).
One big advantage of Smartsheet is that a license is not required to view a Smartsheet. Therefore, you only need to buy a licenses for your project managers and admins. You don’t need a license for everyone assigned a task like some other tools.
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 gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheet to suit your needs. It was difficult to evaluate Smartsheet because it is so flexible almost anything could be built. 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. In the case of Smartsheet, almost anything can be built using their low-code platform, it is so flexible. I assigned this rating if a custom workflow would be required or a series of custom linked sheets. 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 is the spreadsheet used to score the app:
Download Smartsheet Evaluation Spreadsheet
Click here to download the Smartsheet Excel spreadsheet.
Smartsheet doesn’t have the functionality of a training management system (TMS), and I don’t believe it could be built. You could use a sheet to list training dates and there is a chat feature, but that is the extent of the communication functionality.
Cost Management
Cost Management is one of the weaknesses cited in Smartsheet’s online reviews. You could build some basic cost management functionality. You could even build some invoicing capabilities but I believe it would require significant effort. One of my clients added a cost column and payment date column to their project plan sheets so that they could generate a cash flow forecast related to project tasks.
Weakness: No Invoicing
It would be a lot of work for a professional services company to build the capability to invoice customers based on a rate card and hours worked. I believe the process will still be manually intensive, especially if you need the ability to invoice some customers based on hours and others by day. Makes more sense to purchase a PSA tool.
Weakness: Time Not Tracked to Task Level
Smartsheet’s Resource Management module does not record time to specific tasks on the timesheets. Therefore you cannot pre-populate a timesheet with a person’s assigned tasks and have them populate their actual hours. You also can’t measure variance between planned and actual hours to the task level.
Integration Management
Good integration management functionality requires implementing Control Center. This will allow you to capture project level meta data: status, start, end, sponsor, etc. There is also good dashboard building capabilities.
Strength: Project Access Control
It is easy to designate whether a project should be public or confidential. You can also give individuals varying level of access: read only, edit, etc. Finally, if you implement Dynamic View you can give clients or external partners access to the project but block their access to certain columns (such as costs, etc.).
Strength: Highly Flexible
This is Smartsheet’s greatest strength. It is very easy for non-technical people to customize the sheets by simply adding columns. This means it will be very easy for you to customize the project meta data to be captured for each project and how you want to report status.
Weakness: No Change Orders
Smartsheet doesn’t come with out-of-the-box change order functionality. You could build a separate change order sheet for each project and build an approval workflow. However, this would be a considerable amount of work.
Procurement Management
No procurement management functionality. However, this is common for project management tools.
Quality Management
Smartsheet doesn’t provide any testing functionality. However, I believe you could easily build a partial testing solution similar to what I’ve built in Excel in the past. You simply list each test with the indented test steps on a sheet. You have columns to capture test results for different runs. You will be able to attach the test evidence (i.e. screenshots) to the test step/task.
Resource Management
The Resource Management (RM) module must be purchased to provide resource management functionality. The RM module has the typical functionality summing assignments by resource on a timeline so you see who is available for a specific role. Resources can be assigned roles/skills and locations so the staffing manager can sort the available resources. Resource Management review on Capterra.
Strength: Typical Resource Availability Timeline
The resource availability screen is the same found on PSA tools and has a clean and easy-to-understand design.
Weakness: No Resource Requests or Forecasts
I could not download a trial of RM, but I could not find any example of a resource request. Most PSA tools have a functionality which forecasts resource requirements by role/skill on future projects and a formal process for submitting a resource request. It appears Smartsheet just assumes the resource manager will have knowledge of resource needs and then use RM to fill them.
Weakness: Can’t Soft Book Resources
Many PSA tools have a useful feature where a resource manager can soft book a resource. This means they can temporarily assign them to a project for planning purposes, but if resource needs change before they start the project they can be re-assigned. The soft booked resources are a different color on resource summary view so it is easy for the resource manager to see where they have flexbility.
Risk Management
No out-of-the-box risk management functionality. However, it would be fairly easy to build a risk sheet for each project to list the risks and mitigation steps.
Schedule Management
Smartsheet’s scheduling functionality is fair, but it has some serious gaps. It can be used for simple internal projects or simple software projects. It will not be sufficient for complex projects like construction projects.
Strength: Good Views
You can switch between the Gantt, Kanban and calendar views. The Gantt view can be customized and is very easy to use.
Strength: Task Dependencies
Smartsheet supports all dependency types: finish-start, start-start, etc. It also supports defining lag on dependencies. It even supports multiple predecessors assigned to a single task.
Strength: Unlimited Work Breakdown Structure
Many of the Salesforce native scheduling tools limit the levels of summary and child tasks that can be created. Smartsheet allows you to create an unlimited level of summary and child tasks to fit your work breakdown structure.
Strength: Assign Tasks to External Resources
Tasks can be assigned to anyone with an email address, and they aren’t required to have a Smartsheet license to view and update the task.
Weakness: No Effort-Based Planning
Smartsheet scheduling is very simplistic. It is based on start/end date and predecessors. You cannot:
Fix the duration, so the duration is constant if the start/end date or level of effort changes.
Fix effort, so the duration adjusts based on the number of resource assigned to the task.
Load level a project, which automatically schedules tasks so available resource hours are not exceeded.
Weakness: No Inter-Project Dependencies
You cannot define and track inter-project dependencies automatically. In the past, I’ve created a section of the schedule to list external dependencies but this had to be manually maintained. The supplying project manager had to notify me if the dependent task was slipping.
Weakness: Doesn’t Support Constraints
Smartsheet doesn’t allow defining constraints for tasks, such as: must finish on, or must start on.
Scope Management
There isn’t out-of-the-box scope management functionality. You could build a separate sheet for each project listing the in-scope and out-of-scope items.
Stakeholder Management
There isn’t any stakeholder or change management functionality. You could build a partial change management solution by building a separate sheet to list change impacts and mitigation steps (i.e. training and communication).
In Conclusion
Smartsheet’s strengths are:
Ease of use
Flexible low code solution
Licenses are only required for project managers
However, I cannot come up with any business case where Smartsheet would be the correct solution for a company heavily invested in Salesforce. Such a company should use a native PSA or scheduling tool for their project management. Or even, better non-native tools integrated to Salesforce.
I struggle to come up with a Smartsheet business case for any business. There are better scheduling tools (MS Project, etc.). If you are interested integrated project management and reporting, then I would install a true PMO or PSA tool. If you need a customized solution, I would build on a platform with a true relational database, not on the Smartsheet platform.
Maybe the niche is small companies without any IT staff which needs a quick temporary project management solution. It would definitely fit this bill, but to do anything but the most basic functions will require someone to learn Smartsheet admin functions. Also, the company will quickly outgrow Smartsheet.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Customized Timeline/Milestone Process by AppSolu is a Salesforce app which measures the time between record updates. It is intended to be used as a management measurement tool for standard processes. For example, to measure the average time it takes to close an opportunity. As for project management, I believe it would only be applicable for measuring standard repeatable projects like field installations. It wouldn’t be very applicable to custom projects like an internal re-engineering effort or software development project.
Customized Timeline/Milestone Process (CTMP) is a much better tool than Flowdometer which is also available on the Salesforce AppExchange. CTMP has a more user-friendly interface and considerably more functionality. However, Flowdometer is free while CTMP is not.
Pricing
CTMP costs $500/company/month or $6,000 per year.
Review Methodology
To review CTMP, I reviewed the demo and the available documentation. I also installed CTMP into a sandbox environment and setup my own opportunity measurements.
You can also perform your own assessment by installing CTMP into a sandbox. Please note that you must first install an app called Asynchronous Process Manager and then install CTMP.
You are essentially setting up an automated stopwatch. You define when a timestamp should be recorded for specific updates to Salesforce records. You can then generate alerts and create reports based on these timestamps.
You basically define the object to monitor, markers which are when the timestamp should be recorded, and actions to be taken when a marker is triggered. The user interface to setup all of this is very user-friendly.
An example would be:
Select Opportunities.
Define a marker to measure the elapsed time for each opportunity stage. For example, when the value of the ‘stage’ field changes.
Define an action triggered by a marker. For example, send an email alert when an opportunity becomes qualified.
Advanced Features
CTMP has some really nice advanced features which make it very easy and flexible.
Record Filters – Define filters to limit the types of records that are measured. For example you could only measure opportunity stages for a specific account.
Triggered Actions – The timestamp marker can trigger a variety of actions to be taken. In essence, they have built a nice user interface to define custom record-triggered flows. There are even options on how to time the action. For example, you can schedule the action to trigger when the marker starts/ends or relative to its target time. Some of the actions are:
Send an email.
Update a record.
Lock/Unlock a record.
Aggregate Measurements – You can define an aggregate measurement (i.e. count, sum, average, etc.) with a custom grouping for a marker. For example, you could measure the average time to close an opportunity grouped by account.
Targets – When you define a marker it is very easy to define a target goal, which is then displayed on the record page to let users know if they are on schedule. In fact, you can easily add several Lightning Web Components to an object’s Lighting Record Page so users can see the CTMP stats.
Dynamic Target Dates – The target date can be set based on the start of the process or it can also be set based on the value of certain fields. For example, you can set a target date of an opportunity stage to be X days from the opportunity’s close date. Available fields are things such as: close date, last stage change, last modified date, etc.
Timestamp Based on Child Records – Not only can you trigger the timestamp based on a field in the main object being updated, you can also trigger the timestamp based on child record updates. For example, if you create projects as child records of your opportunities, you can create a marker that completes when a project is added to the opportunity.
Record Workflow – You can also build a Timeline Task which is a workflow related to the Salesforce object. The user will follow the workflow in the CTMP Lightning web component on the record page. The workflow options are: upload file, review content or answer questions. Timestamps will be taken at each step in this workflow.
Weaknesses
I only found one weakness: a lack of standard reports and dashboards. Two very basic reports are provided with the app and no dashboard. The report types have already been created so it should be very easy to create your own custom reports and dashboards.
In Conclusion
If you want to measure your standard Salesforce processes you should consider Customized Timeline/Milestone Process. The advanced features and user-friendly interfaces make it worth the price versus the free Flowdometer.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Kickboard is the virtual equivalent to a facilitated meeting where participants place Post-It notes on a whiteboard. Salesforce describes it as a digital transformation tool, but I would use this for a variety of project planning such as, initial project timelines and payoff matrices. This would be especially useful for virtual teams.
It only lacks one major feature of Miro: you can’t draw on the whiteboard, you can only add and move Post-It notes
Kickboard Pricing
It is a free app provided by Salesforce Labs. This is compared to Miro’s business pricing of $16/user/month.
How Kickboard Works
Static Background Image
The Kickboard whiteboard consists of a static image which you can create from provided templates or uploading your own image. You create cards (i.e. Post-It notes) with a description and place them on the board. You can use different colored cards of just like Post-Its.
Auto-Categorization
The niftiest feature is an auto-categorization capability. When you create the whiteboard, you can define categories based on either the color of the card or its position on the whiteboard. When you’ve populated the board you click the “Categorize” quick action and it applies the category values you’ve defined. You can then create a report and export the card information with the categories.
Multiple Board Templates
Kickboard comes with two templates with several boards that have pre-defined category rules. You can easily customize the category rules.
External Collaboration
Another great feature of Kickboard is that it can be used to collaborate with team members not on Salesforce. You create a Experience Cloud website and can then share the whiteboards.
In Conclusion
I definitely plan to use Kickboard in the future. I wish I had known about it during COVID, as it is a great alternative to Miro.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Splash Announcements is a neat little app for broadcasting announcements to all your Salesforce users. It would be a great app for a corporate-wide software release or for Salesforce admins.
Splash Announcements allows you to display a message to Salesforce users when they open their Salesforce app. This would be useful as a communication tool for a project implementation or software release. It would also be very useful for Salesforce admins to communicate to their users.
Strengths
Very easy to use
Ability to create rich text messages with graphics and links
Tracks user’s acknowledgement of the message
Messages can be scheduled with a start and end date
Free
Weaknesses
The only weakness is that the messages are all or nothing. It doesn’t support specific distribution lists. Therefore, every user of the apps that have installed the Splash Announcement tab will see the message. So, it is only good for company-wide type announcements.
If you wanted to use Splash Announcements only for a specific group, you could control the distribution of the messages by only giving the specific groups permission to view any Splash Announcement messages through permission sets. Or, you could only add the Splash Announcement tab to a specific Salesforce app.
Splash Announcements Pricing
Free!
How Does it Work?
1) An admin adds the Splash Announcements tab to the relevant Salesforce apps. It is added as the first tab so the users will see the message as soon as they open the app.
2) A Splash Announcements admin creates a message with a start and end date.
3) The user reads the message and clicks a button acknowledging they’ve seen the message.
4) Management can monitor the acknowledgements in a report to ensure everyone has gotten the message and determine if additional communication is required.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Projecleo is reviewed against 250+ project management software requirements on a downloadablespreadsheet. Projecleo 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.
Projecleo is a very simple Salesforce-native professional services automation (PSA) tool. The target market would be a Salesforce company looking for a inexpensive tool and that can run their projects simply using a checklist of tasks without any scheduling. Projecleo captures hours and hourly rates, so it captures the base data needed to create an invoice, but it doesn’t have any functionality to create or track invoices. It is severely lacking the cost and resource management functionality found with most PSA tools.
Projecleo is also intended for internal projects that aren’t billed. So it could also be used by company as an internal PMO tool. However, it lacks some key functionality around status reporting, program and release planning that most companies would want.
Unfortunately I couldn’t find any unique piece of functionality that would make Projecleo an ideal fit for a certain customer base. It has weaker versions of standard functionality found in the other PSA and PMO tools. Its only differentiator is its low price.
Download Projcleo Evaluation Spreadsheet
Click here to add the Projcleo Excel spreadsheet to your basket and continue reading. Visit the basket page to complete the download.
Projecleo is $7/user/month. This is the most inexpensive PSA tool I’ve found, except for the free Salesforce Labs apps.
Projecleo 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 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, but be aware there is very little documentation for this app. The demos on the AppExchange don’t even show the app screens. The only way you can evaluate it is to load it into a sandbox environment:
No communications functionality other than use of Chatter.
Cost Management
Extremely limited cost management functionality. You can enter an hour budget for a project, create rate cards and track actual hours charged to the project.
Weakness: No Monetary Budget
You can’t create a budget by rolling up tasks and their costs. You can’t plan expenses or record actual expenses. There isn’t even a field to manually enter a dollar budget. You can only enter a total hour budget.
Weakness: Doesn’t Invoice Customers
You could calculate the amount to be billed from reported hours and rates, but it doesn’t capture expenses so those would have to recorded in another system. You would have to build reports to calculate the billable amounts.
Integration Management
The only integration management functionality it has is a dashboard which lists the project stages and and various metrics related to tasks. It doesn’t even have fields to report the project status (i.e. red, yellow or green).
Weakness: No Project Status
You could customize the project object so you could report project status (i.e. red, yellow, green) for scope, budget and schedule, but this is standard functionality which should have been included.
Weakness: No Project Security
Every user of the app has read/write access to every project. I couldn’t even find any permission sets so that access to hourly rates could be restricted.
Procurement Management
No procurement management functionality.
Quality Management
No quality management functionality.
Resource Management
There really isn’t any resource management functionality. You can create a list of project team members. However, you can’t allocate their time to the overall project. All you can do is assign them tasks with associated hours. There isn’t any way to plan resources by comparing resource needs against availability.
Risk Management
No risk management functionality.
Schedule Management
The only schedule management functionality is creating milestones and then associating stand-alone tasks with the milestones. While tasks have start and end dates, there isn’t any way to schedule them using dependencies.
You can also create task groupings of child tasks under a parent task. However, this doesn’t serve the need of a work breakdown structure because you can’t visualize the hierarchy. The parent and child tasks are listed on the same level as a static list.
Weakness: No Gantt Chart or Kanban Board
There isn’t a Gantt chart or a Kanban board. All you have is a list of tasks and milestones. The tasks aren’t even listed in chronological order.
Weakness: No Rollup of Tasks
There isn’t any rollup of either task hours or % complete to the project level. You’ll have to create reports to total the task hours and related costs for budgeting purposes. The project % complete calculation is based on the number of milestones completed regardless of the number of hours associated to a milestone. This makes is impossible to do CPI or EAC calculations.
Scope Management
No scope management functionality.
Stakeholder Management
No stakeholder management functionality.
In Conclusion
I just completed the review and I wasn’t able to list one strength for Projecleo. If you are trying to find an inexpensive PSA or PMO tool, I’d recommend one of the free Salesforce Lab tools:
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Leankor appears to be a lite version of a PSA tool geared towards field service projects. It has a nice Kanban board and a great Gantt chart for scheduling. However, it is lacking the invoicing, cost management and resource management of many of the other PSA tools.
Leankor is reviewed against 200+ project management software requirements on a downloadablespreadsheet. Leankor 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.
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.
Leankor is geared towards field service projects. It is a lite version of a PSA app focused on the scheduling process. It has a nice Kanban board and a great Gantt chart for scheduling. However, it is lacking the invoicing, cost management and resource management of many of the other PSA tools.
I’m at a loss to figure out where Leankor would be the best choice relative to the other PSA tools that are available. It is much more expensive than the other tools, which have much more functionality. The only key differentiator I could find is the ability to perform effort-based scheduling, which most Salesforce scheduling tools don’t have.
Download Leankor Evaluation Spreadsheet
Click here to add the Leankor Excel spreadsheet to your basket and continue reading. Visit the basket page to complete the download.
Leankor’s published price on the AppExchange is $75/user/month. This is much higher than other PSA tools that have achieved higher scores: Kantata $45/user/month, Certinia $40/user/month.
Evaluate Leankor Quickly
Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Leankor quickly and thoroughly.
Like most Salesforce project management apps, Leankor doesn’t have any change management functionality related to training or communication.
Cost Management
I had difficulty evaluating Leankor’s cost management functionality (see methodology section for details), therefore I’m not going to go into a lot of detail here. I believe there are two major weaknesses: doesn’t issue invoices, doesn’t support daily/weekly rates.
Weakness: No Invoicing
It allows you to mark an individual expense as being invoiced. However, I didn’t see any functionality which would allow you to generate a charge based on actual hours worked and publish an invoice. Let alone, any functionality to track the status of an invoice.
Weakness: Doesn’t Support Daily/Weekly Rates
A daily or weekly rate is popular in consulting and I would imagine would be popular for field service work. The hourly rate to be charged a customer is recorded in the Resource Assignment record. I did not see any place to record a daily or weekly rate in the Resource Assignment record.
Integration Management
I didn’t find any strengths that would differentiate Leankor from other PSA tools, but I did find a few weaknesses: lacks project-level security, and change orders.
Weakness: Lacks Project-Level Security
It appears you can define whether an individual user can read or edit the Kanban cards are a specific project’s board. However, I didn’t find any other project-specific security settings. Therefore, all users will have visibility to all projects. You can’t create confidential projects. Access to financials and resource data is controlled with permission sets, so these rights will be applied globally and can’t vary by project.
Weakness: No Change Orders
It doesn’t support issuing and approving change orders when the scope, schedule or the cost of the project changes.
Procurement Management
No procurement management functionality to speak of other than recording project expenses.
Quality Management
The only quality or testing functionality it has is the ability to record acceptance criteria on a Kanban card. This field is a single plain text field, so you won’t be able to record individual test results for each criteria.
Resource Management
I had difficulty evaluating Leankor’s resource management functionality (see methodology section for details), therefore I’m not going to go into a lot of detail here. It has the standard functionality to view a resources assignments against availability and to re-assign resources when they are overallocated. It does appear to have some gaps in the resource management functionality: tracking skills, issuing resource requests, soft booking resources, and project-level allocation.
Weakness: Doesn’t Track Skills
It lacks the ability to define skills and to assign various skills to a resource. It does have the ability to define resource types, but this isn’t as granular as skills.
Weakness: Can’t Issue Resource Requests
The resource management all seems to be handled at the task level. I didn’t see any functionality where a project manager can issue a resource request, say an Apex developer at 100% for three months.
Weakness: Can’t Soft Book Resources
It doesn’t have the ability to soft book a resource and indicate which assignments are soft booked in the resource management view. Therefore, the resource manager won’t have the visibility as to which assignments can be easily re-assigned because they are only soft booked.
Weakness: No Project-Level Allocation
All the resource allocations appear to be done at the task level. There doesn’t appear to be the ability at the beginning of a project to assign a resource to the project at X% of their time.
Risk Management
You can designate a task as a risk. Overall, it has standard risk management functionality with a risk log and the ability to record mitigation plans.
Schedule Management
Schedule management is Leankor’s greatest strength. It has an excellent project Gantt chart and Kanban board. The Gantt chart supports all standard planning functionality: dependencies, critical path, etc. It’s one key differentiator is that is supports effort-driven scheduling. Its only Gantt chart weakness is that it doesn’t support task constraints (i.e. Must Finish On, Must Start On, etc.).
Strength: Effort-Driven Scheduling
Leankor is one of two native Salesforce scheduling tools which support effort-driven scheduling. You even have the option with each task as to whether to use duration or effort-driven scheduling.
Duration-driven scheduling is the default for most tools. This keeps the task duration constant regardless of how many people are assigned to the task. In effort-driven scheduling the duration of the task will shorten as you assign more people to the task.
Strength: Inter-Project Dependencies
It has a very cool feature for creating inter-project dependencies. You create a custom Gantt chart board which contains the predecessor task of Project A, and the project plans for the dependent projects (Project B thru n). You can then create any type of dependency: SS, SF, FF, FS.
Weakness: Lacks Releases and Sprints
Leankor appears to be oriented to an Agile approach, however, you can’t define releases or sprints. I’m sure you could create a dedicated Kanban board for a release or a sprint, but I don’t believe you’d be able to report at the release or sprint level.
Weakness: Can’t Assign Tasks to External Users
There isn’t any functionality to assign a task to a non-Salesforce user through email or a community portal. Other apps support making external assignments and even allowing the external user to update the task when it is complete.
Weakness: No Task Constraints
Leankor doesn’t support assigning constraints to tasks, such as: Must Finish On, Must Start On, Start As Soon As Possible, Finish As Late As Possible.
Scope Management
There aren’t any scope management capabilities.
Stakeholder Management
There aren’t any stakeholder management capabilities.
Leankor 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 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.
WARNING: I had a very tough time scoring the Cost Management and Resource Management functionality for Leankor. So if you are interested in Leankor, you should validate my scores in these areas. The difficulty in scoring arose from:
I lacked financial and resource management rights in the test drive.
The Leankor free trial failed to load to my sandbox environment. A help request to Leankor support went unanswered.
There aren’t any Leankor demos or documentation related to invoicing or cost management.
There are very few documents or demos related to resource management.
I had to resort to going through the Leankor custom objects to discern the capabilities.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Best Salesforce Scheduling Software
A project manager reviewed thirteen native Salesforce scheduling software solutions against 200+ requirements, the top four tools are reviewed in detail. The detailed review highlights the key differences between the apps. Additional research can be performed by accessing individual detailed reviews of each app, and downloading the spreadsheet listing the 200+ requirements.
All of these project scheduling apps are native Salesforce scheduling software solutions. External non-native project scheduling tools can also be integrated with Salesforce. I will do reviews of the non-native options in future posts.
These top four Salesforce scheduling software solutions were selected based on their schedule management scores. However, I’ve included the scores for the other processes because two of the apps are professional services automation (PSA) tools that have good scheduling capabilities.
None of these tools have the level of project scheduling functionality found in Primavera or Microsoft Project. If you are a construction firm or have very complex schedules you’ll have to look outside of Salesforce for your scheduling solution.
Plan releases – Only Inspire Planner has the ability to define releases and group tasks by release.
Create project from sales funnel – Since Certinia and Kantata are PSA tools, they have the ability to generate a project from a sales opportunity as part of the client onboarding process.
Synch with Salesforce tasks – I think it is very important that employees can see all of their assigned tasks in one place. Employees are not going to open multiple tools each day to view/work their tasks. If your company works tasks in Salesforce, then you’ll want Kantata or Inspire Planner which synchs their tasks with Salesforce, so employees can work from the Salesforce home page and don’t have to open Kantata or Inspire Planner. If your employees work from an external calendar (i.e. Microsoft Outlook) then this requirement is not relevant, and you can build an interface to the external calendar.
Assign a task to a team queue – Only Inspire Planner and Klient allow a task to be assigned to a team queue, so anyone on the team can see and complete the task.
List inter-project dependencies – Only Certinia will allow you to define dependencies between projects. This usually occurs in large programs and IT projects. For example, another project is upgrading a software tool, so you’re project can’t start your testing until that upgrade is complete.
Rank tasks/user stories in a product backlog – If you want to run Agile projects within your PSA tool, this is critical functionality missing in Certinia and Klient PSA. The product owner needs to maintain a list of user stories and prioritize them within the backlog. I personally, don’t include user stories in my project schedules so this would not be an issue for me.
Kanban board – If you want to run Agile projects within your PSA tool, this is critical functionality missing in Certinia. Overall, Inspire Planner has the best Agile project solution. Klient PSA has a lot of Agile functionality but it has one severe defect: I wasn’t able to re-order tasks on the Kanban board to list them by priority.
Assign checklists to tasks – In order to keep schedules clean, it is useful to be able to associate a detailed checklist to a task rather than having to detail all the steps as tasks in the schedule. Certinia does not offer checklists.
Update task assignments on a project template – If you create new projects from standard templates, you’ll want to assign the template tasks to standard roles and once you create the new project assign an employee to the role. You want to have all the tasks assigned to that role updated at once when the employee is assigned. You don’t want to have to open all one hundred tasks to assign employees. Certinia and Klient PSA don’t support this functionality.
Task constraints – Inspire Planner is the only app that supports the task constraints: Must Finish On and Must Start On. However, it does not support the constraint: As Late as Possible.
Assign tasks to external users – Klient PSA doesn’t support assigning tasks to a non-Salesforce user and then allowing them to complete the task without a Salesforce license.
Fixed-effort task scheduling – Please note that Klient PSA is the only tool to support effort-based scheduling. The rest only use a fixed duration model. Suppose you have a task that takes 40 hours, 5 days and only one person is assigned. You then assign a second person, the duration will remain 5 days on the other tools. It will only automatically adjust to take 2.5 days using Klient PSA.
Evaluate Scheduling Tools Quickly
Purchase the scorecard spreadsheet (fit/gap analysis) with over 200 project management requirements to evaluate scheduling tools quickly and thoroughly.
Inspire Planner is the best project scheduling tool and also the cheapest. You can only justify the higher cost of Certinia or Kantata if you are going to use their PSA functionality.
NOTE: Klient PSA lists its pricing as $49/user/month including the Salesforce licenses. I’m assuming they are referring to selling Klient PSA along with a Platform Cloud license to a company without Salesforce. For a company with Salesforce licenses, I’m assuming the price would be the difference without the Platform Cloud licenses ($25/user/month).
Other Considerations
Certinia
Certinia used to be named ‘FinancialForce’ and offers an entire suite of apps which would result in the most comprehensive solution if all the apps were implemented. Here is the list of other available apps:
Billings & Receivables
ERP Cloud
Revenue Management
Services CPQ
Procurement
Services Analytics
Order & Inventory Management
ERP Analytics & Reporting
Subscription & Usage Billing
Professional Services Quoting
Inspire Planner
Inspire Planner is transitioning from Salesforce Classic to Salesforce Lightning in Spring 2024.
A user of Inspire Planner has reported some performance issues with slow response times. You’ll want to test this for yourself.
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 for each app I’ve reviewed so you can perform your own analysis. Here is the blog page where you can find the detailed app reviews. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.
I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheets to suit your needs. Each requirement was rated as either:
Certinia Scoring Notes
I wasn’t able to install a copy of Certinia to test all of the functionality first hand. I had to rely on demos and documentation.
Kantata Scoring Notes
I wasn’t able to install a copy of Kantata to test all of the functionality first hand. I had to rely on demos and documentation.
There are two versions of Kantata:
SX which is a native Salesforce app.
OX is an external applicated which interfaces with Salesforce.
I wasn’t able to clearly differentiate the SX vs OX functionality from the demos and documentation. Therefore, you’ll need to work closely with Kantata to determine if you should purchase SX or OX.
Salesforce Scheduling Software That Didn’t Make the List
Many of the Salesforce project scheduling tools that didn’t make the short list are missing the following key functionality:
Don’t allow unlimited task hierarchies to define the work breakdown structures. Put more simply: you can only have a few levels of tasks.
Don’t support task dependencies, such as, Start/Finish, Finish/Finish or Start/Start.
Don’t provide a critical path.
Don’t synch tasks to Salesforce tasks.
The Salesforce Agile Accelerator didn’t make the list because it is a specialized Kanban board tool to support Agile software projects. It doesn’t even have a project Gantt chart. However, it should be considered if you are looking for an alternative to JIRA to support your Agile teams.
Here is a list of the Salesforce project scheduling tools that didn’t make the cut, with their schedule management score. You can research these other tools on my comparison page, and then follow links to the individual review posts.
Conclusion
If you are just looking for a native Salesforce project scheduling tool, then you should strongly consider Inspire Planner as it has the best functionality and the second-lowest price.
You should only consider Klient PSA if you need fixed-effort scheduling. But even then, if you need fixed-effort scheduling you’ll probably need the more advanced features you would find in Microsoft Project or Primavera. These more advanced tools will allow you to do resource load leveling where the entire project is rescheduled based on resource allocations. But Project and Primavera are not native Salesforce tools so you’ll be looking at having to implement an integration.
If you are a professional services firm, you should lean towards Kantata as it has the best scheduling solution within the PSA tools. You should consider Certinia for scheduling if you are interested in implementing their entire suite of back-office apps.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Best Salesforce PSA Tools
This post compares what I personally consider the four best Salesforce professional services automation (PSA) tools: Certinia, Kantata SX, Mission Control and Precursive PSA. After evaluating these top Salesforce PSA solutions against 200+ project management requirements, I highlight the key differentiators to help you choose the best PSA software for your organization. You can also download the complete PSA software comparison spreadsheets to apply your own priorities and perform a thorough PSA tool evaluation.
The percentage represents how well each Salesforce PSA tool satisfies the 250+ requirements, with all requirements weighted evenly. Kantata SX has the highest overall score among these professional services automation Salesforce solutions and leads in both resource and schedule management capabilities, making it one of the best PSA software options available.
Customized PSA Tool Shortlist
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.
When conducting a PSA software comparison, cost management capabilities are crucial. The largest single gap is that Certinia does not support invoicing customers directly within the app. Certinia creates a data set for an invoice, but the data has to be passed to an external invoicing system. All three of the other Salesforce PSA tools allow the creation, issuance and tracking of customer invoices within the apps. You must purchase Certinia’s Billings & Receivables app to generate invoices or use your financial system.
The second biggest gap is that Kantata SX does not support daily rates and overtime charges. This seems extremely odd, considering the breadth of Kantata SX’s functionality. I wasn’t able to install a copy of Kantata SX, so if you like everything else about Kantata SX, you might want to confirm this gap for yourself.
Resource Management Key Differentiators
When evaluating the best PSA software options, resource management capabilities are essential. All these Salesforce PSA tools do a great job of identifying resource needs and matching people with the correct skills to resource openings. However, professional services automation Salesforce solutions differ in several secondary but important functionalities.
Percentage allocations of resources to a project – All but Mission control allow you to simply assign a person to a project for a percentage of their available time. This is useful in the early stages of the project when you can’t allocate people to the task level. All of these PSA tools also support assigning a person to individual tasks and rolling those hours to an overall project allocation.
Project-specific access – The ‘Control access by individual project’ and ‘Project-specific access to financial data’ are related to setting user’s access rights on a project-by-project basis.
On Certinia and Mission Control, if a user has access to one project, they have access to all projects. This could be a problem if you want to have some confidential projects.
On Kantata SX and Pecursive, you can block a user from specific projects and even vary whether they have read or edit access on a project-by-project basis.
Only Kantata SX allows you to control a user’s access to financial data on a project-by-project basis. The other three apps support global access rights, so if a user can see financials on one project they can see financial data on all projects.
Automatically assign available resource – Certinia, Kantata SX and Precursive each have functionality which either assigns or suggests the best suited resource with availability for a resource opening.
Publish resource opening for people to apply – Certinia and Kantata SX support publishing resource openings to all users, so that users can apply to the open position.
Differentiate between soft and confirmed allocations in resource management view – All four PSA tools have a resource management view which shows total allocations for each resource, so the resource manager can match available resources to open needs. However, only Kantata SX and Precursive use visual queues in this view to differentiate between ‘soft’ allocations versus confirmed allocations. This is important to a resource manager because ‘soft’ allocations can be shuffled around without consequences.
Schedule Management Key Differentiators
Schedule management is a critical component when comparing PSA software options. I believe Kantata SX has the best scheduling tool of all the Salesforce PSA tools evaluated. In fact, it is nearly as good as the dedicated scheduling app Inspire Planner. It’s only missing the ability to define constraints to tasks, such as Must Finish On or Must Start On. The gap related to synching with external calendars can probably be addressed easily using a third-party app or custom interface.
Mission Control’s inability to support unlimited task levels within the schedule would disqualify it for my use. However, it is a very popular app, so this gap must not be a severe limitation for most users.
Please note that none of these Salesforce PSA tools support effort-based scheduling. They all use a fixed duration model. Suppose you have a task that takes 40 hours, 5 days and only one person is assigned. You then assign a second person, the duration will remain 5 days. It won’t automatically adjust to take 2.5 days.
Unlimited task levels – Mission Control has a severe limitation where you can only organize tasks into three levels: milestones, actions/tasks, checklists. This severally limits how you organize the work breakdown structure in your schedule.
Calculate critical path – Only two of the PSA tools will show the project manager the critical path on the Gantt Chart. I find this extremely useful to prioritize the tasks which must be completed on schedule.
Synch with Salesforce tasks – I think it is very important that employees can see all of their assigned tasks in one place. Employees are not going to open multiple tools each day to view/work their tasks. If your company works tasks in Salesforce, then you’ll want Kantata SX or Mission Control which synchs their tasks with Salesforce, so employees can work from the Salesforce home page and don’t have to open Kantata SX or Mission Control.
Synch tasks to external calendars – I think it is very important that employees can see all of their assigned tasks in one place. Employees are not going to open multiple tools each day to view/work their tasks. If your company works tasks in external calendars like Google Calendar or Outlook, then you’ll want Certinia or Precursive which synchs their tasks with the external calendars.
Support all dependency types – Only Certinia and Kantata SX’s scheduling tools support all dependency types (finish/start, start/finish, start/start, finish/finish). Mission Control supports all dependency types except start/finish which is rarely used. Precursive only supports the finish/start dependency which is the most common type.
List inter-project dependencies – Only Certinia and Mission Control will allow you to define dependencies between projects. This usually occurs in large programs and IT projects. For example, another project is upgrading a software tool, so you’re project can’t start your testing until that upgrade is complete.
Rank tasks/user stories in a product backlog – If you want to run Agile projects within your PSA tool, this is critical functionality missing in Certinia and Mission Control. The product owner needs to maintain a list of user stories and prioritize them within the backlog. I personally, don’t include user stories in my project schedules so this would not be an issue for me.
Kanban board – If you want to run Agile projects within your PSA tool, this is critical functionality missing in Certinia.
Assign checklists to tasks – In order to keep schedules clean, it is useful to be able to associate a detailed checklist to a task rather than having to detail all the steps as tasks in the schedule. Certinia does not offer checklists.
Update task assignments on a project template – If you create new projects from standard templates, you’ll want to assign the template tasks to standard roles and once you create the new project assign an employee to the role. You want to have all the tasks assigned to that role updated at once when the employee is assigned. You don’t want to have to open all one hundred tasks to assign employees. Certinia and Mission Control don’t support this functionality.
Hide internal tasks from clients – All the PSA tools have the ability to share the schedule externally with clients. However, only Mission Control and Precursive allow you to mark certain tasks not to be shared with the client.
Assign tasks to external team members – Mission Control is missing the ability to assign a task to a non-Salesforce user and have them update the task when it is complete. This is important if you work with lots of external team members and you don’t want to have to buy them all Salesforce licenses.
Salesforce PSA Tool Evaluation Spreadsheets
These are RFP-level fit/gap analysis spreadsheets utilizing 200+ requirements. Use these spreadsheets to understand the detailed functionality of the tools on your shortlist and to perform a side-by-side comparison.
The published pricing for all four PSA tools is similar. However, Certinia and Kantata SX pricing is contract-based and customized. Therefore, I suspect most companies will end up paying significantly more than the minimum published price for Certinia and Kantata SX.
Other Considerations
Certinia
Certinia used to be named ‘FinancialForce’ and offers an entire suite of apps which would result in the most comprehensive solution if all the apps were implemented. Here is the list of other available apps:
Billings & Receivables
ERP Cloud
Revenue Management
Services CPQ
Procurement
Services Analytics
Order & Inventory Management
ERP Analytics & Reporting
Subscription & Usage Billing
Professional Services Quoting
Mission Control
Mission Control only supports very detailed planning, where you are creating tasks with specific assignments and hours and then rolling up these values. While this is a strength for companies that track every minute of a person’s time, I’ve never found this level of planning realistic for the business improvement and IT projects I manage. I think for general applications, project managers will find the level of detail required by Mission Control overwhelming.
Salesforce PSA Tool 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 for each app I’ve reviewed so you can perform your own analysis. Here is the blog page where you can find the detailed app reviews. Here are detailed instructions on how to use the spreadsheet to weight requirements and compare multiple software packages side-by-side.
I gave all processes and requirements equal weights, but you can adjust the scoring weights in the Excel spreadsheets 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. To select the four best PSA tools, I focused on the following processes:
Cost Management
Resource Management
Schedule Management
Certinia Scoring Notes
I wasn’t able to install a copy of Certinia to test all of the functionality first hand. I had to rely on demos and documentation.
Kantata SX Scoring Notes
I wasn’t able to install a copy of Kantata SX to test all of the functionality first hand. I had to rely on demos and documentation.
There are two versions of Kantata SX:
SX which is a native Salesforce app.
OX is an external applicated which interfaces with Salesforce.
I wasn’t able to clearly differentiate the SX vs OX functionality from the demos and documentation. Therefore, you’ll need to work closely with Kantata SX to determine if you should purchase SX or OX.
Precursive Scoring Notes
Precursive has two products:
OBX which is a Kanban board.
PSA which provides resource and cost management.
I scored PSA integrated with OBX’s Kanban board.
Salesforce PSA Tools That Didn’t Make the List
Here is a list of the Salesforce PSA tools that didn’t make the cut, with their overall score. You can research these other tools on my comparison page, and then follow links to the individual review posts.
Conclusion
After this comprehensive PSA software comparison, Kantata SX emerges as the overall best Salesforce PSA tool based on my requirements and scoring methodology—if your budget permits. For organizations seeking a complete professional services automation Salesforce ecosystem, Certinia deserves serious consideration.
However, I highly recommend downloading the detailed PSA tool evaluation spreadsheets for each solution so you can prioritize requirements based on your organization’s specific needs. Before making your final decision, install these PSA tools in a sandbox environment to validate my findings against your critical requirements.
The right professional services automation software can dramatically improve your operational efficiency, resource utilization, and project profitability. Take the time to find the best PSA software for your specific business model and workflow requirements.
If you found this PSA software comparison useful, please leave a comment. Also send me a comment if you find any errors or missing requirements.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Klient PSA is reviewed against 200+ Salesforce project management software requirements on a downloadablespreadsheet. 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.
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.
Download Klient PSA Scorecard
Click here to download the scorecard. It is an Excel spreadsheet with over 200 requirements scored for the tool.
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 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.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Certinia Professional Services Cloud (PSC) is reviewed against 200+ Salesforce project management software requirements on a downloadablespreadsheet. 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 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.
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.
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 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.
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 completesuite of Certinia apps
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Precursive PSA
Precursive PSA is reviewed against 200+ project management software requirements on a downloadablespreadsheet. 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.
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 Score
52%
Communications Management
9%
Cost Management
62%
Integration Management
48%
Procurement Management
0%
Quality Management
17%
Resource Management
88%
Risk Management
58%
Schedule Management
62%
Scope Management
0%
Stakeholder Management
17%
Customized PSA Tool Shortlist
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.
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 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.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Precursive OBX is reviewed against 200+ project management software requirements on a downloadablespreadsheet. 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.
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.
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.
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).
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.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Projectivity is reviewed against 200+ project management software requirements on a downloadablespreadsheet. 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 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 Score
10%
Cost Management
23%
Resource Management
43%
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.
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 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:
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.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Salesforce Professional Services Automation (PSA) is reviewed against 200+ project management software requirements on a downloadablespreadsheet. 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.
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.
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.
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 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
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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.
Perform a Kantata Review Quickly
Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Kantata SX quickly and thoroughly.
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 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.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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 downloadablespreadsheet. 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.
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.
Evaluate Resource Hero Quickly
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.
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 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.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Varasi Program Management is reviewed against 200+ project management software requirements on a downloadablespreadsheet. 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.
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.
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.
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 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.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Resource Availability Checker is found to have a serious bug that makes it unusable.
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.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
DayBack is reviewed against 200+ project management software requirements on a downloadablespreadsheet. 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.
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?
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.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Neilon Project Management is reviewed against 200+ project management software requirements on a downloadablespreadsheet. 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 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 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 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.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Task Manager app is reviewed and found to provide a nice task view but to have limited overall usefulness.
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.
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’
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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 downloadablespreadsheet. 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 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.
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 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 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.
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.
Strength: Detailed Work Breakdown Structure
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.
Strength: Documents Components
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.
Weakness: Lacks Detailed Scope Definition
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.
Weakness: No Change Orders
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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 downloadablespreadsheet. 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 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 Score
34%
Communications Management
14%
Cost Management
9%
Integration Management
29%
Procurement Management
0%
Quality Management
17%
Resource Management
57%
Risk Management
0%
Schedule Management
58%
Scope Management
6%
Stakeholder Management
17%
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 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 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.
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.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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.
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.
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:
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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.
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.
Customized PSA Tool Shortlist
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’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.
Evaluate Mission Control Quickly
Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Mission Control quickly and thoroughly.
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.
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.
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.
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.
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 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.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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 Score
0%
Communications Management
0%
Cost Management
0%
Integration Management
0%
Procurement Management
0%
Quality Management
0%
Resource Management
0%
Risk Management
0%
Schedule Management
0%
Scope Management
0%
Stakeholder Management
0%
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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.
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:
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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.
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.
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 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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Project Lifecycle Pro is reviewed against 200+ project management software requirements on a downloadablespreadsheet. 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.
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 exceptscheduling 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 Score
39%
Communications Management
27%
Cost Management
31%
Integration Management
56%
Procurement Management
13%
Quality Management
17%
Resource Management
31%
Risk Management
83%
Schedule Management
25%
Scope Management
94%
Stakeholder Management
71%
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 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 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.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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 downloadablespreadsheet. 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 Score
51%
Communications Management
9%
Cost Management
68%
Integration Management
61%
Procurement Management
13%
Quality Management
17%
Resource Management
55%
Risk Management
83%
Schedule Management
56%
Scope Management
0%
Stakeholder Management
29%
Customized PSA Tool Shortlist
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.
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.
Evaluate the Cloud Coach Salesforce App Quickly
Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Cloud Coach quickly and thoroughly.
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 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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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 downloadablespreadsheet. 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.
Customized PSA Tool Shortlist
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+ 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 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.
Evaluate Milestone PM+ Quickly
Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Milestone PM+ quickly and thoroughly.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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.
Evaluate Salesforce Agile Accelerator Quickly
Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate Salesforce Agile Accelerator quickly and thoroughly.
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 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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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.
Evaluate Project Management Software Quickly
Purchase the scorecard spreadsheet with over 200 project management requirements to evaluate any project management software quickly and thoroughly.
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.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
This is a comparison of SalesforcePMT 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 exceptscheduling 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.
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.
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.
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.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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.
Free Software Selection Process Template
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
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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.
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.
FlexibleRollup 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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and 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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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.
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”
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”?
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.
“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.
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.
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.
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.
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.
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.
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 Ihave 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!
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
Project Charter Template and Guide
A free project charter template with a supporting guide to project charters from a professional project manager (PMP). Includes a Microsoft Word project charter template for large projects and one for small projects.
The project charter is simply the “charter” (e.g. contract) between the project team and management to ensure everyone is on the same page. The project team is agreeing to deliver the business case benefits within the schedule and costs outlined in the charter. Management (e.g. sponsor and steering committee) are signing off on their commitment to fund, staff and support the project. The rest of this post will provide a guide to creating a project charter with free project charter templates for download at the end of the post. Sections are organized around the sections of the project charter templates.
You MUST have a charter for every project. I’ve included a one-page template for small projects which can entail as little as a 15 minute meeting with the sponsor. Large projects will require the larger template and may take weeks to develop and get approved. While it can be quick and straightforward, don’t skip the step of getting the understanding of the project in black and white. Also don’t skip the step of getting approval in writing. First, to get true understanding and consensus things must be in writing. People walk away from conversations with different understandings and memories of what was discussed. Second, nothing makes a busy manager pay attention and squirm more than asking them to put their signature on something. I’ve had managers avoid me for weeks as I chased them down to sign the charter. They simply didn’t want to have to make the commitment. If they don’t want to sign, that is a flag that something is amiss and it needs to be addressed.
You must have a charter for every PROJECT. I’ve seen overly eager project managers try to create charters for everything. A project is a significant effort with considerable cost. Timelines are measured in months. Budgets are measured in hundreds of thousands and millions. If something can be accomplished using existing people in your department in a week, than it isn’t a project requiring an approved charter.
I made the mistake once of working on a project without a charter, and I’ll never do it again. A project being run by another consultant was floundering. The first release was due in thirty days and the consultant hadn’t even started testing. I was asked to coordinate the testing effort and try to hit the release date. The first thing I asked for was the project charter. They didn’t have one. I should have walked away immediately. But the project had been running for over six months, there were regular meetings with the steering committee and hundreds of thousands of dollars had already been spent. I thought it was way too late to create and ask the steering committee to approve a project charter. If I’d insisted, I would have saved myself a month. As the release date approached, the consultant started communicating the details of the release functionality to the steering committee. Guess what? No one on the steering committee wanted what was being delivered and the project was scrapped.
Project Charter Template Sections
Description
Pretty obvious what this section is for. Provide a brief description of the project. Try to tell a story and make it a little engaging. Lead off with the issue or opportunity: “In this modern age of cell phones, state regulations require an employee personally visit a home and provide a final warning before disconnecting electricity for non-payment. Using text and phone calls (as is being done by other utilities) will be far more effective and will reduce labor costs of $3.6M per year.” Other topics to cover are:
Purpose – Why is the project needed? For example: “Besides being more cost effective, using cell phone communications are much more effective in helping customers to make a payment to avoid disconnection. In 60% of cases, no one is home when the employee visits the residence. Having more effective communication will reduce disconnects, and thus increase customer satisfaction.”
Business Case – The next section will contain the detailed business case numbers, but add some prose to tout the benefits: “With only an investment of $300K to automate the text and phone calls, we can reduce labor for disconnect visits by $300K per month thus achieving a one month payback.”
Goals/Metrics – Describe how project success will be measured: “The reduction in unnecessary disconnects is expected to increase overall customer net satisfaction scores by 1 point. Expect to eliminate 6K disconnect visits a month.”
Expected Deliverables – Briefly describe what will be built. For example: “An automated system that will generate text and phone call reminders at 7, 2 and 0 days from scheduled disconnection.”
Business Case
The level of detail required for a project business case has varied considerably among my clients. This section of the charter is intended to be a back-of-the-envelope summary of the business case. There may be much more detailed spreadsheets supporting these numbers. Typically, the minimum requirement is a positive return on investment (ROI) and a payback of under three years. Measure the three year benefits from the time the benefits start to be realized (typically at the end of the project), not from the start of the project. It is important to also note which costs and benefits will occur once and which will be ongoing. Don’t list every little cost or benefit. Use the 80/20 rule and list the 20% of items which make up 80% of the cost/benefits and group the rest under “Miscellaneous”.
During the Plan Phase, these numbers should be extremely high level. In some cases, you might want to mark some items as approximate or even “TBD”. By the end of the Analyze Phase, these numbers should be as exact as they are going to get.
Key Assumptions
Notice the title of this section is KEY Assumptions. Only list assumptions which you’ve made which will have a significant impact on the business case and have a reasonable probability of being wrong. You don’t want obvious or highly unlikely assumptions: “Assuming a meteor doesn’t destroy the city.” This list can be fairly long during the plan phase, but should be very short at the end of the analyze phase once you’ve dug into the assumptions. An example could be: “Assuming a 1 point increase in overall net customer satisfaction because the net customer satisfaction for customers disconnected in the current month is 5 points lower than customers that have not been disconnected.”
Scope
This is simply what you’ll be working on, where you’ll be working on it and with whom. Often, the “Out of Scope” portion is what generates any pushback from management, so you’ll want to include a brief explanation of why it is out of scope. For example: “All accounts marked as using life-saving medical equipment will be out of scope for this effort, for the obvious reason that their electricity cannot be disconnected and we do not want to unnecessarily alarm them.”
The grouping of scope items by people, process and technology is simply a prompt for you to consider all aspects of the scope. For people, you should consider which part of your organization is impacted, or which types of customers. For process, you should consider key scenarios that are out of scope like the example above of a customer dependent on a breathing assistance. For technology, you should consider which systems will be impacted.
Schedule
This will only list the high-level milestones for the project. The most important one at the beginning of the project will be when the first release will be ready. During the plan phase this is an educated guess, but any experienced project manager or IT architect should be able to sense whether a project will take 3, 6, 12 months or longer. Under promise at the plan phase and give yourself a minimum of 20% contingency. So if your team estimates a six month project, put seven months in the charter.
By the end of the analyze phase, this schedule for the first release should be locked down and the team should be held accountable for delivering against the schedule. Timing for later releases will be estimated but should include the minimum 20% contingency since they haven’t been fully analyzed. Besides, the charter is usually obsolete after the first release. Later release timing and budget tracking will be handled in the steering committee presentations. Any major budget increases will be handled by change orders.
Dependencies
This is a list of things that must be delivered by others to keep your project on schedule and are outside of your control. Usually, these are other software projects for systems you’ll be using or that interface with your systems. For example: “There is currently a freeze on building new text messaging campaigns while the automated text messaging system is being upgraded. If the upgrade is not completed by January 30th the start of this project will have to be delayed.”
Project Team
At the end of the plan phase when the charter is first developed, this is a list of the team needed for the analyze phase. At the end of the analyze phase when the charter is finalized, this is a list of the larger team needed to build the first release. I’ve populated standard team roles as a starting point, but there obviously could be other roles on your project. The developer roles probably won’t be staffed until the end of the analyze phase. The percent-of-time column is included because many of the team members will work for the steering committee members, and this is confirmation that they approve dedicating these people to the project.
Primary Stakeholders
Stakeholders are either impacted by the project or should have a say in the project design. Again, use the 80/20 rule and list the 20% of the organization which will feel 80% the pain from this project. For example: “Customer Service – All 500 customer service reps will have to be made aware of the automated messages and be trained on how to respond to customer inquiries.” There are other tools which will track all the stakeholders and impacts.
Unique Risks
Notice this is titled UNIQUE risks. This is a pet peeve of mine. Every time I sit down with a client to write a charter, they want to add a risk that says something like: “May not be able to fully staff the project due to conflicting priorities.” The problem with this risk is that it is obvious and every project has the same risk. Besides, it is the job of the sponsor and the steering committee to set the priorities and assign the necessary resources. The risks listed here should be unique and they should be actionable so that they can either be mitigated or avoided. For example: “State regulators may not approve eliminating personal notifications at the residence. Plan to avoid this risk by presenting the results of similar programs in other states to the regulators and gauging their consent prior to launching a pilot program.”
Governance
You shouldn’t have to spend too much time on this section. In most cases, this section should be the same for every project. Just need to get concurrence on how big a change needs to be for the team to get approval. Also, I like scheduling steering committee meetings at key stages of the project when decisions need to be made, rather than a standing monthly meeting. Often, the standing monthly meetings become stale if there aren’t any major decisions to be discussed.
Approval
This section is used to record the project approvals by the: product owner, project manager, sponsor and steering committee members. I’ve found it is best to meet one-on-one with the sponsor to go over the charter. Also, I distribute the charter to the steering committee once I’ve incorporated the sponsor’s input, and hold a meeting a few days later to review the steering committee’s input. I ask people to simple send an email approving the charter and then attach the emails to the document. It is critical to get forma approval for the first version of the charter at the end of the plan phase. However, I don’t usually ask for formal approval for the final version at the end of the analyze phase unless there are significant changes.
Reference
This section just stores some document information and a log of version changes.
Free Project Charter Template
The Large Project Charter Template is in Microsoft Word format and is a project charter for ERP implementations or other large software projects. The Small Project Charter Template is a PowerPoint slide and is ideal for small improvement projects like Six Sigma projects.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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.
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:
What is the high-level business case? Roughly how much will it cost and will the benefits justify the cost.
What are the high-level software requirements? A list of what the software needs to do. Identify any key interfaces with existing systems.
Should we make or buy? Meaning, do you buy software off the shelf or code it from scratch. In many projects you may have a combination of both.
Do we need external help? Determine if you need a consultant to help with the Plan Phase. You may need a strategy consultant like McKinsey to help develop the high-level business case. You may need a project management expert to help with the make vs. buy decision? If you are buying an off-the-shelf software you will probably need some professional guidance on installing the software.
What is the high-level timeline? Logically group functionality into releases and determine how long will it take to complete each release.
Should we proceed with the Analyze Phase? Determine who needs to be dedicated to the team to perform detailed analysis. Determine how much the Analyze Phase will cost and how long it will take. Get approval to spend the money and staff the team.
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:
Detailed current state review. Review how things are currently done, so that you can identify: detailed software requirements, required process changes, improvement metrics and who will be impacted.
Future process. Design the future improved process as this will drive software requirements.
Detailed software requirements for the first release. This will be everything the developers will need to know to design and build the software. Detailed requirements can be documented just-in-time for later releases.
Finalized business case. Develop final cost and benefit estimates that will be used to measure the success of the project.
Software selection. If using off-the-shelf software, the software is selected and purchased at this point.
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:
Software install. If using new off-the-shelf software, the software vendor and perhaps a supporting consultant will join the project now that contracts have been signed. They will have a series of questions that will need to be answered to perform the initial install of the software so that detailed configuration can start.
Technical design. For custom builds, the technical team will be designing the software components like databases, user interfaces and system interfaces.
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:
User Training. Train the users on how to use the new software and any new processes.
Software Migration. The new code or new software has been built and tested in non-production environments only accessible by the team. Now the new build needs to be moved into a training environment to support training and then into the production environment where it will be used.
Communication. Everyone impacted by the new software needs to understand the changes, how they will be impacted and any actions they have to take.
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:
Product Owner – This is your role. It can go by different names like program manager, VP/Director of X Project but it basically means that you are the person upper management is holding responsible for the success of the project. You will be responsible for prioritizing the software functionality.
Sponsor – This is the manager whose budget is paying for the project. Since they are paying for the project they obviously have the final say on all major decisions. They also have to be kept informed so they are confident their money is being spent well.
Steering Committee Member – These are managers of the departments which will be severely impacted by the project. They will have to be convinced to lend resources for the project, either to help the team or to be trained. They will need to be consulted on key project decisions that impact their departments.
Project Manager – This is a person experienced at running software projects, which will help you by running the day-to-day aspects of the project. On Agile projects, this role can be called a scrum master. On small projects, the same person can fill both the product owner and project manager roles.
IT Architect – This is the IT person who will guide the team on key project technical decisions and designs. They will make decisions like: what language to code in, how to structure the database, etc. On large projects there may be several different types of architects specializing in different technologies.
Business Analyst – This is the person documenting the processes, business case and requirements. They ensure the developers have the information they need to build great software. In many cases, the business analyst will also be testing the initial build and creating training.
Developers – These are the people actually coding the software or configuring the off-the-shelf software. These are the people that make the magic happen, and all the roles above are basically supporting roles so the developers can create great software.
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:
Development – This is where the developers do their coding or configuration work. This is chaos and unstable. There can be dozens of developers making changes simultaneously.
Testing – There will be a formal process to periodically move changes from the development environment to the testing environment. The changes will be moved for a specific release so that it can be tested. This environment will be much more stable, and should reflect the changes going into the next release.
QA/Training – This can be one or two environments, that serve several purposes. In between releases it is a duplicate of the production environment with either a full copy of data or a near-full copy of data. It is used to investigate production bugs. Just prior to a release, this environment is updated with the new code that has passed testing and is setup with data to be used for training.
Production – This is where the work is done. All end users must be trained and ready before release changes are moved to this environment.
Some key environment concepts you need to understand as manager of the project are:
Setting up these environments is a lot of work. If you are working on existing software, these environments will already be setup. But if you are building/installing new software then these environments need to be created.
Access to these environments is controlled separately. The project team works in the Development, Testing and QA/Training environments. Separate usernames and logins will need to be created for each environment. Developers should not have access to Production. All changes should flow from Development to Testing to QA/Training and then Production with checks and re-checks occurring along the way.
Migrating changes between environments is a lot of work and easy to mess up. Migrating the changes three times is practice for IT to make sure they can do so quickly and smoothly. In fact, IT should be automating the process of migrating the changes as much as possible so the automated process is perfect for the move to production. After each migration, a test has to be run to confirm the changes were migrated to the environment correctly.
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.
Brian Springman is a Charlotte, NC freelance business consultant with over twenty years of experience. He specializes in program and project management. He is a certified project management professional (PMP). He is also a certified Salesforce Administrator and ISV Partner.
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.