©Alistair Cockburn 2013 Disciplined Learning: The successor to risk reduction Disciplined Learning: The successor to risk reduction Dr. Alistair Cockburn.

Slides:



Advertisements
Similar presentations
E.g Act as a positive role model for innovation Question the status quo Keep the focus of contribution on delivering and improving.
Advertisements

What Is Agile Development & What does it Imply?
©Alistair Cockburn Slide 1 Alistair Cockburn The Crystal Family of Methodologies for Software Development.
HCI in the software process Chapter 6
Agile Software Development Alistair Cockburn Addison Wesley.
1 Project Presentation Sethu Lambu Manager, IS Production Engineering GBA573 IT Project Management Summer 2004 University of San Diego Electronic-File.
NAUG NAUG Knowledge Evening – th February 2007.
Software Engineering.
Systems Analysis and Design Kendall & Kendall Sixth Edition
EXtreme Programming Quick Introduction Daniel Arraes Pereira Eduardo Lourenço Apolinário Ricardo de Oliveira Cavalcanti.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Agile Software Development Alistair Cockburn Addison Wesley.
CSC230 Software Design (Engineering)
Software Life Cycle Model
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 Core Employability Skills in the Workplace by Carmela I. Torres ILO Sub-Regional Office for East Asia National Technical Workshop & Study Programme on.
Software Testing Lifecycle Practice
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
Project Management Chapter 3. Objectives Become familiar with estimation. Be able to create a project workplan. Understand why project teams use timeboxing.
Chapter-3 Agile Development
Interviewing CIS 331. Required Skills of the Systems Analyst Technical knowledge and skills – Computer hardware, software, databases, and related devices.
CSU 670 Review Fall Software Development Application area: robotic games based on combinatorial maximization problems. Software development is about.
Introduction to Interactive Media The Interactive Media Development Process.
What is an Agile Methodology?. Delivers nearly no knowledge (or risk reduction) Knowledge comes at the “moment of truth”: final integration. Waterfall.
Some Sub-Activities within Requirements Engineering 1.Prototyping 2.Requirements Documentation 3.Requirements Validation 4.Requirements Measurements 5.Requirements.
 Systems analysts are the key individuals in the systems development process.  A systems analyst studies the problems and needs of an organization to.
WORKING YOUR WAY ITE Success depends on Working Smarter not Harder 10 THINGS EMPLOYERS LOOK FOR 1.Positive Attitude 2.Adaptability and Flexibility 3.Passion.
XP – Extreme Programming
1 Technical & Business Writing (ENG-315) Muhammad Bilal Bashir UIIT, Rawalpindi.
Technological Literacy For All Students. Manual Training: 1870’s Manual Arts: 1890’s Industrial Arts: early 1900’s to 1990’s Technology Education: Mid.
T Iteration demo T Iteration Demo Team Balboa I1 - Iteration
PBA Front-End Programming Development Organisation.
CS5103 Software Engineering Lecture 02 More on Software Process Models.
Extreme Programming Based on and
FINAL PRESENTATION OF ORGANIZATIONAL BEHAVIOUR AND ANALYSIS Prepared for : Dr. S. Kumar Group : Dollar 2 A. R. S. BANDARA - PGIA / 06 / 6317 B. A. G. K.
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
Stand Up Comedy Project/Product Management
Project Management Why do projects fail? Technical Reasons
From the customer’s perspective the SRS is: How smart people are going to solve the problem that was stated in the System Spec. A “contract”, more or less.
To RAD or not to RAD? RAD is the relatively new kid on the block. You know the one. The one with all the flashy stuff and is practically the Usain Bolt.
©Alistair Cockburn 2009 “I Come to Bury Agile, Not to Praise It” Effective Software Development in the 21st Century Alistair Cockburn
Alistair Cockburn©Humans and Technology, Inc., Slide 1 Foundations of Agile Development: Cooperative Games of Invention and Communication in.
1 Requirements Engineering for Agile Methods Lecture # 41.
Introduction to Software Engineering Muhammad Nasir Agile Software Development(2)
1 Introduction to eXtreme Programming Remko Popma Azzurri Ltd.
Jeffrey Murray Principle Test Manager – PowerPoint Problems with PowerPoint? … you can blame me!
© 2010 Alistair Cockburn The New Methodology isn't a Methodology Dr. Alistair Cockburn.
Extreme programming (XP) Advanced Software Engineering Dr Nuha El-Khalili.
Internal developer tools and bug tracking Arabic / Hebrew Windows 3.1Win95 Japanese Word, OneNote, Outlook
©Alistair Cockburn 2010 What Makes Agile Work: The New Software Engineering Getting Past “Wimpy” Agile Dr. Alistair Cockburn
© 2010 Alistair Cockburn Designing in Teams Dr. Alistair Cockburn
Slide 1 ©Alistair Cockburn 2008 Alistair Cockburn Effective Software Development in the 21st Century: The New Face Of Software.
Slide 1 ©Alistair Cockburn 2009 Project Management as Pharma: Sometimes the opposite of a good strategy is a better strategy Dr. Alistair Cockburn Humans.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
4D Simulation Impacts on Construction Management
Agile Software Development
Владимир Гусаров Директор R&D, Dell Visual Studio ALM MVP ALM Ranger
Introduction to System Analysis and Design
Hard-Agile Effective Software Development in the 21st Century
Agile Software Development The Cooperative Game
Crystal (How to make a methodology fit)
Skills needed to become a Good Software Engineer
Introduction to Magento Magento is one of the most popular ecommerce solutions in the world. But learning this powerful content management system also.
User Stories Applied, Mike Cohn Chapter 1: An Overview
Careers in Engineering
Designing in Teams The Cooperative Game
Chapter 1 (pages 4-9); Overview of SDLC
Designing in Teams Dr. Alistair Cockburn
Teaching the Next Generation Software Engineering
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Presentation transcript:

