Scrum.org has announced its new Professional Scrum with User Experience™ (PSU) training course. PSU is a 2-day hands-on course where students with some Scrum experience learn how to integrate modern User Experience (UX) and design practices into their way of working in Scrum.
In this era of Agile development, we hear a lot about different styles, flavors and even frameworks. When you have the experience of facilitating the Agile journey in big as well as small companies, one thing that you will learn is that one size does not fit all. The only thing that seems to be working is what the presenter choose to call polyglot Agile, being able to “speak” different languages with different teams within the same company.
Agile approaches are used to generate quicker feedback that supports continuous improvement. Giving proper feedback is important between Scrum team members or with other project stakeholders. This is however hard and this article provides some hints on how to make it easier.
The default use of an “estimate-driven” approach is pervasive in software development efforts. While estimates can be useful, it is worthwhile to scrutinize our use of estimates, and to seek better ways to manage the development of software when estimates are not appropriate.
Is hiring for an Agile team (team member, scrummaster or product owner) different than hiring for a software development organization that follows another approach? Scrum.org and McKinsey & Company have recently published the results of a joint study exploring the values and traits that make agile teams successful. The goal of this document is to help and guide organizations with concepts and ways to better recruit and coach their teams.