- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
There's a notable evolution on the horizon for those of us who manage agile work within the ServiceNow ecosystem. ServiceNow has announced the upcoming deprecation of the Agile Development 2.0 application, a tool that has been a cornerstone of my daily project delivery. While change can be daunting, this move signals a strategic shift towards a more integrated and collaborative future with the introduction of the new Collaborative Work Management (CWM) solution.
A Personal Reflection: My Daily Driver
For anyone like me who lives in the trenches of ServiceNow implementation projects, Agile Development 2.0 has been a constant companion. It has been the backbone of my daily routine for managing stories, coordinating sprints, and keeping development teams aligned. Its straightforward approach has been invaluable in delivering complex projects and driving client success. The news of its deprecation is a moment to reflect on the countless sprints planned and executed within its framework.
The Path Forward: Embracing Collaborative Work Management
Just as the agile methodology itself preaches, we too must be agile in our adoption of new tools. ServiceNow is guiding us toward a more modern and unified approach with its Collaborative Work Management (CWM) solution. CWM is packed with features designed to enhance how teams work together.
This transition is more than just a tool swap; it’s a reminder that the ServiceNow platform is constantly improving. It challenges us to adapt, learn, and grow alongside it. While it's tough to say goodbye to a familiar tool, I am genuinely excited to start using the new CWM solution and see how its features can streamline our workflows and enhance project visibility. We must be agile not only in our development practices but also in our use of the applications that support them.
Final Thoughts & A Call for Community Feedback
The deprecation of Agile Development 2.0 isn't an end, but a necessary evolution. It’s a push for us to embrace a new way of working that promises greater collaboration and alignment. By mastering these new tools, we are not just keeping up with platform changes; we are positioning ourselves to deliver even greater value.
I'm keen to get hands-on with CWM and explore how it can enhance our project delivery. But I am also curious to hear from the community.
Have you already started exploring or using Collaborative Work Management for agile development management? What are your initial thoughts? Is the transition proving to be easy or a significant challenge?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
