Leading the Digital Business Culture
Engaging Citizens through Technology
Forging Ahead with DevOps
Agile Isn't Just for Dev Anymore: Five Steps to Achieve IT Ops Agility
DevOps Changes Everything: From Your Body to the Government
Kurt Collins, Director of Technology Evangelism and Partnerships, Built.io
Diving into the Depths of DevOps
Pauly Comtois, VP DevOps, Hearst Business Media
Measuring DevOps - Where are you on the cheat scale?
Peter Waterhouse, Senior Strategist, CA Technologies
Taming the Cultural Transformation Beast during DevOps Evolution
Amit Gupta, Associate VP-Delivery, Ness Digital Engineering
Identifying and Dealing with Hidden Dependencies in Software Systems
In any software, a dependency pops up when one module in an application, say A, depends on another module or environment, say B. A hidden dependency like this is not apparent. And to discover such dependencies, one has to dig into the source code of the respective module. Below listed are few risks of the most common dependencies and how to cover them:
1. Teams that adopt multiple agile platforms do not have the flexibility to work across teams as efficiently as their co-located counterparts, and this eventually slows down the response time which in turn slows down the releases. Teams must make their dependencies transparent to stress their importance.
2. Large and medium-scaled organizations usually release multiple versions planning sessions for a particular product. But running them at the same time, or in a sequence and in different locations tend to increase the risk that the teams will overlap their work and not plan for any dependencies which may occur.
3. Few organizations and groups plan for dependencies by adding more time to their estimates as a buffer. But organizations and teams must ensure that these estimates are based only on complexity and effort and do not waste time. Doing so will help in revealing the things that are making progress difficult.
4. In other organizations, which are more substantial have a sophisticated infrastructure and team tend to be highly dependent on one another for delivering work which is like a chain effect where one team’s work begins only after the other finishes. As organizations are in favor of adopting Agile, enterprises must carefully examine their structure to ensure it is optimized. This will thereby reduce risks and dependencies, instead of exaggerating them.
5. Team members usually allow blockers and dependencies to get in the way of completing work. If team members predict that a dependency, a blocker with key features or user stories will hamper their work, they should stop the job there and then. It is the responsibility of every individual to refrain from committing to a work they know they cannot complete.
Visualization is a must
Organizations can manage and tackle issues related to dependencies and risks only if they can plan for them. Teams can use roadmaps for identifying any risk factors and evaluate dependencies continuously. Opting for a platform that enables real-time visualization into dependencies is one way to prevent time wastage and get an in-depth understanding of the right details at the right time.