Agile User Story. Agile – User Story us·er stor·y uzər st ɔ ri noun A user story is a tool used in Agile software development to capture a description.

Slides:



Advertisements
Similar presentations
UI Story Board CIS78 Group Project Created by: Aliese Zacharias.
Advertisements

Practical User Stories Brett Maytom Senior Consultant, Readify VIC.NET - 10 May 2011.
Writing Good User Stories Bob Schommer, CSP, PMP Senior Project Manager Skyline Technologies, Inc.
Beyond “The System Shall...” A Journey from Good to Great Requirements.
MAY 11, 2011 WRITING USE CASES IN AN AGILE WORLD KARL O’BRIEN SENIOR SOLUTIONS ENGINEER BLUEPRINT SYSTEMS.
May 4, 2015 Writing Stories 7 September, 2006 Kane Mar.
Project Title (as descriptive as possible) Group Members CPE Computer Engineering Design I Electrical and Computer Engineering.
Unit 211 Requirements Phase The objective of this section is to introduce software system requirements and to explain different ways of expressing these.
Management 421 Computer Science 350. Overview Project Roles Software Development Process Extreme Programming Management/Developer Interaction in Extreme.
Idea Presentation Team Name : Title of Product/Service : Team Members Name, HP, .
Pre-Authorization for Faculty Travel Request Form.
Web2SMS. Description of service Web2SMS Service is a web (internet) based SMS service that will enable TN customers to log onto the TN website and send.
Software Development Models: Waterfall and Spiral Sung Hee Park Department of Mathematics and Computer Science Virginia State University August 21, 2012.
Managing a Project Using an Agile Approach and the PMBOK® Guide
1 CSc Senior Project Software Testing. 2 Preface “The amount of required study of testing techniques is trivial – a few hours over the course of.
, TargetProcesswww.targetprocess.com1 TargetProcess:Suite Agile Project Management System Powers iterative development Focuses on Project Planning,
Starter for 10 Unit 10: Flickr & YouTube Transform IT SFT10_Flickr_YouTube.
Intro to Excel - Session 7.11 Tutorial 7 - Session 7.1 Developing an Excel Application.
Quiz 1. Who is the guru of Extreme Programming?
RUP Requirements RUP Artifacts and Deliverables
Background The Encyclopedio of Life (EOL) is an ROR open source project to create a free, online reference source and database for every one of the 1.8.
The Project Process Inception - initial planning Elaboration - refining the design Construction - building the system Transition - installation support.
LBTO IssueTrak User’s Manual Norm Cushing version 1.3 August 8th, 2007.
Copyright David Churchville - XP and Agile Planning David Churchville ExtremePlanner Software XP Fishbowl.
What is Sure BDCs? BDC stands for Batch Data Communication and is also known as Batch Input. It is a technique for mass input of data into SAP by simulating.
Team ELL System Requirements Ladakeysha Thomas Elizabeth Waldo LaWanda Warren Brandon Williams.
Developing Use Cases in a Group Carolyn L. Cukierman Face-to-Face Technology Conference March 27, 2000.
SCRU M Scrum Overview - Commonly Used Terms Ali Qureshi, parorrey.com – 31 st Aug, 2015 PI Media parorrey.com.
Mobile Aps: Agile Mentoring Review
AN EASY-TO-USE SYSTEM THAT WILL HELP YOU CHOOSE A CAREER BASED ON YOUR INTERESTS AND.
Agile User Stories. What is a User Story? User stories are short, simple description of a feature told from the perspective of the person who desires.
Retail Training Manuel 2 Overview  One stop, secure, and easy-to-use web-based tool that incorporates rate, quote, and bind functions  Enables agents.
Agile User Stories Enriched with Usability ANA M. MORENO AND AGUSTÍN YAGÜE UNIVERSIDAD POLITECNICA DE MADRID MADRID, SPAIN
Facebook login was deprecated. ( notification sent to ~12k existing users) Legacy uSell referral system was deprecated –No more “uSell Wallet”, “Invite.
Systems Life Cycle. Know the elements of the system that are created Understand the need for thorough testing Be able to describe the different tests.
Telerik Software Academy Software Quality Assurance Binding business requirements to.NET code.
Agile Engineering. Agile - Engineering en·gi·neer·ing enjə ˈ niriNG/ noun the branch of science and technology concerned with the design, building, and.
April 24, 2017 Agile BVIR.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Changing Your Password General Lesson 3. Objectives Following completion of this lesson you will be able to:. Define how often a password must be changed.
Quality Criteria : Are you and your team capable of communicating the shared vision to whom it may concern so that it make sense to all relevant stakeholders.
Requirements specification Why is this the first major stage of software development? –Need to understand what customer wants first Goal of requirements.
1 Presentation Title Test-driven development (TDD) Overview David Wu.
Some Thoughts On PROTOTYPE Form Design. You may place prompt over or to the left of the data-entry field; select one and be consistent. Name Tom PromptResponse.
SafeSpeed Do your part CMPT 275 – Group 04 Two Squared.
Team Skill 3: Defining the System The Vision Document (16) 1.
Challenges in Agile Unclear project scope, multiple iterations, minimal documentation, early and frequent testing needs and active stakeholder involvement.
Agile Ceremonies. Agile - Ceremonies cer·e·mo·ny serə ˌ mōnē noun 1. a formal religious or public occasion, typically one celebrating a particular event.
Agile Project. Agile - Project proj·ect präj ˌ ekt noun an individual or collaborative enterprise that is carefully planned and designed to achieve a.
By Manish Shrotriya CSE MS 4 Point Agile Manifesto 1.Individuals and interactions over processes and tools 2.Working software over comprehensive.
Matching Exercise Creating User Stories Planning Poker Risk/Value Quadrant Mapping Advanced Burndown Interpretatio n Interactive.
Agile Requirements Introducing User Stories. Key Principles for Agile Requirements Active user involvement is imperative Agile teams must be empowered.
Requirements: Stories Emerson Murphy-Hill. What are User Stories? A user story represents a feature customers want in the software A user story is the.
Use Cases Discuss the what and how of use cases: Basics Examples Benefits Parts Stages Guidelines.
Software Development Life Cycle. The Software Life Cycle  Encompasses all activities from initial analysis until end of work  Formal process for software.
Agile Iteration. Agile - Iteration it·er·a·tion itə ˈ rāSHən noun the repetition of a process or utterance. repetition of a mathematical or computational.
You will need to… Sort out your teams Know your assessment schedule Identify your personal project title Discover the core functionality Agree the shared.
Penn State Project Management Conference
Discovering Use Cases.
Use Cases Discuss the what and how of use cases: Basics Benefits
Agile Scrum Management
LECTURE 3: Requirements Engineering
Affinity Program | Client Approved Copy| Native App Landing Page
Chapter 3: The Project Management Process Groups: A Case Study
How to Build an MVP in the Right Way
Working On-Line Module 4
Project Iterations.
LECTURE 3: Requirements Engineering
User Stories Agile Methodology HEE Learning Hub
Presentation transcript:

Agile User Story

Agile – User Story us·er stor·y uzər st ɔ ri noun A user story is a tool used in Agile software development to capture a description of a software feature from an end- user perspective. The user story describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement. plural noun: user stories Charter : Confidential 2

Agile – User Story Purpose Describes a feature from the customer’s perspective Anything that describes another thing looses information Promise to have a conversation Object used during Agile activities Place to capture information Don’t get hung up on the presentation, it will change Charter : Confidential 3

Agile – User Story Title Short but unique Will be used in conversation a thousand times Avoid metadata (e.g. QA only, Accounting, ASAP, etc.) Charter : Confidential 4

Agile – User Story Description Normal format As a I want so that As a defines how will benefit from this change I want describes what they want to accomplish So That defines the customer value, why they want the change As a returning customer I want to log in So that I can view previous orders Charter : Confidential 5

Agile – User Story Acceptance Criteria Normal format Given When Then Given set up the test When is the action that causes the test to happen Then is the expected result to test for Given an invalid user name is entered When the Login button is selected Then failed login message is displayed Charter : Confidential 6

Agile – User Story Size Sizing avoids using hours or days, to granular at this stage Story Points are relative, they don’t relate to time and are different between teams The smaller the better while still having customer value Needs to fit into 1 iteration Improves the accuracy of the Road Map Charter : Confidential 7