You read so many books and articles that present how perfectly a Scrum project goes; yet in practice, that is rarely the case. Natalie shares ten lessons that she learned the hard way when she started out as a ScrumMaster. Special attention is given to ways you can avoid those same mistakes.
Agile projects assume that test planning, test creation, and test execution take place throughout a project's lifecycle. So the need for unit testing (and especially automated unit testing) can't be ignored and should be considered as a key responsibility of the entire team—not just the software developers.
Whole team testing makes product quality everyone's business. It can also make people uncomfortable. Matt explains how this new way to approach project quality helps with leading retrospectives, conducting defect analysis, and mitigating project risks.
Without clearly defined roles and responsibilities, actions taken by key project stakeholders may result in project misfires. Kyle shows what you should do to avoid the situation when roles are misunderstood, overlapped, or completely missing.
How do we build more reliable, complex systems in a way that is both pragmatic and economically feasible? Many of the DevOps practices provide the key to building better software that can be maintained, upgraded, and supported from its first installation to its eventual retirement when the system is no longer required.
What do you consider the role of product owner in an agile development project to be? Bob presents a compelling perspective that a product owner has four distinct critical roles that can prove impactful to a team's success.
Can you take the best practices of agile and apply them to your personal life? You bet you can. Johanna Rothman writes on how she manages her personal project portfolio the same way she advise other people to manage their work project portfolios.