Agile has the manifesto and principles, it focuses on people, clarity for the stakeholders, faster delivery, and happier customers, so why would you need DevOps? John Clapham from Nokia Entertainment in Bristol talked at the Agile Methods in the Finance Sector and Complex Environment conference about what DevOps is and what it has brought to their business.
Scrum.org announced that it is no longer mandatory to do a Professional Software Developer 1 course to do the PSD 1 assessment and become certified.
Organizations have a need for changing the culture when implementing agile. Different approaches exist to spread agile ideas and make changes happen.
Tony Wong, a project management blackbelt, enumerates some practical points on individual procutivity. This article wonders how well these apply to software development and contrasts his list with that of other lists.
Mitch Harper, co-founder of BigCommerce.com, claimed in a recent issue of the Sydney Morning Herald that university education might be the wrong way to become a software engineer. According to Harper, a self-educated software engineer without an university degree: universities leave their students rather unprepared for the realities of being a software engineer.
High-performance teams constitute a mere 2% of the workforce, but Agile processes appear to stimulate the formation of these types of teams. This article discusses Steve Denning's perspective on how such teams can be nurtured in the workplace; it also looks at a recent talk by Ominlab Media's Stefan Gillard on how to select and employ for the formation of high-performance teams.
No one wants programming errors. We have many tools to detect and correct errors in code. We also have a number of techniques we can use to prevent the introduction of errors. In this presentation, Michael Feathers t looksat error prevention while posing a number of interesting questions.
One unfortunate modern truth about software engineering university graduates is that a frightening number come out of school with little to no applicable knowledge about agile software development. A soon to be published undergraduate textbook by Orit Hazzan and Yael Dubinsky is a step towards turning this around.
James Golick and Reg Braithwaite discuss the often overlooked realities of how putting teams into "Crunch Mode" can have undesirable results. The discussion looks at various ways applying pressure to a team often results in putting your project into not better but worse shape and how teams and managers might benefit by taking a different approach.