|
DevOps and the Culture of Code Migrating an organization to continuous integration requires adoption new processes, tools, and automation. DevOps relies on dramatic culture change to encourage total transparency and collaboration among all project stakeholders.
|
|
|
Automation’s Role in the Fall of Software Testing Has the rise in test automation resulted in product releases of lesser quality? Besides adopting more comprehensive automated scripting, there are process and organizational dynamics to consider.
|
|
|
Agile outside the Development Team Most developers have tough encounters with business-oriented nondevelopers. An expert business analyst shows how an understanding of each others’ perspective will result in project success.
|
|
|
How Agile Has Shrunk Documentation Agile teams enjoy focusing their time on product features while keeping documentation to a minimum. But every team needs to consider what documentation is really needed. How much is enough?
|
|
|
The New Normal for Software Development and Testing Customers expect fast-paced, quality product releases. To meet these demands, you must consider test automation, testing in production, and the extensive use of data and analytics.
|
|
|
Scaling Agile Thinking through Empowered Teams Just because a software team adopts agility doesn’t mean they’ll see results. Being flexible has its benefits, but ensuring that the team is given total responsibility to make decisions may be more important.
|
|
|
Bridging the Bimodal Divide between Waterfall and Agile Most software developers are in either the agile or the waterfall camp. Agile is required to be competitive, but many enterprise processes still rely on waterfall practices for stability. They can coexist.
|
|
|
10 Things You Must Do to Become Truly Agile Agile is not a state of doing; it’s a state of being. Adopting business models on value and learning how to make teams autonomous are both necessary steps to reap the benefit of agility.
|
|
|
Managing Risk in an Agile World Most software projects take great pains to identify and mitigate risks. Traditional risk analysis techniques can be subjective, time-consuming, and complicated. All it takes is a simple spreadsheet.
|
|
|
Reshaping Our View of Agile Transformation Transforming a software development team to agile may not go as planned. The real change requires a phased approach to earn agile acceptance. That mindset must extend beyond the team to the entire organization.
|
|