Can't live without Rally
March 30, 2016
Can't live without Rally
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Rally Software Development
To specify the same details put in a traditional use case, I use the predecessor/successor relationships on user stories to track dependencies. I use the “Ready” option on the board to indicate completion of an activity. I adjust permissions for those projects to ensure limited access to requirements in different phases. When a phase is complete, I bulk move the stories into the next phase.
Pros
- Agile
- DevOps
- Planning
- Tracking
- Action
Cons
- Context Driven Testing
- Level 1 production support
- Vertical in healthcare
- ROI is cool
- Agile is great
- DevOps is the best fit
I've also evaluated the following agile solutions: ActiveCollab, Agile Bench, Agilo for Scrum, Atlassian JIRA, Pivotal Tracker, SpringGround, Targetprocess. Telerik Teamprocess, VersionOne, ZebraPlan etc.
If it’s time to transition to software that’s specific to your Agile needs, check out some of these options for your team’s communication, reporting, and assessment requirements. Once you find a better tool set, your projects will be within the deadline.
If it’s time to transition to software that’s specific to your Agile needs, check out some of these options for your team’s communication, reporting, and assessment requirements. Once you find a better tool set, your projects will be within the deadline.
Using Rally Software Development
58 - The team represent:
- HIPAA regulations compliance
- Migration to new EMR/EPIC
- Risk analysis and testing
- Meaningful use reimbursement
- ICD-10 clinical coding for billing standards
- Infrastructure support (managed services platform)
- Interfacing with HL7 files
- Virtualization on server & storage
- Data storage and security
- Remote desktop & VDI
- Thin clients & Think clients
- Interoperability solutions
- Secure and remote accessibility
- Mobile device integration
- Backup & Storage
- Healthcare Intelligence
- Tech Service Org
20 - I see the top skill set includes:
- The Scaled Agile Framework®, or SAFe®, provides a recipe for adopting Agile at enterprise scale.
As Scrum is to the Agile team, SAFe is to the Agile enterprise.
- SAFe tackles the tough issues – architecture, integration, funding, governance and roles at scale. It is field-tested and enterprise-friendly.
- SAFe is the brainchild As Ken Schwaber and Jeff Sutherland are to Scrum, Dean Leffingwell is to SAFe.
- SAFe is based on Lean and Agile principles.
- There are three levels in SAFe:
* Team
* Program
* Portfolio
At the Team Level:
- Scrum with XP engineering practices are used.
- Define/Build/Test (DBT) teams deliver working, fully tested software every two weeks. There are five to nine members of each team.
- Rally’s weekly webnar covers the basic practices at the team level.
At the Program Level:
- SAFe defines an Agile Release Train (ART). As iteration is to team, train is to program.
- The ART (or train) is the primary vehicle for value delivery at the program level. It delivers a value stream for the organization.
- EPIC localization
- OnBase upgrade
- UCS swap
- Pure replacement
- Internal sale diffcult
- Budget fight
- License upgrade
- Push to other group
- Expand to infrastructure team
- Get more project swap to agile
Evaluating Rally Software Development and Competitors
Yes - TargetProcess got replaced since it can take some initial time to get to know the tool, there is a learning curve. But it's worth it! takes a while to load on the first use - requires an initial training session to understand all concepts. It is expensive compared to other solutions.
What I dislike the most is that the experience isn't consistent - some data types can be created, renamed and tweaked extensively, while some others are set in stone and baked into the system. I would rather have that it was very scaled down, and that you could create your own data types for cards, instead of having a few baked-in types (Epic, Feature, UserStory, Request, Bug etc). And the cards are tied to metadata such as Release, Project, User, Role, Effort etc., - these cannot be modified and you cannot use them as you wish. You cannot rename card types or create more, delete unused types etc. You have to choose between points or hours as effort metric - but they don't work the same! Some features are not available when you choose points instead of hours. I'd rather it was only a label choosing "p" instead of "h". Multiple things like the above - some stuff is built-in and can't be changed and it can be very confusing. The API is a mess. Everything can be modified in every request, instead of having separate requests for modifying different objects. For instance: you add a comment to a bug, you have to include the user (as an object, not just an id) that authored the comment. However, if you accidentally input the wrong name for the user (but the correct ID), it will actually *change the name* of that user. WTF? The query language is very useful, but has some subtle bugs and inconsistencies.
What I dislike the most is that the experience isn't consistent - some data types can be created, renamed and tweaked extensively, while some others are set in stone and baked into the system. I would rather have that it was very scaled down, and that you could create your own data types for cards, instead of having a few baked-in types (Epic, Feature, UserStory, Request, Bug etc). And the cards are tied to metadata such as Release, Project, User, Role, Effort etc., - these cannot be modified and you cannot use them as you wish. You cannot rename card types or create more, delete unused types etc. You have to choose between points or hours as effort metric - but they don't work the same! Some features are not available when you choose points instead of hours. I'd rather it was only a label choosing "p" instead of "h". Multiple things like the above - some stuff is built-in and can't be changed and it can be very confusing. The API is a mess. Everything can be modified in every request, instead of having separate requests for modifying different objects. For instance: you add a comment to a bug, you have to include the user (as an object, not just an id) that authored the comment. However, if you accidentally input the wrong name for the user (but the correct ID), it will actually *change the name* of that user. WTF? The query language is very useful, but has some subtle bugs and inconsistencies.
- Product Features
- Product Reputation
- Vendor Reputation
- Analyst Reports
- Third-party Reviews
Software applications are changing the world, disrupting established business models and bringing in completely new experiences in areas from travel to banking. In order to compete, businesses need to develop high quality software quickly and reliably. Rally is a leading provider of Agile development software and services, with offerings that complement and expand our strengths in the areas of DevOps and Management Cloud. Every developer dreams of creating truly transformative software that responds to a business challenge extremely quickly. Joining forces with Rally makes this dream a possibility for millions of developers worldwide, and in turn opens up the possibility of a whole new range of experiences driven by software. At the end of the day, this deal is about enabling speed and flexibility, about how we can make the most demanding enterprises truly agile.
The current proof of concept & pilot took too long to finish. How can I make sure my substantial software purchase won't leave me sore into project management, getting company buy-in and change management.
To focusing on the process of evaluating and purchasing software once my needs changed.
I might rule out a vendor or two based on what the RFP response tells me.
Time is money & I need to get the job done quick.
To focusing on the process of evaluating and purchasing software once my needs changed.
I might rule out a vendor or two based on what the RFP response tells me.
Time is money & I need to get the job done quick.
Rally Software Development Implementation
- Vendor implemented
Change management was a big part of the implementation and was well-handled - Due to our production environment is 24x7x365, so any change has to go through a tough change control approve process which took a lot of our time to get Rally implemented. To prevent down time from happening, each implement has to provide detail action plan step by step to make sure even the most Jr. member could get the job done.
- Planning
- Change control
- Compatibility
Rally Software Development Support
| Pros | Cons |
|---|---|
Quick Resolution Knowledgeable team Kept well informed Support cares about my success | Poor followup Problems left unsolved Escalation required Need to explain problems multiple times |
Yes - I get expert help for Rally--wherever I need. You get complete software diagnosis to get to the root cause of your issue, with the premier support option for Rally suites and applications.
Dedicated attention. The Answer Tech will work with me one-on-one to make sure my software issues are resolved. Help from the comfort of my home. I can stay comfortable in my home or office while my Answer Tech works on my computer remotely.
Dedicated attention. The Answer Tech will work with me one-on-one to make sure my software issues are resolved. Help from the comfort of my home. I can stay comfortable in my home or office while my Answer Tech works on my computer remotely.
Once I was running into a tough epic performance issue and luckily I got talk to David Adiiutori who helped me work on the issue until it was fully improved. He is also helped me tap into Rally's passionate network of customers and Rally experts who are ready to answer any of my toughest questions.
Using Rally Software Development
| Pros | Cons |
|---|---|
Like to use Easy to use Quick to learn Feel confident using | Unnecessarily complex Requires technical support Cumbersome Lots to learn |
- Tracking
- Kanban
- Update
- Team work
- Trouble shooting
- Swap
- Down gred
Yes, but I don't use it
Comments
Please log in to join the conversation