What makes an agile team great and why? After coaching a number of teams in Scrum, we’ve now seen a number that, after a some months now, could be considered high performers. Some of these go bad and reject any external criticism regardless of how accurate that might be. Why do these teams go bad? Groupthink might have the answer.
There are many traditional times you can engage users – gathering requirements and user acceptance testing. What are the best times to engage users when you’re in an agile team?
How do you make Design Thinking, Lean UX, and Agile work together. Sprint 0? Design Sprints? Upfront design and planning tends to delay the delivery of value, so there must be a better way to use Scrum but also engage in discovery work at the same time without devolving into parallel design work. Integrating design, user research, and experimentation into Sprints is the key.
We get the best feedback from working software over documentation, says Alistair Cockburn when commenting recently on the Agile Manifesto. View on Prezi: http://prezi.com/x3dgayc1zbpa/?utm_campaign=share&utm_medium=copy&rc=ex0share And while
Who should be your (Scrum) Product Owner? I’ve had a number of these conversations recently with small, boutique software development agencies and even design companies
On one of my recent projects, we were asked to deliver a new Information Architecture for a government website that reflected the depth and breath
So you’ve just finished usability testing in your Sprint and have a pile of changes for your agile team to implement. How do you break down the UX changes that are needed to make a product useful, usable and accessible, into smaller, bite-sized User Stories?
Traditionally, all testing, including assessing how easy real users can use your software, occurs in the very last phase of the project. But what if
The UX Pin have produced a great infographic in an attempt to describe the differences between Lean UX and Agile UX. It’s a great look
© 2019 All rights reserved