Articles → PROJECT MANAGEMENT → Persona In Agile

Persona In Agile

This article describes persona in Agile.

Requirement

The client needs you to create a task management tool. This article develops the persona based on the need to build a task management tool.

Steps

There will be 5 steps for creating the personas.

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

Gather Evidence

Begin by gathering information about your users. This can originate from various sources.

Interviews or Surveys

Speak to real users or send surveys to understand how they manage tasks, pain points, and goals.

Analytics Data

Check usage data from your current task management tool. How often do users create tasks? How many tasks do they typically add in a session?

Customer Support Logs

Look for patterns in support requests that might indicate common frustrations or requests for features like bulk task creation.

User Feedback

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

The example data points are: -

Data Points
Users feel adding tasks one at a time is tedious.
Users manage multiple projects and need to create related tasks quickly.
Efficiency and time management are key pain points for these users.

Analyze And Segment

Once you have your data, categorize 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 needs quick and easy bulk task creation.

Freelancers/Individual Contributors

Juggling multiple clients or projects, looking for quick task input to save time.

Small Teams

Collaborating on shared task lists requires efficient ways to create and assign tasks in bulk.

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

Run feedback sessions or interviews with real users to verify that this persona resonates with their experience and needs.

Make Them Visible

Once you have reviewed and validated the persona, make it accessible to the entire team. This ensures everyone has a shared understanding of the users they are designing for.

Create a Persona Document

This could be a visual document that includes 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 in your team’s collaboration tools.

Refresh

Personas are not static; they should evolve as you get more insights about your users.

Continuous Feedback

Keep gathering feedback from users. If the persona’s needs or behaviors shift over time, update it accordingly.

Quarterly Review

Set a regular schedule (e.g., every 3-6 months) to revisit and adjust 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	**