Kantata Cloud (formerly Mavenlink + Kimble) provides project management and collaboration software for small to mid-sized professional services companies. Features include resource management, project dependencies, time and expense tracking, file sharing, versatile user permissions, private messaging, planning and reporting.
N/A
Rally Software
Score 7.7 out of 10
N/A
Rally Software headquartered in Boulder, Colorado developed the Rally agile software development / ALM platform which was acquired by CA Technologies and rebranded as CA Agile Central. After CA's acquisition by Broadcom the software was once again rebranded as Rally.
It is appropriate and even exceeds expectations 90% of the time. It makes project tracking very easy and visually accessible for most cases. The only occasion where Mavenlink came slightly short was for a special project that required more interaction options among project members. I am certain there are ways to work around that issue, but we did not find them.
Rally is well suited to help outline the specific tasks of a project, create timelines, indicate progress/status of tasks and provide views of team members' workloads. My team used it for our weekly stand up meetings in order to update one another on our progress, and our manager used it as a way to determine who had capacity for additional tasks. It facilitated our transition to a more agile work environment and we used it to implement 2 week "sprints".
With Mavenlink when starting to assign tasks to people, set deadlines and milestones, and add files to our projects we can look at it all from a variety of perspectives, including a task tracker view and a Gantt chart view
Through Mavenlink each project also includes an activity stream where we can view all project details as they come up, as well as an activity feed for all the projects it is linked to.
There are dashboards that provide friendly and useful metrics at the team, program and portfolio levels which help get an easy and quick visual representation of what's going on.
Story management made easier, It offers a quick way of quickly entering a number of user stories without losing the overview, by just typing the title and selecting a few attributes directly in the overview screen.
Sprint management is seamless in CA Agile Central . It allows you to drag stories from the backlog to the sprints and back again. When a story is dragged into an sprint, it automatically checks the velocity for that sprint and indicates how many more story points can be chipped in. No more manual checking needed by scrum master with respect to allocation and team velocity.
Though CA Agile Central has many inbuilt apps, but it also has an App-SDK that allows you to build free app extensions using JavaScript and HTML. So, as per their needs, teams can customize & build various apps & dashboards.
Dashboard is an awesome feature which allows you to select and drag panels with all kinds of graphical information about the current sprints and releases.
It offers tremendous support for scaled Agile & almost all scaling frameworks are supported specifically tuned to SAFe .
CA Agile Central includes several applications but it also integrates well with Jira, Confluence, Jenkins, Eclipse, Subversion, IBM, HP, Salesforce.com and many other products to allow users to organize projects to their specifications. So you can still use Jira at a team level & CA Agile Central at the program & portfolio level for efficient tracking & management.
The custom tags are very helpful in segregating the user stories based on the project needs. Even though it's a very small feature, it is very effective ( you will realize why specifically if you are using Jira).
CA Central Agile enables agile delivery with ease and provides comprehensive features to track time-boxes, Work In Progress items of the forecast increments.
Backlog management is hassle free since you can either drag and drop your user stories to the desired position on the backlog, or change a setting and manually enter priorities as a number.
User management is pretty basic and could be better. For example more filters and reports and more ability to do mass updates.
The report generator is very, very basic and is not WYSIWYG. It has limited filters to generate reports. Often a Scrum master will need to export data to Excel or a tool like Crystal Reports to get enhanced reporting capability.
Although the company I currently work for does not use the product I have recommended that we do switch to Mavenlink. We will be opening some new sites internationally this year and I can see that Mavenlink would be a great product for us to use
I think Mavenlink is the most robust and best project management tool out there for an organization like ours. However, some of our staff feel like it isn't as user-friendly as it could be. From a Director point of view or a Project Manager point of view, Mavenlink is exceptional. From the point of view of a task-doer, it could be more visually appealing. Also, the mobile version isn't great.
Great UI, recent refresh was terrific. Great graphs and metrics, inline editing for updates, and a multitude of views on sprint progress make for a great team collaboration experience. There is also an active community and forums so that if you do need help, it is readily available
Very good integration with Google apps. Some complexity is called however in the synchronization between Google Tasks and Maven links tasks. This can sometimes lead to duplicate records in Google Tasks. It has been dissolvable that becomes cumbersome if not properly curated.
The screens render relatively quickly but many actions that you would expect to require a single click require multiple clicks and pop-up windows. The extra windows and clicks make the product feel ponderous.
Mavenlink support is fantastic! Any issues that arise are always handled quickly and efficiently. Granted, we haven't had many issues to report. Typically, my team tends to only reach out to support if they need assistance remembering how to do something or asking about an improvement. We had Mavenlink build an integration when we first started using the software, and the support team worked hard to listen and improve the integration.
I've had to use support only one time and my issue was eventually resolved but not because of my ticket--because others complained about the functionality taken away so they brought it back. My ticket was never answered or addressed. So I can't really say much for the support factor for Rally.
We prepared questions in advance, and our trainer was an expert in what Mavenlink was and wasn't able to do. We were able to have multiple people trained at once.
The training was very well-organized. We were able to send questions in advance so the instructor knew what to cover, and the brought up related topics to maximize the usefulness of what they were teaching us.
It more or less confirmed that we are using it the way they had in mind. We were hoping for a epiphany in terms of how we could use it better.
They also want to be a go to source for agile processes and have an online resource center. It’s not that great but had a couple of nuggets. It hasn’t really helped us too much and we are not too far off from the classical interpretation of agile.
I would recommend training, in particular for organizations that multiple on-going projects. The product seems optimized for larger, more complex teams and getting proper training on how to configure, administer and use the system would be beneficial
Dedicate as much internal time to the implementation effort as possible, even if you're using a 3rd party or Mavenlink services. Your team knows your processes the best
Implementation of RALLY services and program satisfaction among various group,... 1) Dev Outcomes: How were our resiliencies, development, learning & practitioners “make them do the work,” but that they ask you to do it “in a way like before. 2) The Ops group: Just wish to make sure any change won't break current production envirements All the stake holders has to be on the same page
We have since switched over to JIRA and let me tell you, it was probably the best decision we have made as a company. We chose Mavenlink based on promises from the sales team about future roadmap work that really never happened. We thought Mavenlink would easily integrate with our billing software but we couldn't have been more wrong. We ended up never utilizing Mavenlink invoices as they don't even allow you to fully customize your invoices that go out to clients!
It was a close race between Jama, JIRA and Rally. We decided to go for Jama as a requirements management tool and use Rally for Agile projects. The cost was another factor that made us select Rally.
Manvenlink is perfect for showing expenses and income over time and across people.
Manvenlink is adaptable for the integration and automation of the processes of each of our projects in order to optimize resources and improve operational performance.
Mavenlink allows us to determine if our projects are profitable or not, as well as save significant time by automating components such as recurring tasks and having templates, among other things.
Manvenlink is advantageous for our operations due to its simple portfolio management of our projects: manage several projects at once and receive a complete perspective of the development of each one at a glance.
Manvenlink kindly provides us with robust discussion threads, access restrictions, and built-in document management, allowing us to contextualize communications.
it helped organizing many of the processes management use to communicate tasks with engineers, and provided detailed charts on the speed/blockage during any iteration
with time Rally became the main tool we used to track and report tasks/defects in our projects, but frequent service outages made it very hard to continue consider as a reliable solution
too much features is good, but for engineers a few features (User Stories section, iterations, defects, and Kanban boards) are necessary and the rest is just noise
