Copyright © 2012-2014 by Mark J. Sebern Software Engineering Process I SE-2800-13 Sprint Execution.

Slides:

Advertisements

Similar presentations

Agile Development Primer – Using Roundtable TSMS in an Agile Shop Michael G. Solomon Solomon Consulting Inc.

Advertisements

A little Software Engineering: Agile Software Development C Sc 335 Rick Mercer.

Steve Collins Richland County IT Manager Agile.  Have Fun  Learn About Agile  Tell Some Stories.

What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.

IAgile – iNetFrame’s framework for agile development Features Get to see a working product early Development shadows evolving requirements Pair programming.

Agile Project Management with Scrum

Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.

Agile Development.

Copyright © by Mark J. Sebern Software Engineering Process I SE Product backlog, estimation, velocity.

 User assignments (product owner)  ‘circle’  1 st sprint: ◦ Scrum Boards (informative workspace)  Product -, release -, sprint -, defect backlog 

Agile Process Models. Prescriptive models don’t work It is unrealistic to not have changes. Why? The Agile Manifesto: Individuals and interactions over.

Agile development By Sam Chamberlain. First a bit of history..

Extreme Programming Mark Steverson. What Is Extreme Programming? ● Extreme Programming (XP) is a lightweight, agile methodology developed by Kent Beck.

Extreme Programming--a “New” Process Model Extreme Programming-- a “New” Process Model.

Managing a Project Using an Agile Approach and the PMBOK® Guide

Programming with eyes wide open. Your host today Subby Angelov Team

Introduction to Agile.

Agile Software Development Practice Adoption Survey Narendra Kurapati, Venkata Sarath Chandra Manyam, and Kai Petersen Blekinge Institute of Technology.

An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.

1 Agile Methodology & Programming Ric Holt July 2009.

Copyright 2008 Scott W. Ambler Agile Practices and Principles Survey 2008 Scott W. Ambler Michael.

What is Scrum Process? Where is it used? How is it better?

SE-280 Dr. Mark L. Hornick 1 Process Adaptations.

Agile and XP Development Dan Fleck 2008 Dan Fleck 2008.

SCRU M Scrum Overview - Commonly Used Terms Ali Qureshi, parorrey.com – 31 st Aug, 2015 PI Media parorrey.com.

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Agile Assessment Gadi Lifshitz, Ayelet Kroskin, Barak Yagour, Yael Dubinsky.

Coming up: What is Agile? XP Development Dan Fleck 2010 Dan Fleck 2010.

Extreme Programming (XP). Agile Software Development Paradigm Values individuals and interactions over processes and tools. Values working software over.

Extreme Programming.

Copyright © 2012 by Mark J. Sebern Scrum Overview (from

THE AGILE MENTALITY CHAPTER Topics  Why Use Agile and Scrum?  Agile Development –Manifesto for Agile Software Development  Scrum Methodology.

Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.

Copyright © 2015 Curt Hill Software Development Paradigms What do you need to know?

Traditional Process Models A quick overview. 2 Waterfall Model (Diagram) Communication Project initiation Requirements gathering Planning Estimating Scheduling.

Theories of Agile, Fails of Security Daniel Liber CyberArk.

Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.

Copyright © 2012 by Mark J. Sebern Sprints Sprint planning Sprint execution.

PV213 EIS in Practice: 06 – Development process 1 PV213 Enterprise Information Systems in Practice 06 – Development process.

WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ CA Agile Vision Product Manager Michael Lester.

Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.

Agile Development Chapter 10 - part 2. Agile Philosophy  A guiding philosophy and set of guidelines for : developing information systems in an unknown,

Kanban Advanced Software Engineering Dr Nuha El-Khalili.

Scrum Overview. Agenda What is scrum…and what it isn’t Scrum’s Characteristics The Scrum Process Scrum Phases Measurements Key Practices Backlogs Sprint.

Extreme Programming מתודולוגיה לפיתוח פרויקטי תוכנה.

The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.

Coming up: What is Agile? XP Development Dan Fleck 2010 Dan Fleck 2010.

Copyright © Curt Hill Scrum Software Development Paradigms What is a Scrum?

Scuola Politecnica Dipartimento DITEN Università degli Studi di Genova An Introduction to Scrum and XP Prof. Riccardo Berta.

Manifesto for Agile Software Development

Agile Project Management

CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.

Burn Down charts for Project Management

روش‌های سريع الانتقال (چابک) توسعه نرم افزار

Johanna Rothman Agile Team Measurements Chapter 12

Teaching slides Chapter 1.

Scrum Overview.

Scrum - Plan a Sprint Great Video (but added release /sprint layer)

© University of Liverpool

Agile and XP Development

Scrum Overview.

Agile and XP Development

Agile and XP Development

Real World Scrum with TFS & VSTS / Azure DevOps

Coming up: What is Agile?

Agile Development.

Presentation transcript:

Copyright © by Mark J. Sebern Software Engineering Process I SE Sprint Execution

Copyright © by Mark J. Sebern Sprint Execution Sprint execution planning Didn’t we just do sprint planning? Flow management Parallel work (multitasking) Swarming Mini-waterfall

Copyright © by Mark J. Sebern What is swarming? This?

Copyright © by Mark J. Sebern Swarming This?

Copyright © by Mark J. Sebern This? Swarming Or this?

Copyright © by Mark J. Sebern This? Swarming Or this? Can’t just help after all your own work is done. Can’t play bunchball: everyone do same story.

Copyright © by Mark J. Sebern Which Work To Start Next highest-priority item? PBI/task What if there are dependencies? Inter-task Special skills

Copyright © by Mark J. Sebern Danger of Role-Based Thinking What does the “testing expert” do before there is anything to test? Work together in rapid increments? Develop (by practice during execution) a wider range of team skills? Replace “individual” emphasis with ongoing team collaboration (not “my tasks”)

Copyright © by Mark J. Sebern Daily Scrum Daily, 15-minute (time boxed) activity How does this translate to a course project? Don’t forget the three questions!

Copyright © by Mark J. Sebern Daily Scrum Daily, 15-minute (time boxed) activity How does this translate to a course project? Don’t forget the three questions! What did I accomplish? What do I plan to work on? What is preventing me from making progress?

Copyright © by Mark J. Sebern Daily Scrum Daily, 15-minute (time boxed) activity How does this translate to a course project? Don’t forget the three questions! Identify “blocking” items that need attention What did I accomplish? What do I plan to work on? What is preventing me from making progress?

Copyright © by Mark J. Sebern Test-driven development Refactoring Simple design Pair programmin g Continuous integration Collective code ownership Coding standard Metaphor Technical Practices

Copyright © by Mark J. Sebern Task Board

Copyright © by Mark J. Sebern Burndown Chart Can be remaining hours, story points, or both; how would they be used?

Copyright © by Mark J. Sebern Burndown Chart Can be remaining hours, story points, or both; how would they be used?

Copyright © by Mark J. Sebern Sprint Report

Copyright © by Mark J. Sebern Review Sprint execution Swarming Role of experts Why not use waterfall model? Daily scrum 3 questions Technical practices Tracking: burndown, sprint report