User Centered Interaction Design in Agile Environment.

Slides:



Advertisements
Similar presentations
Chapter 5 – Enterprise Analysis
Advertisements

Supported by: What do you think is new or different about your idea? If this is such a good idea, why hasn’t it been done before? Why do you think.
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
© AgiliX Agile Development Consulting Agile Software Architecture Cesario Ramos.
Can you plan without understanding what is it that you are planning for? e.g. - what is it we are doing? - what do we need to do?
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
William H. Bowers – Understanding Users: Qualitative Research Cooper 4.
Requirements Analysis CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology January 7, 2003.
Ch 4 The Process page 1CS 368 Building Software is Difficult often delivered late often over budget always with errors must be a custom solution complexity.
Architecture is More Than Just Meeting Requirements Ron Olaski SE510 Fall 2003.
Artificial Intelligence
Software Engineering. How many lines of code? Average CS1004 assignment: 200 lines Average CS4115 project: 5000 lines Corporate e-commerce project: 80,000.
1 SYS366 Week 1 - Lecture 2 How Businesses Work. 2 Today How Businesses Work What is a System Types of Systems The Role of the Systems Analyst The Programmer/Analyst.
LARGE SYSTEMS IMPLETATION PROCESS  Overview Review process diagram homework practice.
Software Engineering.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Management 421 Computer Science 350. Overview Project Roles Software Development Process Extreme Programming Management/Developer Interaction in Extreme.
Introduction to Software Engineering Dr. Basem Alkazemi
Administrivia Turn in ranking sheets, we’ll have group assignments to you as soon as possible Homeworks Programming Assignment 1 due next Tuesday Group.
SE 555 – Software Requirements & Specifications Introduction
8 Systems Analysis and Design in a Changing World, Fifth Edition.
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
Lecture 3 Strategic Planning for IT Projects (Chapter 7)
Classical vs. Agile Requirements Development Svetlin Nakov Telerik Software Academy academy.telerik.com Senior Technical Trainer
The Many Contexts of Software Architecture
Roles Managers Technical Team Leaders Programmers Customers Database Administrators Instructors.
Extreme Programming(XP)
Incorporating Pragmatic Usability Testing Into a Software Test Plan Carla Merrill, Ph.D. Focused Design focuseddesign.com
Sri Lanka Institute of Information Technology Software Engineering Project – I Clone of Rally GROUP NO : WD-SEP-002 | PROJECT NO :25 PROJECT : CLONE OF.
SCRUM for Startups Innosquared – Providing expertise on demand.
Presenter: 陳秋玉 1.  Extreme programming Extreme programming  On-site customer On-site customer  Benefit Benefit  Characteristics of a good customer.
Classical vs. Agile Requirements Development Svetlin Nakov Telerik Software Academy academy.telerik.com Senior Technical Trainer
5. Planning.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Interaction Design CMU. Today’s objectives Continue Design approaches (UCD, ACD)  User-Centered Design  Activity-Centered Design.
Planning Game in Artifacts Tracker (AT) Project Michal Pilawski.
Agile User Stories Enriched with Usability ANA M. MORENO AND AGUSTÍN YAGÜE UNIVERSIDAD POLITECNICA DE MADRID MADRID, SPAIN
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Object-Oriented Analysis and Design Fall 2009.
Chapter 3 Agile Software Development (1/2) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
The Long Tail Why the future of business is selling less of more ▫ISBN = ▫Chris Anderson Low Distribution and Inventory costs allow companies.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 other methodologies 1 Method/Process = step-by-step description of the steps involved.
Inception Chapter 4 Applying UML and Patterns -Craig Larman.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 18 Goal-Directed.
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
Stand Up Comedy Project/Product Management
SCRUM.
Chapter 7 Lecture 1 Design and Implementation. Design and implementation Software design and implementation is the stage in the software engineering process.
1 Requirements Engineering for Agile Methods Lecture # 41.
SupervisorMr. Phan Trường Lâm Group Members01446 – Trịnh Anh Đức – Nguyễn Minh Thành SE02311 –Phạm Tuấn Anh SE02425 – Vũ Hoàng Anh 1.
1 Introduction to eXtreme Programming Remko Popma Azzurri Ltd.
Chapter 8: Maintenance and Software Evolution Ronald J. Leach Copyright Ronald J. Leach, 1997, 2009, 2014,
Public Management Information Systems System Analysis & Design Saturday, June 11, 2016 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program.
Extreme programming (XP) Advanced Software Engineering Dr Nuha El-Khalili.
Why is Design so Difficult? Analysis: Focuses on the application domain Design: Focuses on the solution domain –The solution domain is changing very rapidly.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
Classifications of Software Requirements
C. What is a Feasibility report
Imran Hussain University of Management and Technology (UMT)
September 20, 2017 Agile Techniques Workshop Susan Futey
Systems Analysis – ITEC 3155 Evaluating Alternatives for Requirements, Environment, and Implementation.
Operational Feasibility
FEASIBILITY STUDY Feasibility study is a means to check whether the proposed system is correct or not. The results of this study arte used to make decision.
Chapter 3: The Project Management Process Groups: A Case Study
Agile Development – a new way of software development?
Public Management Information Systems System Analysis Thursday, August 01, 2019 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program Graduate.
Presentation transcript:

User Centered Interaction Design in Agile Environment

What customer want?

$

Dollar Printing Machine II Give them tools which helps them to make money(legally)

A good system is something which eliminates existing tasks(wherever its possible), or speedup the tasks with efficiency, save money and time.

Business Design Engineering

Design + Engineering Design + Engineering + Business

Design Engineering

Deciding what to build It is all about how we develop stories

“Plan for artifacts, whose form, content, behavior is useful, usable, desirable, as well as economically viable, and technically feasible ” – Alan Cooper

The hardest single part of building a software system is deciding precisely what to build? -- Fred Brooks

Business Design Engineering

Agile is an Engineering Process

Planning Game Stories Story Card Iteration Plan Release Plan Planning Game Decide on scope and priorities Estimate cost and schedule Benchmark for feedback

Who does the design?

Customer UsersProgrammerGraphics Designer

software development is not just about coding

Can you imagine Windows without mouse?

Customer UsersProgrammerGraphics Designer

Application Architect Interaction Designer Solution Architect

Customer Architect SME Users

Design Game Design Game Design Team Stories

Planning Game Story Card Iteration Plan Release Plan Planning Game Design Team

The Design Team typically creates a sizeable queue within just a few iterations by continuing to work with the Customer to develop new stories while current ones are being implemented.

Design involves a sizable up-front activities

Domain Design Customer Personas GoalTasksContext Objects

Domain Design Customer Personas GoalTasksContext Objects

Stocks SD.com Buy Sell StocksDirect.com MyStocks Domain: Stock Trading, Stock Exchange Entities/Objects: Stocks, User Tasks: login, Buy, List, Sell

Shekar Alex

Shekar StocksDirect.com Agent

Alex LOGIN USRNAME:PWD SELL STOCK_SYMBOL

Domain Customer Personas GoalTasksContext Objects Design

Shekar Alex Customer Goal: More Transaction Potential Users: Working Professional – Especially IT and Sales Personas: Shekar, Alex Context: Shekar - Work Environment & Work, Alex - Always on Move

“No matter how skillful and creative the designer,If he does not have a clear and detailed knowledge of the users he is designing for, what the constraints of the problem are, and what business or organizational goals the design is hoping to achieve, he will have little chance of success.” - Alan Cooper

A good system is something which eliminates existing tasks(wherever its possible), or speedup the tasks with efficiency, save money and time.

Business Design Engineering

Application Architect Interaction Designer Solution Architect

Domain Customer Personas GoalTasksContext Objects Design

Planning Game Story Card Iteration Plan Release Plan Planning Game Design Team

“If the software were magic, what would it do?”

Domain

Functioning of particular [business] environment Understanding the terminology Creating language for all stories, conversations, customer tests & code

Freeform Domain Discussion

Customer

Why some one has to buy our product? decision process for purchasing a product

Personas

User Models Personas represent behavior patterns

Goals

A goal is an end condition, whereas a task is an intermediate step that helps to reach a goal.

Context

Design is Technology Dependent

where, when, and how frequently would the users interact with this task?

Tasks

A goal is an end condition, whereas a task is an intermediate step that helps to reach a goal.