©Alistair Cockburn 2013 Disciplined Learning: The successor to risk reduction Disciplined Learning: The successor to risk reduction Dr. Alistair Cockburn

©Alistair Cockburn People... Solving a problem Creating a solution To an interpreter unforgiving of error Making decisions Where every decision has economic consequences and resources are limited. … they don’t understand which keeps changing Communicating Deciding Inventing Expressing ideas in a language … they don’t understand which keeps changing … they don’t understand which keeps changing

©Alistair Cockburn time Growth of business value Commitment to decisions (Thanks to Dr. Mary Shaw, CMU for this graph)

©Alistair Cockburn Craft Cooperative Game Knowledge Acquisition Flow Self-Awareness origami courtesy of Gery Derbier

©Alistair Cockburn Self Awareness: People don’t match formulas

©Alistair Cockburn Infinite Organization Survival Career Management Competitive Cooperative Open-ended Jazz music Finite goal-directed King-of-the-hill wrestling Poker Tennis Chess Rock-Climbing Theater Journalism Exploration Software Development Business Product Line Management IT Systems Cooperative Games: positions, moves (invent, communicate), strategies

©Alistair Cockburn I wish they’d decide what style they want! Users & Sponsors Testers Business Analysts I wish they’d decide what functions they want! A decision I wish they’d decide on the UI design already! I wish they’d think a bit more carefully before coding! Programmers Every line of code is a decision UI Designers Flow: Design=manufacturing if Inventory=Decisions!

©Alistair Cockburn Users & Sponsors UI Designers Programmers Testers Business Analysts Convert jams Users & Sponsors UI Designers Programmers Testers Business Analysts to continuous flow. Flow: Global optimization

©Alistair Cockburn Craft: People learn skills in 3 stages Shu: Learn a technique Ha: Collect techniques Ri: Invent / blend techniques

©Alistair Cockburn Disciplined Knowledge Acquisition

©Alistair Cockburn Trim to deliver on-time (or early) Delay to get more or better Payoff = Trim-the-Tail: Deliver by value or date

©Alistair Cockburn Delivers nearly no knowledge (or risk reduction) Big-Bang Design is a late-learning strategy time Knowledge comes at the “moment of truth”: final integration. cost Growth of knowledge with big-bang integration

©Alistair Cockburn Development sequence indifferent (with respect to knowledge) Delivers knowledge (risk reduction) We can pay to learn early in the project time cost Growth of knowledge with early, continuous integration

©Alistair Cockburn Develop for business value once risks are down time Knowledge growing (risk reduction) cost Business value growing Risk / learn: - business - social - technical - cost / schedule

©Alistair Cockburn Trim to deliver on-time (or early) Delay to get more or better Payoff = Trim-the-Tail: Deliver by value or date

©Alistair Cockburn Business Learning: (Risk: Are we building the right thing?) Learning:What should we build? Paper prototyping Ambassador user Early delivery Empty delivery and Manual delivery “Hothousing” - tunneling to feedback

©Alistair Cockburn Social Learning: (Risk: Can these people do the job?) Learning:How can we make them a stronger team? Early victory "Walking Skeleton” "Simplest first, worst second" [AC-sfws]

©Alistair Cockburn Technical Learning: (Risk: Why won’t our beautiful design work?) Learning:How do we correct it so it works? Micro-incremental development Walking skeleton Spikes Story splitting

©Alistair Cockburn Cost / schedule Learning: (Risk: Will we deliver it on time/budget?) Learning:How long will this really take? Core Samples Microcosm

©Alistair Cockburn Three stages per feature: Risk, Value, Tail Value Knowledge / risk reduction time Tail riskvaluetail Item1..…... item 2.….. item 3..…. item :

©Alistair Cockburn Extended by G. Benefield’s Outcomes-Options model

©Alistair Cockburn Extended by G. Benefield’s Outcomes-Options model

©Alistair Cockburn Learn Early Learn Often : beyond risk reduction