QualityNet Jira and QualityNet Confluence will be briefly unavailable on Wednesday, July 24, 2024, between 8:00 PM ET and 9:00 PM ET while the team performs an AMI update.  If you have questions or concerns, please reach out to us in Slack at #help-atlassian.

Human-Centered Design

Blog

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

In 2016, NN/g asked Agile practitioners at the UX Conference to share tips or techniques that have contributed to the success of their Agile projects. They received 125 responses from professionals in USA and Singapore. The respondents worked in various-size companies and held different job responsibilities, ranging from UX designers and developers to product owners and project managers. From this, these Top 10 Key Tips for Successful Agile Projects were developed. Here is the first of the most popular techniques reported by Agile professionals:

Tip #1. Allow time for release planning and story mapping.

Respondents reported that spending time at the start of projects to properly plan for releases is worth the investment:

“Place more effort in planning, design, and specification.”

“Be involved at the earliest stage.”

“Spend more time in the planning phase and then focus on refinements and tweaks. Get buy-in before starting the project.”

“Block out business time early, get sign off on everything.”

“Do proper and extensive planning in the beginning of the sprint. Allow sufficient time to deal with inevitable blockers.”

Collaborating with stakeholders from the beginning allows teams to develop a shared understanding and a common vision for their projects. This shared vision guides team members throughout the project, helping them prioritize user stories and make the right trade-offs along the way.

Some teams employ story mapping during release planning to help stakeholders collaborate with other team members in creating the product backlog. This activity often uncovers new opportunities and helps teams group and prioritize user stories.

UX involvement in release planning keeps the focus on the broader context, identifies knowledge gaps that require future research, and gathers information (e.g., by running appropriate user studies) to inform team decisions before the project begins. When teams allocate time for discovery work and research at the beginning, they reduce wasted effort later on.

“Include the discovery process before Agile kicks off for chartering, persona development, and story mapping.”


Source: NN/g

  • No labels