The Hidden Requirements: Exploring Emotions with Placebos
The way we feel is important!
All that we think, do, or say is influenced, to some degree, by emotions. Many successful businesses and people recognize the importance of emotional considerations.
The way we feel is important and should be considered!
All software is intended to help solve some problem, and both problems and solutions evoke emotions. Software requirements are simply wants or needs, which often stem from core emotions. Research shows that emotions can affect the acceptance or rejection of software.
The way we feel about software is important and should be considered!
A placebo is designed and used primarily to evoke emotions. Things like sugar pills, false elevator door close buttons, and fake office thermostats aim “to please”, rather than have any other physical effects. Placebo requirements focus on emotions. And so, considering software through the lens of a placebo can help emphasize emotional considerations, and provide a valuable perspective on bugs, ethical design, and much more.
In this session, I support the claims above, suggest some methods to elicit and test emotional requirements, and finally, use placebos as a lens to view software design and testing. Using presentations, demonstrations, and interactive discussions and exercises, we collaboratively explore why “The way we feel about software is important and should be considered!”.
Outline/Structure of the Talk
This is a 45-minute version of a 1-hour talk, or half-day workshop.
The talk consists of: A claim, support of my claim (via an appeal to authority and emotion with quotes; a deep consideration of "the purpose of software"; field research; a study of requirements, wants/needs), and actions to take based on my claim (how to design, develop, and test emotional requirements; and how to use placebos to gain insight into emotional requirements).
A much deeper understanding of 1) why we make software, 2) what requirements are, and 3) what requirements are typically neglected.
Ways to act on this.
PMs, BAs, Devs, Testers, and anyone else that contributes to making software
Prerequisites for Attendees
schedule Submitted 1 year ago
People who liked this proposal, also liked:
damian synadinos - More Than Thatdamian synadinosownerineffable solutions
schedule 1 year agoSold Out!
“What do you do?”
It’s a frequent first question asked at parties, networking events, and bad dates. And sadly, the answer often includes the word “just”.
Perhaps a more interesting question is, “Who are you?”. But, how do you answer? Often, our identity is dominated by our professional image. However, even those that “live to work” have other facets which may contain hidden value.
In this session, Damian uses humor, improv, personal stories, and more to examine our identities, explore our interests, and find inspiration from unexpected sources. Join him to laugh, learn, and “unjust yourself” as you rediscover Who You Are!
Thomas Haver - Develop Yourself and Uplift OthersThomas HaverSr. Application ArchitectHuntington National Bank
schedule 1 year agoSold Out!
In the constant flux of software development, everyone involved in creating new technologies and features must adapt to changes or be left behind. One obstacle facing professional development is lack of support and/or guidance from management. According to a recent survey by Robert Half Finance & Accounting, only 26% of employers allow their employees to attend continuing professional education courses during business hours. However, all is not lost: change can come from within rather than management. Employees can take the reins of continuous improvement and generate positive change for themselves & their organization. In this session, the audience will learn how to implement a robust continuous improvement curriculum that can be integrated into an organization’s culture – one training class, one conference, one professional group at a time.
Chris Ruch - Putting the Customer FirstChris RuchEnterprise Agile ConsultantAgile Rising
schedule 1 year agoSold Out!
Where has the customer gone in large scale enterprise agile frameworks? Customer Collaboration is one of the main tenants of the Agile Manifesto, but it seems that have we lost touch with this concept as we have scaled agile into large organizations. If we look at the SAFe Big Picture, the customer is represented, but only at the end of the process consuming the solution. This talk explores how and why it is important to pull the customer to the beginning and middle of the process and not just the end. This isn't to pick on SAFe -- the customer doesn't appear at all on the graphics for Disciplined Agile, LeSS, and Nexus at all! The concepts and principles explored in this presentation are universal in any large enterprise and can, and should, be applied to to any framework.
Each of the main enterprise agile frameworks today (Disciplined Agile, SAFe, LeSS, Nexus, etc) have a graphic representation of their model, which present an inside-out view of how an enterprise is organized to delivery in an agile fashion. But what do our agile enterprises look like from the outside, from our customers' view point? As agile becomes widely adopted as the way of developing products, there is a growing gap with where new product development ideas are generated and how customer input is integrated into the agile process. Increasingly we are seeing organizations struggling because of a lack of an effective and experienced product management group and even experienced agile coaches not knowing how to effectively engage customers in their process.