Creating Effective Requirements - Selma Zafar


Published on

Defining clear requirements at the start of any project helps not only helps the build go smoothly, but aligns the whole project team. Selma will introduce you to different methods for uncovering and documenting requirements that will set up your intranet project for success.

Published in: Business, Sports, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Need to understand that approaching the company website and intranet are 2 different entities with 2 different ways to approach and document requirementsYour corporate Website:Communicate informationSupport a productE-commerceGOAL: Outward focussed & aligned with marketing strategies
  • Designed to meet the needs of your staffIncreasing staff efficiencyCollaboration, knowledge transferCommunicating accurate information Providing effective working environment
  • Before you begin on defining the requirements for your new intranet, you need to take a look at what you are starting with.If you have an intranet or even if you don’t, you can use some of the following techniques to define your current state. Understanding your current state is an important exercise in identifying what works well and what doesn’t work well.Focus on understanding what people are doing, where the gaps are, and identify where there is opportunity to introduce efficiencies, change processes etc
  • Changing Focus to the Users….Define the main goals the users are to performDefine a comprehensive list of all tasks the users will perform Prioritise tasks according to their importance (e.g. frequency or safety). Define task characteristics, such as goals, time of performing, inputs and dependencies, output, variability, frequency, duration, time constraints, flexibility, physical and mental demands, linked tasks, safety, criticality.Define and analyse tasks and sub-tasks and identify obstacles for solving tasks.Identify the usage environment through usage scenarios. Investigate environmental characteristics including physical and organisationalIdentify and prioritise functional requirements based on user task and environmental requirements.
  • The following are technique to help extract all of the information from your users that will help define better requirements.But defining
  • Before you even get started, you need to understand what information are you looking for. Based on your questions, you can select the correct method for gathering that information.
  • Survey design – designing a great survey is a hard thing to do, so don’t under estimate this.Great for gathering information on: When assessing customer or employee satisfaction, such as identifying or prioritizing problems to address.
  • Use techniques to help understand key tasks and priority of information with a department , team or group.Not to be used to identify what is not working, use this to understand the overall goals, process and priority of information.
  • Great for understanding people’s processes and pain points
  • Combining observations with interviewsThe merger of what people say they do with what they actually do.
  • Step by step break down of what people are doing.
  • Who: User group/department
  • What: the task in context of use
  • WHY: Goal of the task;
  • End result is something that is more relevant and useful not only for the project team, but also to understand what tasks are.
  • Creating Effective Requirements - Selma Zafar

    1. 1. Intranet Requirements<br />Making them user focused and usable<br />Selma Zafar<br />Senior User Experience Designer<br />OpenRoad Communications<br />
    2. 2. Requirements Defined <br />‘…is a statement that identifies a necessary attribute, capability, characteristic, or quality of a system in order for it to have value and utility to a user.’<br />- wikipedia<br />
    3. 3.
    4. 4.
    5. 5. Intranet vs Website Requirements<br />Source: Step Two Design<br />
    6. 6. Current State Assessment<br /><br />
    7. 7.<br />
    8. 8. User Centred Design Round-up<br />
    9. 9. What are the questions that you want to have answered? <br />
    10. 10.
    11. 11. Focus Groups<br /><br />
    12. 12. Staff and Stakeholder Interviews<br />
    13. 13. Observation<br />
    14. 14. Contextual Inquiry<br />
    15. 15. Task Analysis<br />
    16. 16.
    17. 17. Moving from SYSTEM<br />
    18. 18. TO YOUR EMPLOYEES<br />
    19. 19. From the System…<br />“The system shall support<br /> blog activity.”<br />
    20. 20. Refocusing on the user<br />WHO<br />
    21. 21. Refocusing on the user<br />WHAT<br />
    22. 22. Refocusing on the user<br />WHY<br />
    23. 23. Refocusing on the user<br />
    24. 24. Summary<br /><ul><li>Different than website with a focus on efficiency, content authoring and familiarity
    25. 25. Never ask employees what they want, observe and interview them to assess what they need
    26. 26. Write in a manner that answers: who, what and the why</li></li></ul><li>Selma Zafar<br /><br /><br />