Agile Development

SCRUM is a framework within agile methodology that organizes work into short, fixed-length iterations called sprints, typically lasting 2-4 weeks. Teams plan, design, develop, test, and review each sprint. Key roles include the Scrum Master, Product Owner, and Development Team. Artifacts like the product backlog, sprint backlog, and events such as daily stand-ups and sprint reviews drive progress. Scrum promotes collaboration, adaptability, and quick feedback.

In agile methodology, an epic represents significant work that the team breaks down into smaller user stories for better manageability. It encapsulates a considerable enhancement or feature, spanning multiple sprints or releases. Just as Google's design sprint process, highlighted in our video, streamlines the creation of designs, epics help teams categorize and prioritize large-scale activities in agile projects. 

While a design sprint focuses on rapid prototype development, like the "sketch" or "prototype" phases, an epic encompasses broader goals, guiding a team's trajectory over multiple cycles.

In agile development, a sprint is a set period during which specific work must be completed and ready for review. Sprints typically last 2 to 4 weeks, allowing teams to break down larger projects into manageable chunks. 

The video highlights the challenges of sprints, ensuring the team finalizes all research and decisions on time. For example, when designing a new feature like a search category screen, decisions on categories must be made promptly to meet the sprint's deadline. This emphasizes the importance of collaborative and cross-functional teams in agile, where designers, engineers, and researchers work closely to make informed, timely decisions and ensure smooth sprint completions. Many organizations overcome these challenges by running user experience sprints ahead of implementation sprints.

In agile methodology, Kanban is a visual tool that helps teams manage workflow effectively. As described in the video, a Kanban board typically consists of columns representing stages of a task, such as things you're going to do, currently doing, and jobs already done.

This board can be as simple as using Post-it Notes, Blu Tack, or sophisticated digital tools. The fundamental principle is moving tasks from one column to another as they progress. For teams handling multiple projects, Kanban boards may feature swim lanes – vertical divisions that separate different projects, ensuring clarity and organization. Kanban offers a clear snapshot of work statuses, facilitating smoother project management and better team collaboration.

In agile development, a spike is a time-boxed task to answer a specific question or address uncertainties. It involves research or prototyping to gain the knowledge needed for reducing risks or making informed decisions. Unlike regular user stories that produce shippable product increments, spikes generate knowledge. Once completed, teams can estimate, design, or prioritize better. Typically used in Scrum or Extreme Programming, a spike ensures the team doesn't commit to uncertain tasks, promoting effective planning and higher product quality.

In Agile development, a user story is a tool used to capture a description of a software feature. In user-centered design user stories are written in collaboration with designers who are familiar with users’ needs. Outside of UCD, they represent the development teams’ best guess. . As highlighted in the video, user stories often follow a format like: "As a [type of user], I want [an action] so that [a benefit/a value]." For instance, "As a job applicant, I want to save my resume information so I don't have to re-enter it every time I apply for a new job." This approach ensures that developers and designers understand the feature's requirements, the desired outcome, and its significance to the user. 

In this Master Class webinar, user-centered design expert and IxDF course editor, William Hudson, will unveil the surprising origins of user stories and how simple changes in their structure can make them much more effective in the form of persona stories.

In Agile development, an MVP or Minimum Viable Product is a foundational concept aimed at validating a product idea with the least amount of work. As emphasized in the video, the MVP approach, rooted in The Lean Startup methodology, isn't about delivering a stripped-down product version but a functional version designed for learning. 

The primary goal is understanding whether the product addresses a genuine problem for a targeted user group. Contrary to misconceptions, an MVP is a moderate product; it's a tool for gathering insights. By presenting the MVP to a select group of early users, developers can obtain valuable feedback on essential missing elements, often realizing that a more straightforward solution than initially envisioned can adequately meet user needs.

In Agile development, Continuous Discovery is a paradigm shift from the traditional project-based approach, emphasizing the constant infusion of customer input into product decisions. As detailed in the video, instead of setting significant project goals based on early research and then relying on that data throughout, continuous discovery advocates for a relentless focus on gathering customer insights.

The aim is not just to answer big questions, such as "What should we be building?" but also to address the minute details that arise during the development process, like button naming or interface design. The risk of neglecting these details is clear: products might align with a broad user need but fail in execution due to overlooked specifics. By adopting a continuous discovery mindset, teams can ensure that both the overarching concept and the granular elements of a product align with user needs and preferences.

Information radiators are prominent tools in agile environments that "radiate" essential data to the team. Essentially, they are big visible charts or displays that provide real-time insights. As mentioned in the video, information radiators can range from dashboards showcasing company metrics, sales numbers, and critical alerts to design artifacts like journey maps or personas posted on walls. 

They ensure that vital information is consistently accessible to all team members. This concept can be adapted for remote teams with tools like dedicated Slack channels updating specific metrics or Google Analytics dashboards shared with everyone. The main goal is to keep everyone informed and aligned at all times.

Agile teams consistently aim for incremental improvements, as highlighted in the video, which discusses the balance between substantial innovative changes and minor adjustments. 

While most adjustments are incremental and designed to refine and enhance existing features, occasionally, deeper insights reveal the need for more significant innovation. For instance, realizing that job applicants lack the necessary skills could lead to introducing training modules – a substantial shift. Such innovations often stem from in-depth research methods like contextual inquiries or diary studies. Therefore, agile teams should prioritize innovation when deep research insights reveal substantial gaps or when there's an opportunity to meet user needs in novel ways. Regularly scheduled retrospectives can be an ideal time to discuss and plan for these innovative endeavors.

The Agile Methods for UX Design course on Interaction Design Foundation is an excellent starting point for those eager to dive deep into agile methodologies. This course provides comprehensive insights into agile practices and their application in UX design. Additionally, Interaction Design Foundation offers many articles, such as the one on agile development, which shed light on various facets of the agile approach. By coupling these resources with real