• Save
120715 agile requirements_handout
Upcoming SlideShare
Loading in...5
×
 

120715 agile requirements_handout

on

  • 733 views

Slide set on "Agile Software Requirements" used throughout open space discussions at Barcamp Karlsruhe 2012 in Germany (language of slide set: German)

Slide set on "Agile Software Requirements" used throughout open space discussions at Barcamp Karlsruhe 2012 in Germany (language of slide set: German)

Statistics

Views

Total Views
733
Views on SlideShare
733
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

120715 agile requirements_handout 120715 agile requirements_handout Presentation Transcript

  • Agile RequirementsWas ist das? – Diskussion – ErfahrungsaustauschAndreas Birk14. und 15. Juli 2012, Open-Space Sessions beim Barcamp Karlsruhe 2012
  • EinleitungDieser Foliensatz fasst Informationen zu den Open Space Sessions beim Barcamp Karlsruhe 2012 zum Thema“Agile Software Requirements” zusammen. Die Sessions wurden vorgeschlagen von Andreas Birk und moderiertvon Andreas Birk und Heiko Stapf.Die Foliensammlung wurde nicht als zusammenhängender Vortrag konzipiert, sondern sie sammelt die zuverschiedenen Punkten der Sessions gezeigten Abbildungen. Für diese nachträgliche Dokumentation wurdenGliederungsfolien als Kapitelüberschriften mit kurzen Einleitungen eingefügt.Weitere Informationen zu den Sessions sind auf den folgenden Webseiten vorhanden. Zusätzliche Details können beiden Moderatoren angefragt werden.Fotoprotokoll der Diskussionsergebnisse:https://www.openpm.info/display/openPM/Agiles+Requirements+ManagementSession-Ergebnisse des Barcamp Karlsruhe 2012 mit weiteren Links:http://www.barcamp-karlsruhe.de/networks/wiki/index.Sessionergebnisse-2012Kontaktdaten der Moderatoren:http://www.xing.com/profile/Andreas_Birkhttp://www.xing.com/profile/Heiko_Stapf14./15. Juli 2012 Copyright © 2012, Software.Process.Management 2
  • Warum agiles Requirements-Management? Was ist agile Entwicklung?14./15. Juli 2012 Copyright © 2012, Software.Process.Management 3
  • Herkömmliches Requirements-Managementin der Sackgasse?14./15. Juli 2012 Copyright © 2012, Software.Process.Management 4
  • Agil 1.014./15. Juli 2012 Copyright © 2012, Software.Process.Management 5
  • Agil 2.014./15. Juli 2012 Copyright © 2012, Software.Process.Management 6
  • http://agilemanifesto.org14./15. Juli 2012 Copyright © 2012, Software.Process.Management 7
  • Principles behind the Manifesto Our highest priority is to satisfy the customer Working software is the primary measure of progress. through early and continuous delivery of valuable software. Welcome changing requirements, even late in Agile processes promote sustainable development. development. Agile processes harness change for The sponsors, developers, and users should be able to the customers competitive advantage. maintain a constant pace indefinitely. Deliver working software frequently, from a Continuous attention to technical excellence couple of weeks to a couple of months, with a and good design enhances agility. preference to the shorter timescale. Business people and developers must work Simplicity--the art of maximizing the amount together daily throughout the project. of work not done--is essential. Build projects around motivated individuals. The best architectures, requirements, and designs Give them the environment and support they need, and emerge from self-organizing teams. trust them to get the job done. The most efficient and effective method of At regular intervals, the team reflects on how conveying information to and within a development to become more effective, then tunes and adjusts team is face-to-face conversation. its behavior accordingly. http://agilemanifesto.org/principles.html14./15. Juli 2012 Copyright © 2012, Software.Process.Management 8
  • Scrum Daily Scrum Meeting Sprint 1-4 Weeks Product Sprint Potentially Backlog Backlog Shipable Product Increment Sprint Collect Input & Agile Iteration Acceptance & Planning Requirements Cycle (Sprint) Delivery Meeting14./15. Juli 2012 Copyright © 2012, Software.Process.Management 9
  • Requirements in der agilen Entwicklung  User Stories  Requirements neu denken  Agile Requirements skalieren (Frameworks von Dean Leffingwell)14./15. Juli 2012 Copyright © 2012, Software.Process.Management 10
  • Requirements in der agilen Entwicklung Kommunikation Testfälle Feedback14./15. Juli 2012 Copyright © 2012, Software.Process.Management 11
  • User Story Example rebook past trip As a frequent flyer I want to rebook a past trip, so that I save time booking trips I take Source: Mike Cohn: http://blog.mountaingoatsoftware.com/advantages-of-the-as-a-user-i-want-user-story-template14./15. Juli 2012 Copyright © 2012, Software.Process.Management 12
  • User Story Template http://blog.mountaingoatsoftware.com/advantages-of-the-as-a-user-i-want-user-story-templateA standardized form to write user stories ensurescertain quality characteristics: <Title> As a <user> I want <functionality> So that <business Source: Mike Cohn: value>14./15. Juli 2012 Copyright © 2012, Software.Process.Management 13
  • INVESTUser Stories shall be: Independent Negotiable Valuable Estimable Small Testable14./15. Juli 2012 Copyright © 2012, Software.Process.Management 14
  • Agile Requirements StatementsThought Provoking? No requirements any more User stories are not requirements Throw away the requirements after the end of an iteration14./15. Juli 2012 Copyright © 2012, Software.Process.Management 15
  • Source: Dean Leffingwell. Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise. Addison-Wesley, 2010.14./15. Juli 2012 Copyright © 2012, Software.Process.Management 16
  • Tools für agiles Requirements-Management14./15. Juli 2012 Copyright © 2012, Software.Process.Management 17
  • 14./15. Juli 2012 Copyright © 2012, Software.Process.Management 18
  • http://www.uservoice.com/blog/founders/trello-google-docs-product-management/14./15. Juli 2012 Copyright © 2012, Software.Process.Management 19
  • 14./15. Juli 2012Copyright © 2012, Software.Process.Management http://www.atlassian.com/de/software/greenhopper/overview/screenshot-tour20
  • Agile RM-Tools inSEHR GROSSEN UmgebungenFür die agile Entwicklung in sehr großen Umgebungen werden mitunter Tool-Lösungeneingesetzt, die auf etablierten Application Lifecycle Management (ALM) Werkzeugenbasieren. Ein Beispiel ist HP Quality Center / ALM, das die Prozesse von denRequirements bis zu den Tests abdeckt und mit Entwicklungsumgebungen integriert.Zur Unterstützung der agilen Entwicklung werden dann meist unternehmensspezifischeAnpassungen auf die traditionelle Tool-Plattform aufgesetzt. Beispiele kann ich hier nichtzeigen, da sie für die Veröffentlichung nicht frei gegeben sind.Wer an detaillierteren Informationen über die Bausteine derartiger Tool-Lösungen für “AgileRM in-the-Large” interessiert ist, kann mich sehr gerne über die folgende E-Mail-Adresseansprechen: info@swpm.de14./15. Juli 2012 Copyright © 2012, Software.Process.Management 21
  • Praktiken (auch) für agiles Requirements-Management14./15. Juli 2012 Copyright © 2012, Software.Process.Management 22
  • http://guide.agilealliance.org/14./15. Juli 2012 Copyright © 2012, Software.Process.Management 23
  • Gesamtsicht auf das System wahren: Anleihen beim Requirements Abstraction Model (RAM) machen14./15. Juli 2012 Copyright © 2012, Software.Process.Management 24
  • Requirements Abstraction Model (RAM) T. Gorschek and C. Wohlin. “Requirements Abstraction Model”, Requirements Engineering Journal, 11, pp. 79–101, 2006.14./15. Juli 2012 Copyright © 2012, Software.Process.Management 25
  • Kontakt Dr. Andreas Birk Software.Process.Management info@swpm.de http://www.swpm.de Blog & Resources http://MakingOfSoftware.com Xing, LinkedIn, Google+14./15. Juli 2012 Copyright © 2012, Software.Process.Management 26
  • Bildnachweis Folie 4 iStock Photo 000004145220 Folie 5 Creative Commons, Brian Scott, ”Jumping Impala”, CC BY-NC-ND 2.0 http://www.flickr.com/photos/brianscott/5474796454/ Folie 6 Creative Commons, Gary Eyring, ”Cheetah Run 4“, CC BY-NC-ND 2.0 http://www.flickr.com/photos/geyring/5290188093/ Folie 11 Microsoft Clip Art MP900430490 Folie 18 Creative Commons, levelTen_Colin, ”task-board 004“, CC BY-SA 2.0 http://www.flickr.com/photos/levelten/4188756530/ Folie 26 Andreas Birk14./15. Juli 2012 Copyright © 2012, Software.Process.Management 27