Story Refinement How to write and refine your stories so that your team can reach DONE by the end of your sprint!
|
|
- Albert Warner
- 6 years ago
- Views:
Transcription
1 + Story Refinement How to write and refine your stories so that your team can reach DONE by the end of your sprint! Tonya McCaulley Director of Training ROME Agile
2 + About Your Speaker Tonya McCaulley Born here Raised here Live here Travel the world doing what I love Want to bring Ohio forward!
3 + Audience Poll How many of you are using Agile at work? How many of you hit DONE by the end of the sprint? Why or why not?
4 + User Story and Acceptance Criteria Refinement and hitting DONE! Level set on User Story purpose and definitions How to INVEST in good user stories Refining the Acceptance Criteria. Beginning to end to set your team up for SUCCESS!!!
5 + Let s level-set on User Story purpose and definitions
6 + Keep yourself expressing business value Avoid introducing detail too early that would prevent design options and inappropriately lock developers into one solution Why user stories? Get to small enough chunks that invite negotiation and movement in the backlog (MR./MRS. PO- THIS IS FOR YOU!!!) Leave the technical functions to the architect, developers, testers, etc.
7 + What is a User Story? A concise, written description of a piece of functionality that will be valuable to a user (or owner) of the software.
8 + User Story Description Who (user role) What (goal) Why (value) gives clarity as to why a feature is useful can influence how a feature should function can give you ideas for other useful features that support the user's goals
9 + User Story Description As a [user role] I want to [goal] so I can [value] For example: As a registered user I want to log in so I can access subscriber-only content
10 + Use specific user roles Try to avoid the generic role "User" when writing user stories. User stories are about all of the "actors" who interact with the system or who realize some value or benefit from the system. Not all actors are end users. For example, an actor could be another system or someone who wants certain functionality in order to buy your product but will never actually use the product. It may be useful to create aggregate actors (e.g. "consumer") and specialized actors (e.g. "browser" or "frequent shopper"). These aggregates are called user personae.
11 + How big a piece of work should a user story be? User Story should be small enough to be coded and tested within a sprint - ideally just a few days. When a story is too large, it is called an "epic". Backlog items tend to start as epics, when they are lower priority. For release refinement & planning, epics should be broken down into smaller chunks, but not so small that you've moved into detailed design.
12 +Who can make a user story Creation The customer, customer proxy, product owner and anyone else who identifies a need for the product can contribute user stories. Ownership & Maintenance The product owner owns the user stories and is responsible for writing, gathering, maintaining, and prioritizing. Usage Developers, testers, technical writers use user stories to be able to know what to implement and when they're done. Product owners track overall progress based on the status of the user stories. Management tends to track user stories rolled up to epics or features.
13 INVEST in Good User Stories User Stories should have these characteristics: Independent User Stories should be as independent as possible. Negotiable User Stories are not a contract. They are not detailed specifications. They are reminders of features for the team to discuss and collaborate to clarify the details near the time of development. Valuable User Stories should be valuable to the user (or owner) of the solution. They should be written in user language. They should be features, not tasks. Estimatable User Stories need to be possible to estimate. They need to provide enough information to estimate, without being too detailed. Small User Stories should be small. Not too small. But not too big. Testable User Stories need to be worded in a way that is testable, i.e. not too subjective and to provide clear details of how the User Story will be tested.
14 + Acceptance Criteria
15 Refinement Start The ASK is input in Execution state get and may get automatically converted depending on software used Refinement Team Features are presented to assign the three amigos in charge of refining them. Three Amigos Create the Epics Identify Scenarios Identify solution and document it inside the Epics Project: Backlog Three Amigos PO, Architect, UX/QA Next step: Estimation
16 Estimation: 20% to 50% confidence Three Amigos Once there is agreement on 1 piece of Acceptance criteria and scenarios for a US, an estimate is provided for it [1]. The estimate is at 20% confidence level if it is above 13 SP (the reference value for something feasible within 1 sprint) and if the story cannot get assigned to one specific team. Three Amigos YES US break down (by scenario) Prioritize broken down US Identify acceptance criteria Estimate Estimate <= 13 SP and US assigned to one scrum team? NO [1] Estimates are provided in SP using Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144, ). At 20% confidence level, the estimate can be expressed also in T-Shirt size (XS to XL) with the following correspondence: S <= 13, M = 21, L= 34, XL = 55, XXL = 89, XXXL = 144)
17 Estimation: 50% to 80% confidence (and beyond) Scrum team (look ahead meeting) Revisit data at the right time (i.e. when the 80% bucket depletes) to refine available information. Add test scenarios (Further breakdown possible, at scrum team level) Scrum Team (Iteration planning meeting) Entry point for Release and Iteration planning Beyond scope
18 The confidence buckets Some 3 amigos teams work on this transition In parallel, some other 3 amigos teams work on this transition In parallel, Scrum teams work on this transition as part of the look ahead meetings To execution W W I New Feature- 3 amigos team is identified Epic are created, discussed and estimated US are broken down to fit Single scrum teams and and single iterations (SP<=13) Information is refined to be ready for sprint planning These buckets correspond to backlog portions to be constantly kept filled up (i.e. with 2-3 iterations worth of work in every bucket at any time) Frequency guidelines: W Weekly I Every iteration
19 Can AC any day! 80% 50% 2-3 iterations worth of work 2-3 iterations worth of work Constantly, 9 iterations worth of work are stackranked and estimated (at different level of confidence). We can take a snapshot of this to use for a commitment every day. 20% 2-3 iterations worth of work
20 + Let s do some laundry! How many tasks does it take you to finish your laundry?
21 What did we learn? Make sure you ask the right questions of your PO Ask WHO (role) is using it. WHAT they are using (goal) and WHY (Value).
22 User Story Acceptance Criteria In addition to the statement of the user story, additional notes, assumptions, and acceptance criteria can be kept with a user story on your scrum board or electronic scrum board (there is a separate section for Acceptance Criteria). Many discussions about a story between the team and customers will likely take place before and during the time the story is committed to code. **NOTE: One of the GREAT things about AGILE is CREATIVE LICENSE and being RESULTS DRIVEN. The difference between Design and Acceptance Criteria is what you ask about and your customer cares about.
23 + Acceptance Criteria for Confirmation Represents the items that the PO will verify in order to confirm that a story is done. Gives the team the detail necessary to delimit the product and correctly size the story. Scenarios are excellent ways to delimit the product. The team will build the simplest solution to the acceptance criteria; if you care about something, communicate it to the team. Any scenarios that are not included in a story, but need to be completed are put on another card & added to the backlog.
24 Gherkin is Workin Use Gherkin format when writing Acceptance Criteria Given: State of the system BEFORE user action takes place When: User action Then: State of system AFTER user action takes place EXAMPLE GIVEN: no display of state of services or components WHEN: I choose to monitor /display dashboard of service availability THEN: I should see the Green dot representing site up and running
25 Setting Your Team Up For Success is a WIN WIN For Everyone! Get it DONE!
Development Processes Agile Adaptive Planning. Stefan Sobek
Development Processes Agile Adaptive Planning Stefan Sobek Agile Planning Process Adaptive Planning In agile projects frequently issues and changes will be discovered. Go into these projects with expectations
More informationGETTING STARTED. Introduction to Backlog Grooming
GETTING STARTED Introduction to Backlog Grooming contents SECTION backlog grooming? SECTION 1 what is backlog grooming? 4 SECTION 2 who should be involved in a grooming session? 5 benefits of backlog grooming
More informationCollaboration at Scale: Prioritizing a Backlog. 13-Dec-2017
Collaboration at Scale: Prioritizing a Backlog 13-Dec-2017 Collaboration at Scale Designed for Scrum-centric organizations with more than 10 Scrum teams, the Collaboration at Scale webinar series provides
More informationExtreme programming XP 6
Extreme programming XP 6 Planning Game 3 Planning Game Independent: Stories should be as independent as possible. When thinking of independence it is often easier to think of order independent. In other
More informationAgile Software Development. Software Development Methodologies. Who am I? Waterfall. John York JOHN YORK EECS 441 FALL 2017 A BRIEF LOOK
Who am I? John York Agile Software Development JOHN YORK Director of Engineering at ProQuest Dialog Chief Technologist SpellBound AR A Computer Engineer from the University of Michigan! An agile development
More informationAgile Software Development. Software Development Methodologies. Who am I? Waterfall. John York JOHN YORK EECS 441 WINTER 2018 A BRIEF LOOK
Agile Software Development JOHN YORK EECS 441 WINTER 2018 John York Director of Engineering at ProQuest Dialog Chief Technologist SpellBound AR A Computer Engineer from the University of Michigan! An agile
More informationAgile Software Development Agile UX Work. Kati Kuusinen TUT / Pervasive / IHTE
Agile Software Development Agile UX Work Kati Kuusinen Researcher @ TUT / Pervasive / IHTE kati.kuusinen@tut.fi Contents 1. Introduction / Motivation 2. Agile software development 3. User experience work
More informationUser Stories Applied, Mike Cohn
User Stories Applied, Mike Cohn Chapter 1: An Overview Composed of three aspects: 1. Written description of the story used for planning and as a reminder 2. Conversations about the story that serve to
More informationDefining Project Requirements
Defining Project Requirements SWEN-610 Foundations of Software Engineering Department of Software Engineering Rochester Institute of Technology 1 There are functional and non-functional requirements. Functional
More informationStory Writing Basics
Jimi Fosdick, PMP, CST Agile Process Mentor jfosdick@collab.net 503.248.0800 Story Writing Basics [A user story is] a promise for a future conversation -Alistair Cockburn 1 Welcome Welcome to our ScrumCore
More informationCREATING EFFECTIVE USER STORIES
CREATING EFFECTIVE USER STORIES THE PRODUCT OWNER S PERSPECTIVE By: Philip Wess CREATING EFFECTIVE USER STORIES (THE PRODUCT OWNER'S PERSPECTIVE)... 1 Overview of a User Story... 2 Epics vs User Stories...
More informationBehavior Driven Development (BDD) By Nabeel Ibrahim
Behavior Driven Development (BDD) By Nabeel Ibrahim About Me Quality Engineer at Slalom Consulting 8 years testing experience Experience with Web and Mobile automation Test strategy creation Love soccer
More informationVision, Roadmap, and Release Planning
Vision, Roadmap, and Release Planning Supplemental Materials for a Product Owner Jessica Komarek and Sara Alterisio 5 Levels of Agile Release Planning Vision Roadmap Release Iteration Daily What, Who,
More informationWriting Agile User Stories
RefineM s January 2014 Lunch & Learn Webinar Writing Agile User Stories NK Shrivastava, PMP, RMP, ACP CEO/Consultant - RefineM Agenda 1. What is Virtual Lunch & Learn 2. Your expectations from this webinar
More informationUser Stories. Wednesday, January 23, 13
User Stories 1 User Stories and their friends: Use Cases, Scenarios, Personas, Gherkins and Kanbans 7 W s Who writes user stories? What is a user story? When is it written? Where are they seen? Why is
More informationSpecifying Acceptance Criteria
Freelance SQL Server Consultant Specifying Acceptance Criteria I have worked with some agile product owners who when the write user stories, the like to go epic on the acceptance criteria, in fact when
More informationTracking Issues with JIRA
Tracking Issues with JIRA Get a Linux Foundation Account JIRA User's Guide JIRA Setup for ONAP Viewing Issues in JIRA Reporting a Bug Proposing a New Feature JIRA Issue Types JIRA Workflow JIRA Statuses
More informationTesting Agile Projects Stuart Reid
ing Agile Projects Stuart Reid ing Solutions Group 117-119 Houndsditch London EC3A 7BT UK sreid@ing-solutions.com www.ing-solutions.com Stuart Reid, 2011 Scope Agile Manifesto and Principles An Agile Development
More informationAn Intro to Scrum. Agile (Iterative) Project Development. Written in 2001 Can be read in its entirety at:
An Intro to Scrum Agile (Iterative) Project Development Broken down into iterations Self-Managed Minimal Planning Easily/Quickly adapts to change The Agile Manifesto Written in 2001 Can be read in its
More informationdefined. defined. defined. defined. defined. defined. defined. defined. defined.
Table of Contents Week 1 Software Development... 2 Software Eng Life-Cycle Development Phases... 2 Methodologies... 2 Week 2 - XP, Scrum, Agile... 3 Extreme Programming (XP)... 3 Values of XP Programming...
More informationBacklog Refinement Process. Carolina Graffe Jorge Fernández
Backlog Refinement Process Carolina Graffe Jorge Fernández Product Management El Equipo Scrum Backlog Refinement Process Backlog: cola de características que el equipo Scrum mantiene. Se espera que cambie
More informationAdopting Agile Practices
Adopting Agile Practices Ian Charlton Managing Consultant ReleasePoint Software Testing Solutions ANZTB SIGIST (Perth) 30 November 2010 Tonight s Agenda What is Agile? Why is Agile Important to Testers?
More informationMicrosoft. Recertification for MCSD: Application Lifecycle Management
Microsoft 70-499 Recertification for MCSD: Application Lifecycle Management Download Full Version : http://killexams.com/pass4sure/exam-detail/70-499 QUESTION: 82 Your team uses Microsoft Visual Studio
More informationBusiness Analysis for Practitioners - Requirements Elicitation and Analysis (Domain 3)
Business Analysis for Practitioners - Requirements Elicitation and Analysis (Domain 3) COURSE STRUCTURE Introduction to Business Analysis Module 1 Needs Assessment Module 2 Business Analysis Planning Module
More informationTest Driven Development. René Barto SES Agile Development - Test Driven Development
Test Driven Development René Barto SES Agile Development - Test Driven Development 27-09-2006 Contents About Myself About SES Agile Development A Typical Developer s Day Test Driven Development Questions
More informationTesting in the Agile World
Testing in the Agile World John Fodeh Solution Architect, Global Testing Practice 2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Outline
More informationFinal Paper/Best Practice/Tutorial Advantages OF BDD Testing
Final Paper/Best Practice/Tutorial Advantages OF BDD Testing Preeti Khandokar Test Manager Datamatics Global Solutions Ltd Table of Contents Table of Contents... 2 Abstract... 3 Introduction... 3 Solution:...
More informationBringing QA Into the Agile Process
Quality Assurance - SCQAA-OC 2/17/09 Bringing QA Into the Process SCQAA Meeting 2/17/09 Speaker: Paul Hodgetts, Logic, www.logic.com Rev 090217 Your Speaker: Paul Hodgetts Team coach, trainer, consultant,
More informationUser Stories Applied, Mike Cohn
User Stories Applied, Mike Cohn Chapter 1: An Overview Composed of three aspects: 1. Written description of the story used for planning and as a reminder 2. Conversations about the story that serve to
More informationAtlassian JIRA Introduction to JIRA Issue and Project Tracking Software Tutorial 1
Atlassian JIRA Introduction to JIRA Issue and Project Tracking Software Tutorial 1 Once again, we are back with another tool tutorial. This time it s the Issue and Project Tracking Software Atlassian JIRA.
More informationHow Can a Tester Cope With the Fast Paced Iterative/Incremental Process?
How Can a Tester Cope With the Fast Paced Iterative/Incremental Process? by Timothy D. Korson Version 7.0814 QualSys Solutions 2009 1 Restricted Use This copyrighted material is provided to attendees of
More informationRequirements Gathering: User Stories Not Just an Agile Tool
Copyright 2016 Loft9. All Rights Reserved. 1 Loft9Consulting.com LOFT9 BUSINESS INSIGHTS Requirements Gathering: User Stories Not Just an Agile Tool Copyright 2016 Loft9. All Rights Reserved. 2 Loft9Consulting.com
More informationA CONFUSED TESTER IN AGILE WORLD
A CONFUSED TESTER IN AGILE WORLD QA A LIABILITY OR AN ASSET THIS IS A WORK OF FACTS & FINDINGS BASED ON TRUE STORIES OF ONE & MANY TESTERS!! J Presented By Ashish Kumar, A STORY OF TESTING. WHAT S AHEAD
More informationJIRA 5.x, first steps
JIRA 5.x, first steps Table of Contents: 1.) Change History:... 2 2.) URL:... 3 3.) Login:... 3 4.) Setting user profile:... 3 5.) Using filters:... 4 a) Changing existing filters... 5 6.) Configuring
More informationSAFe Atlassian Style (Updated version with SAFe 4.5) Whitepapers & Handouts
SAFe Atlassian Style (Updated version with SAFe 4.5) Whitepapers & Handouts Exported on 09/12/2017 1 Table of Contents 1 Table of Contents...2 2 Abstract...4 3 Who uses SAFe and Why?...5 4 Understanding
More informationModule 4 Designing, Planning & Estimating
Module 4 Designing, Planning & Estimating Table of Contents Module 4...1 Study Guide...2 Reading... 2 Assignment... 2 Module Overview...2 Outline... 2 Learning Outcomes... 2 Agile Architecture & Design...3
More informationLESSONS LEARNED: BEING AGILE IN THE WATERFALL SANDBOX
www.twitter.com/telerik www.facebook.com/telerik LESSONS LEARNED: BEING AGILE IN THE WATERFALL SANDBOX Philip Japikse (@skimedic) phil.japikse@telerik.com www.skimedic.com/blog MVP, MCSD.Net, MCDBA, CSM,
More informationBest Practices for Collecting User Requirements
Federal GIS Conference February 9 10, 2015 Washington, DC Best Practices for Collecting User Requirements Gerry Clancy Glenn Berger Requirements Provide direction for program success Why Requirements are
More information2014 Intelliware Development Inc.
What You ll Learn in this Presentation: The basics of user stories. How user stories fit into the overall Agile planning process. How to write a user story. A story card example 2 Why is it so Difficult
More informationTest Automation Strategies in Continuous Delivery. Nandan Shinde Test Automation Architect (Tech CoE) Cognizant Technology Solutions
Test Automation Strategies in Continuous Delivery Nandan Shinde Test Automation Architect (Tech CoE) Cognizant Technology Solutions The world of application is going through a monumental shift.. Evolving
More informationRequirement Engineering within an Agile Environment BY KEJI GIWA. Digital Bananas Technology
Requirement Engineering within an Agile Environment BY KEJI GIWA HLR Workshop Requirement Catalogue Product Planning Sprint Planning Meeting Keyscreens Use Case / Epic Stories Implement Wireframes DBT
More informationEssentials of design management with Rational Software Architect
Rational Self-paced training workbook Essentials of design management with Rational Software Architect Lab exercises (Self-paced training) Self-paced training workbook Self-paced training workbook Essentials
More information<Insert Picture Here> CxP Design Sprint
CxP Design Sprint Maria Fernandez Trevino Agenda Intro to Agile The design sprint Unified design board Daily schedule options Product Owner: Tim Scrum Master: Maria elopment
More informationUser Story Workshop. BA-Squared, LLC
User Story Workshop BA-Squared, LLC User Story Level of Detail User Stories elaborate over time, just like other requirements. Start high level and break them into smaller pieces. Product View Release
More informationProduct Backlog Document Template and Example
Product Backlog Document Template and Example Introduction 1. Client Information (Name(s), Business, Location, contact information) 2. Team Information Team Member Names (contact information) 3. Project
More informationW hitepapers. The Nexus Integration Team. Rob Maher, Patricia Kong. November 2016
November 2016 W hitepapers The Nexus Integration Team Rob Maher, Patricia Kong The Nexus Integration Team (NIT) is a new role that is essential within the Nexus framework. It is a role that is performed
More informationHow to Write Effective Use Cases? Written Date : January 27, 2016
Written Date : January 27, 2016 One of the most difficult problem in software development is capturing precisely what you want to build. Inaccurate requirement will end-up with significant delay, rework
More informationXP: Planning, coding and testing. Planning. Release planning. Release Planning. User stories. Release planning Step 1.
XP: Planning, coding and testing Annika Silvervarg Planning XP planning addresses two key questions in software development: predicting what will be accomplished by the due date determining what to do
More informationNEW KANNAWAY APP SCREEN DECK
NEW KANNAWAY APP SCREEN DECK Home Screen Six actions to chose from Profile for user Left hand menu for further options Home page Sliders are on rotation and we can change to show different messages and
More informationAgile Accessibility. Presenters: Ensuring accessibility throughout the Agile development process
Agile Accessibility Ensuring accessibility throughout the Agile development process Presenters: Andrew Nielson, CSM, PMP, MPA Ann Marie Davis, CSM, PMP, M. Ed. Cammie Truesdell, M. Ed. Overview What is
More informationICAgile Learning Roadmap Agile Testing Track
ICAgile Learning Roadmap Agile Testing Track The work in this document was facilitated by the International Consortium for Agile (ICAgile) and done by the contribution of various Agile Experts and Practitioners.
More informationYammer. Getting Started. What Tool Do I Use?
1 Yammer Getting Started In an effort to have fewer passwords, your IT team is making your log-in to Yammer much easier. You will simply have to perform a couple of steps to set this up, only once. After
More informationSeven Deadly Sins of Agile Testing
Seven Deadly Sins of Agile Testing 2 About me Brad Swanson Time to market Traditional Development Analyze Implement Test Agile Development Deliverable Deliverable 3 Risk Risk traditional agile Time 4 Schedule
More informationLecture 7: Software Processes. Refresher: Software Always Evolves
Lecture 7: Software Processes What is a Software Development Process? The Lifecycle of a Software Project Agile vs. Disciplined Some common approaches: RUP, SCRUM, XP, ICONIX, Where UML fits in (next lecture)
More informationRequirements and User-Centered Design in an Agile Context
Requirements and User-Centered Design in an Agile Context The Volvo Group Business Areas AB Volvo Volvo Trucks Renault Trucks Mack Trucks Nissan Diesel Buses Construction Equipment Volvo Penta Volvo Aero
More informationWORKSHOP. Writing User Stories
WORKSHOP Writing User Stories contents SECTION 1 user stories what is a user story? 4 user story template 5 examples: user stories 6 user story checklist 7 why not tasks? 8 SECTION 2 writing acceptance
More informationneeds, wants, and limitations
In broad terms Process in which the needs, wants, and limitations of end users of a product are given extensive attention at each stage of the design process. ISO principles which says that the design
More informationAgile Tester Foundation E-learning Course Outline
Foundation E-learning Course Outline General Description This course provides testers and test managers with an understanding of the fundamentals of testing on agile projects. Attendees will learn how
More informationBy Camille Spruill SPC4, SA, CSM, PMP, CBAP. Raleigh Business Analysis Development Day (RBADD) October 18 th, 2016
By Camille Spruill SPC4, SA, CSM, PMP, CBAP Raleigh Business Analysis Development Day (RBADD) October 18 th, 2016 LLC 1 Presenter Camille Spruill, SPC4, SA, CSM, PMP, CBAP Founder of eztagile, LLC Chief
More informationHOW TO WRITE USER STORIES (AND WHAT YOU SHOULD NOT DO) Stuart Ashman, QA Director at Mio Global Bob Cook, Senior Product Development Manager, Sophos
HOW TO WRITE USER STORIES (AND WHAT YOU SHOULD NOT DO) Stuart Ashman, QA Director at Mio Global Bob Cook, Senior Product Development Manager, Sophos Welcome This presentation will discuss Writing user
More informationThe Agile Samurai: How Agile Masters Deliver Great Software PDF
The Agile Samurai: How Agile Masters Deliver Great Software PDF Faced with a software project of epic proportions? Tired of over-committing and under-delivering? Enter the dojo of the agile samurai, where
More informationSprint Review. DesignOps / October 11, Sprint 2 Sprint Dates: 9/28/2017 to 10/11/2017. CWDS / Child Welfare Digital Services
Sprint Review DesignOps / October 11, 2017 Sprint 2 Sprint Dates: 9/28/2017 to 10/11/2017 CWDS / Child Welfare Digital Services Sprint Agenda Bi-Weekly Backlog Refinement DesignOps Story Auction (the DOSA)
More informationGetting Started with the Salesforce Agile Accelerator
Getting Started with the Salesforce Agile Accelerator Salesforce, Summer 16 @salesforcedocs Last updated: April 14, 2016 Copyright 2000 2016 salesforce.com, inc. All rights reserved. Salesforce is a registered
More informationCONFERENCE PROCEEDINGS QUALITY CONFERENCE. Conference Paper Excerpt from the 28TH ANNUAL SOFTWARE. October 18th 19th, 2010
PACIFIC NW 28TH ANNUAL SOFTWARE QUALITY CONFERENCE October 18th 19th, 2010 Conference Paper Excerpt from the CONFERENCE PROCEEDINGS Permission to copy, without fee, all or part of this material, except
More informationASTQB Advance Test Analyst Sample Exam Answer Key and Rationale
ASTQB Advance Test Analyst Sample Exam Answer Key and Rationale Total number points = 120 points Total number points to pass = 78 points Question Answer Explanation / Rationale Learning 1 A A is correct.
More informationBEHAVIOR DRIVEN DEVELOPMENT BDD GUIDE TO AGILE PRACTICES. Director, Strategic Solutions
BEHAVIOR DRIVEN DEVELOPMENT BDD GUIDE TO AGILE PRACTICES Presenter: Joshua Eastman Director, Strategic Solutions ABOUT THE SPEAKER Josh has over seven years of experience as an accomplished software testing
More informationIntroduction to Extreme Programming
Introduction to Extreme Programming References: William Wake, Capital One Steve Metsker, Capital One Kent Beck Robert Martin, Object Mentor Ron Jeffries,et.al. 12/3/2003 Slide Content by Wake/Metsker 1
More informationSAFe Reports Last Update: Thursday, July 23, 2015
SAFe Reports Last Update: Thursday, July 23, 2015 This document describes the set of reports provided by Jazz Reporting Service (JRS) aligned with SAFe (Scaled Agile Framework) metrics. Some of these reports
More informationInside JIRA scheme, everything can be configured, and it consists of. This section will guide you through JIRA Issue and it's types.
JIRA Tutorial What is JIRA? JIRA is a tool developed by Australian Company Atlassian. It is used for bug tracking, issue tracking, and project management. The name "JIRA" is actually inherited from the
More informationLife between Iterations
Life between Iterations Challenges in Agile Testing Padmasankar Jadu, Senior Delivery Manager, Global Business Services, IBM India Pvt Ltd. STC 2013, Bangalore Biography of the Author Padmasankar Jadu,
More informationXP: Planning, coding and testing. Practice Planning game. Release Planning. User stories. Annika Silvervarg
XP: Planning, coding and testing Annika Silvervarg Practice Planning game Goal: schedule the most important tasks Which features to implement in what order Supports: simple design, acceptance testing,
More informationPracticing Agile As a BA
2014 BA Convention Practicing Agile As a BA Presented by: Jagruti Shah Associate Business Consultant Mastek Ltd 2014 BA Convention 2 Role of BA in Agile What is Agile? What does Agile mean for a Business
More informationTime Tested. Testing Improved. The Materials
The Materials The slides follow the ISTQB Foundation Extension Agile Tester syllabus The terms come from the latest ISTQB Glossary (see next slide also) Two mock exams are included to assess your readiness
More informationKanban, Flow and Cadence
Kanban, Flow and Cadence Karl Scotland 1 KFC Development Kanban Controlled Work Flow Effective Work Cadence Reliable Work 2 Kanban Controlling the Workflow 3 Definition Kanban (in kanji 看板 also in katakana
More informationHello everyone, how are you enjoying the conference so far? Excellent!
1 Hello everyone, how are you enjoying the conference so far? Excellent! I m Andy Sutton, the e-builder User Experience Lead, and I m here to talk to you about User Experience. In this session, we re going
More informationUser Stories for Agile Requirements. Mike Cohn - background. Copyright Mountain Goat Software, LLC
User Stories for Agile Requirements 1 Mike Cohn - background 2 It s a communication problem Software requirements is a communication problem Those who want software must communicate with those who will
More informationSoftware Engineering I (02161)
Software Engineering I (02161) Week 8 Assoc. Prof. Hubert Baumeister DTU Compute Technical University of Denmark Spring 2016 Last Week State machines Layered Architecture: GUI Layered Architecture: Persistency
More informationMeetu Arora Sr V.P. Quality Assurance Naukri.com Testing Team Journey @Naukri.com Automation WATIR 2008 2007 2006 Agile testing team 2010 2015 2012 Automation QTP Inception of Testing Team Automation Selenium
More informationAgile Manifesto & XP. Topics. Rapid software development. Agile methods. Chapter ) What is Agile trying to do?
Topics 1) What is trying to do? Manifesto & XP Chapter 3.1-3.3 2) How to choose plan-driven vs? 3) What practices go into (XP) development? 4) How to write tests while writing new code? CMPT 276 Dr. B.
More informationDESIGN. (Chapter 04)
DESIGN (Chapter 04) THE PROCESS OF INTERACTION DESIGN Overview What is involved in Interaction Design? Importance of involving users Degrees of user involvement What is a user-centered approach? Four basic
More informationI am Stephen LeTourneau from Sandia National Laboratories Sandia s National Security Missions include: Nuclear Weapons Defense Systems & Assessments
I am Stephen LeTourneau from Sandia National Laboratories Sandia s National Security Missions include: Nuclear Weapons Defense Systems & Assessments Energy, Climate & Infrastructure Security International,
More informationRTC SAFe Migration Guidelines
RTC SAFe Migration Guidelines Introduction Rational Team Concert (RTC) is at the core of IBM s DevOps solution and the logical starting point for teams looking to get started with SAFe (Scaled Agile Framework
More informationThe Scaled Agile Framework
The Scaled Agile Framework Foundations of the Scaled Agile Framework (SAFe) SDJug Oct. 15, 2013 2008-2013 Leffingwell, LLC, and Scaled Agile, Inc. All rights reserved. Armond Mehrabian Enterprise Agile
More informationValue & Role of Business Analyst in Agile. Presented by: Jagruti Shah Associate Business Consultant Mastek Ltd
Value & Role of Business Analyst in Agile Presented by: Jagruti Shah Associate Business Consultant Mastek Ltd Our Click Focus to edit Master using Agile text styles Principles Build software quickly Keep
More informationHands-On Lab. Agile Planning and Portfolio Management with Team Foundation Server Lab version: Last updated: 11/25/2013
Hands-On Lab Agile Planning and Portfolio Management with Team Foundation Server 2013 Lab version: 12.0.21005.1 Last updated: 11/25/2013 CONTENTS OVERVIEW... 3 EXERCISE 1: AGILE PROJECT MANAGEMENT... 4
More informationAgile Product Management: User Stories: How To Capture, And Manage Requirements For Agile Product Management And Business Analysis With Scrum
Agile Product Management: User Stories: How To Capture, And Manage Requirements For Agile Product Management And Business Analysis With Scrum (scrum,... Development, Agile Software Development) PDF User
More informationCase Management Digital Service Sprint Review Sprint 5.1: 11/16/17 11/29/17. CWDS / Child Welfare Digital Services
Case Management Digital Service Sprint Review Sprint 5.1: 11/16/17 11/29/17 CWDS / Child Welfare Digital Services Agenda Sprint Stories Core County Brief Sprint Backlog and Team Metrics Feature Based Presentations:
More informationShift Left Testing: are you ready? Live Webinar, Sept 19
Shift Left Testing: are you ready? Live Webinar, Sept 19 Guy Arieli CTO, Experitest 01 What exactly is Shift Left? Agenda 02 03 How Shift Left affects application development & testing organizational structures
More informationWhat s the Value of Your Data? The Agile Advantage
What s the Value of Your Data? The Agile Advantage by Jan Paul Fillie and Werner de Jong In a world of big data, advanced analytics, in-memory data warehousing, and real-time business intelligence (BI),
More informationAdministering SQL Servers for Development Teams. Mike Acord & Tony Sebion Omni Resources
Administering SQL Servers for Development Teams Mike Acord & Tony Sebion Omni Resources Omni Resources Solutions Group Mike Acord Senior Architect Solutions Group, Omni Resources Tony Sebion Director Solutions
More informationAgile 2005 Experience Report
Agile Adoption: Does it have to be All In or Fold? Rebecca WirfsWirfs-Brock 2011 WirfsWirfs-Brock Associates Who I Am There Has to Be A Better Way Jon Spence, Sr. Principal Engineer and Technical Fellow,
More informationUSING TASKS IN OUTLOOK
USING TASKS IN OUTLOOK WORKING WITH TASKS Although there are many layers of complexity you can add into tasks, at their basic level they are very simple. You create tasks either for yourself or for someone
More informationServiceNow - Agile in ServiceNow
ServiceNow - Agile in ServiceNow The ServiceNow Agile Development application is an iterative and incremental process for software development environments. Agile Development application is enhanced with
More informationGoogle Analytics. powerful simplicity, practical insight
Google Analytics powerful simplicity, practical insight 1 Overview Google Analytics Improve your site and increase marketing ROI Free, hosted web analytics service View over 80+ reports online, for download,
More informationAGILE. Getting Started on Your Team. Davisbase. Copyright 2011 Davisbase LLC. Licensed for Classroom Use to ASPE for Webinar Use Only
AGILE Getting Started on Your Team Copyright 2011 LLC. Licensed for Classroom Use to ASPE for Webinar Use Only INTRO AND AGENDA Your Instructor: Christy Clement Agile Trainer and Coach Agenda: Picking
More informationBreakdown of Some Common Website Components and Their Costs.
Breakdown of Some Common Website Components and Their Costs. Breakdown of Some Common Website Components and Their Costs. The cost of a website can vary dramatically based on the specific components included.
More informationThe process of interaction design
Chapter 9 The process of interaction design 1 Overview What is involved in Interaction Design? Importance of involving users Degrees of user involvement What is a user-centered approach? Four basic activities
More informationA Little Lean with Kanban
A Little Lean with Kanban Introduction What is it? What Problem? Why Kanban? How Benefits Path To Agility Tim Wingfield Email: tim@timwingfield.com Blog: blog.timwingfield.com Twitter: timwingfield Hockey,
More informationThe Web Service Sample
The Web Service Sample Catapulse Pacitic Bank The Rational Unified Process is a roadmap for engineering a piece of software. It is flexible and scalable enough to be applied to projects of varying sizes.
More information[PDF] Agile Project Management & Scrum QuickStart Guides
[PDF] Agile Project Management & Scrum QuickStart Guides The ultimate companion for professionals interested or involved in Agile and Scrum, this book will give you a holistic, well-balanced introduction
More information