Show pageOld revisionsBacklinksBack to top This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. # IT:AD:Personas # <callout type="Navigation" class="small"> * [[../|(UP)]] {{indexmenu>.#2|nsort tsort}} </callout> <panel title="Summary"> It's a good idea to create Personas of User Stakeholders before you create Use Cases for them. We capture the current state, and sell the future state. </panel> ## Process ## * Give the Persona: * Name/Age/Gender * Current State: * Personal Attributes: * Tolerance to Change * Adoption of New Technologies * Technical Support Needs * Could teach others * Influence (Social interactions and ability to spread knowledge) * Technology Appetite Continuum: * Schedule: what is a day in the life of the Persona look like? * <span tip>Use Outlook (some day in the past) to create and screenshot a mock day/week Schedule.</span> * Locations: from where does the Persona work now? * On Premise * Across Organisations * Mobile * Remote * Future State: * Personal Attribute: * May have had to expand their ability to tolerate change. * Schedule: their day now looks like the following (easier) * Locations: they can now work from the following locations. Alternatively, you could measure impact by demonstrating better Qualities: * Qualities: * Flexibility * Time/Location ### Examples of Personas * Primary School Student * Secondary School Student * Parents/Caregivers * School ICT Administrator * School Administrator * School Principle * ICT External Service Integrator /home/skysigal/public_html/data/pages/it/ad/personas/home.txt Last modified: 2023/11/04 03:29by 127.0.0.1