Process: Agile Development

UXmatters has published 6 articles on the topic Agile Development.

Top 3 Trending Articles on Agile Development

  1. Reasons Why Agile Transformations Fail

    April 25, 2016

    In today’s fast-moving digital landscape, organizations in all sectors and of all sizes are increasingly turning to agile ways of working, with the goal of gaining the speed, flexibility, and responsiveness they need to remain competitive. In fact, Version One’s most recent State of Agile survey found that 95% of software organizations now practice agile development and, in 43% of organizations, the majority of development teams are agile. However, an organization is unlikely to achieve a successful agile transformation simply by rigidly following a defined set of agile strictures. Instead, an agile transformation requires a complete cultural shift across entire teams, structures, and processes.

    In this article, I’ll look at some of the most common reasons behind the failure of agile transformations. My hope is that this information will help your organization to avoid its agile initiatives’ falling foul of the same mistakes and ensure that you’re able to reap all of the rewards the approach has to offer. Read More

  2. Adapting Scrum to a UX Model

    July 7, 2014

    Agile methodology—more specifically Scrum—is an increasingly popular approach to increasing the speed of software development while maintaining flexibility. Scrum works well when an entire team is collocated. Real-time communication happens between team members during daily Scrum meetings. But assume part of a team is operating in a different role, from a different location. Sound challenging? In this article, I’ll try to answer some common questions about user experience and Scrum by exploring the challenges a Development team faced when working with a separate UX team on a Scrum project. I’ll also provide recommendations for UX teams that are part of a Scrum team.

    While the information in this article reflects my experience working with my clients, confidentiality prevents my discussing specific situations, so I’ll instead present a scenario that is based on some challenging situations that I’ve actually encountered in my work. This scenario resembles real situations from a very successful project on which the UX team was not colocated with the rest of the Scrum team. I hope this article will be useful to both UX professionals and software developers working on Scrum projects. Read More

  3. Agile Manifesto for Product Management, Part 1

    June 8, 2015

    In Part 1 of this two-part series on agile development, I’ll first describe the four phases of agile development projects:

    • Phase 1: Conception
    • Phase 2: Definition
    • Phase 3: Planning
    • Phase 4: Deployment

    Read More

Sponsor Advertisement
Continue Reading…

New on UXmatters