Personas

Pruitt, John; Grudin, Jonathan

doi:10.1145/997078.997089

Cited by 554 publications

(130 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Once synthesized into personas, this captured data can be used for varying types of task analysis. We agree with Pruitt and Grudin (2003) that scenario-based design also works well with personas. Scenarios involve descriptions of users performing a task, including the relevant details that might drive system requirements.…”

Section: Overview Of the Personas Methods And Related Worksupporting

confidence: 84%

Adapting Personas for Use in Security Visualization Design

Stoll

McColgin

Gregory

et al.

Mathematics and Visualization

View full text Add to dashboard Cite

The development of security visualization applications must involve the user in the design process in order to create usable systems. However, it is all too easy to lose track of the user during the design and development process, even though upfront investment in extensive user requirements gathering has proven benefits. To address this challenge, we adapt a user-centered design method called personas that enables effective requirements capture for varying scopes of requirements-gathering efforts, and, when used properly, keeps the user involved at every step of the process from design to evaluation.

show abstract

Section: Overview Of the Personas Methods And Related Worksupporting

confidence: 84%

Adapting Personas for Use in Security Visualization Design

Stoll

McColgin

Gregory

et al.

Mathematics and Visualization

View full text Add to dashboard Cite

show abstract

“…The first question can be answered with the target markets (Haines 2009), the intended differentiation with competitive products, and the planned support of company strategy (Gorschek and Wohlin 2006). The second question can be answered with the intended product use, characterized with user personas (Pruitt and Grudin 2003), use scenarios (Cockburn 2001;Cohn 2004), and value (Khurum et al 2011), and the intended product scope, characterized with a catalogue of product features (Classen et al 2008). The third question can be answered with the process for developing, evolving, marketing, delivering, and supporting the software product (Cooper 2001) and with a risk management plan (Miller 1992;Carr et al 1993).…”

Section: Product Strategymentioning

confidence: 99%

“…Analysis of segments attractiveness and business strengths are a basis for prioritizing segments and for identifying actions needed to serve them (Gorchels 2006;Haines 2009). Segments are often represented with personas (Pruitt and Grudin 2003) whose key needs are matched with a suitable marketing mix differentiated from competitive offerings (Hauser and Clausing 1988).…”

Section: Marketingmentioning

confidence: 99%

Software Product Management

Ebert

2014

IEEE Softw.

View full text Add to dashboard Cite

Software organizations evolve and maintain software solutions with more than a single development project. The delta specifications and artifacts that result from each project make reuse difficult and challenge a company's ability to innovate. Software product management is a growing discipline for understanding how to productize and align software with company strategy, how to evolve software, and how to coordinate product stakeholders. With product focus, in addition to project focus, planning accuracy can be improved, time-to-market reduced, product quality enhanced, and economic success sustained. This chapter provides an overview on software product management and discusses what today is known about this discipline.

show abstract

“…Between three and seven characters are frequently used and often pictures are used as illustrations (Fig. 2) [13].…”

Section: Personasmentioning

confidence: 99%