Throughout the hundreds of conversations we have with the people at the companies building the most complex products in the world, a few themes emerge consistently. Building products is exciting, but managing that process is often frustrating. People love contributing to exciting advancements in hardware or software products. They love working on something that could change the way we live our day-to-day lives. What they don’t love is the burden of managing that process, which is where the Jama Product Delivery platform comes in.
For you in your organization, the decision to purchase a Product Delivery tool may be a difficult one. You may be comfortable with your current document-based process, but something tells you that it isn’t working. We are proud of the feedback we receive from both customers and analysts touting how easy Jama is to use, but even with a great tool, change can be hard.
So what does success with Jama look like? For Deloitte it means delivering high quality results consistently on time. For Jackson National Life Insurance, it means reducing defects across the product delivery lifecycle. What could it mean to you? Read on to learn how we help customers get set up for success.
The first step to success with Jama is configuring the platform in a way that will set you and your company up for success. Here are a few things you need to be thinking about before you start your Services engagement as you onboard to Jama. (FYI, I recommend working with our excellent Services Team, they’ll hook you up.)
Have the right people in the room
You will need input from those who will be impacted by the tool. I say impacted rather than use, because the impact of Jama stretch beyond the BA, Engineering, or QA teams. You will need those with decision authority, and also users who will be in the tool every day. Don’t forget about stakeholders and senior management. They may have needs you haven’t even considered.
On that note, have the right goals
You and your team will likely be the primary users of Jama and have your own goals, but consider that your senior manager may have goals that they want to address with a new product delivery tool. Make sure their needs are met and you’ll be sure to get executive sponsorship for your project.
Identify a project to test the configuration
You may have a new project all ready to go in your new Jama environment; however, I would suggest testing on a product that you have built before and you already know the outcome. If your project team is engaged with learning a new tool as well as successfully navigating the many pitfalls of a new product, how can you be certain what works and what doesn’t? It may be the configuration; it may be the product requirements. It is best to isolate these two things to get a real sense of the value Jama provides.
The last thing to consider is how you will let the rest of the organization know that Jama is coming. Obviously the implementation team has been involved in the trial and working with Jama and thus knows about Jama, but have you considered the change management for the rest of the organization.
- What is Jama? We have resources that can help you with this message to your organization
- Your consultant will help you plan the deployment schedule so users know when they should expect to see more
- Who is involved in your product delivery process? Basically who will be impacted by your Jama rollout
- Let everyone know the goals you decided on above and why you are making the switch to Jama
- Lastly, where can they find more information? This could be internally or with help from one of our many training options