CD is a natural evolution from CI and Agile software development practices. However, the cultural and operational challenges to achieving it are much greater.
The methodologies now employed by Agile and Scrum development teams began in Toyota Plants in Japan. Read on to see how these ideas got their start in America.
On an Agile team, every team member should be able to do every task, right? Actually, you can benefit from a mix of specialists and multi-skilled individuals.
Remote jobs are awesome. Unless the person having to manage five people on four continents. Try these five strategies for getting the most out of your remote team.
When should you start performance testing depends on whether you want to go with the Agile approach or the Waterfall approach. But how do you know when to do which?
In this article we look at the mechanics of a Sprint, and at how team members are expected to collaborate in order to produce a release-quality increment.
Defining your testing scope is key to any development process. Read on to find out how to effectively and consistently define one to keep dev teams on time and on task.
Time passes, technology evolves, but principles of mastery remain the same. See how you can derive some Lean and Agile concepts from old sword fighting teachings.
From the Center of Excellence to Waterfall to Agile and open source, performance testing has seen a lot of changes in its short life. We're now in CoE 2.0.
Real-time test management tools help aid effective collaboration among Agile team members—which is vital for prioritizing bugs in a risk-based software testing approach.
Failing fast isn't unique to DevOps but it's an incredibly important strategy. Practicing failures and mitigating resulting issues is a standard function of DevOps teams.
Mockito2 has made improvements over its predecessor, including the ability to mock final classes. Its new opt-in feature lets you take mockery to a new level.
The best PO might have other responsibilities and be too busy to represent stakeholders. This model is found in enterprises where legacy subsystems are being replaced.
