Articles → PROJECT MANAGEMENT → Persona In Agile

Persona In Agile

This article describes the persona in Agile.

Requirement

The client requests that you build a task management tool. This article creates a persona based on that requirement.

Steps

There are 5 steps to create the persona.

Gather Evidence
Analyze and Segment
Review and Validate
Make Them Visible
Refresh

Gather Evidence

Start by collecting information about your users. This can come from different sources.

Interviews or Surveys

Talk to real users or send surveys to learn how they handle tasks, pain points, and goals.

Analytics Data

Review usage data from your current task management tool. How often do users create tasks? How many tasks do they usually add per session?

Customer Support Logs

Identify patterns in support requests that suggest common frustrations or feature requests, such as bulk task creation.

User Feedback

Pay attention to current users' comments, reviews, or feedback, especially regarding managing workloads and enhancing efficiency.

The example data points are: -

Data Points
Users find it tedious to add tasks one at a time.
Users handle multiple projects and need to create related tasks quickly.
Efficiency and time management are major challenges for these users.

Analyze And Segment

Once you have your data, classify your users into different groups based on their behaviors, goals, and needs. For example, users of a task management tool could be segmented into: -

Project Managers

Managing large projects with multiple task lists requires quick and easy bulk task creation.

Freelancers/Individual Contributors

Managing multiple clients or projects while seeking quick task input to save time.

Small Teams

Collaborating on shared task lists requires effective methods to create and assign multiple tasks simultaneously.

Review And Validate

Take your initial analysis to your team or stakeholders, and ideally to real users, to ensure the persona accurately reflects the needs and behaviors of the target group.

Internal Validation

Share with product managers, designers, or developers to ensure the persona aligns with product goals.

External Validation

Conduct feedback sessions or interviews with actual users to confirm that this persona aligns with their experience and needs.

Make Them Visible

After reviewing and validating the persona, share it with the entire team. This guarantees that everyone has a common understanding of the users they are designing for.

Create a Persona Document

This could be a visual document that shows the persona's name, role, background, goals, frustrations, and needs.

Distribute it to Your Team

Display it in the office, add it to the project documentation, or share it digitally through your team’s collaboration tools.

Refresh

Personas are not fixed; they should develop as you gain more insights about your users.

Continuous Feedback

Continue collecting feedback from users. If the persona’s needs or behaviors change over time, update it accordingly.

Quarterly Review

Set a regular schedule (e.g., every 3-6 months) to review and update personas based on new evidence or changes in the product’s user base.

Posted By -	Karan Gupta

Posted On -	Friday, November 1, 2024

Query/Feedback

Your Email Id		**

Subject		*

Query/Feedback	Characters remaining 250	**