Lean Agile Software Projects - Northwestern University
Lean Agile SoftwareProjectsChris RiesbeckElectrical Engineering and Computer ScienceLearning SciencesNorthwestern University1Wednesday, October 9, 2013
Starting a Project?2Wednesday, October 9, 2013
3Wednesday, October 9, 2013
Feature Presentation:Agile Intervention4Wednesday, October 9, 2013
Week 1WorkIt!We've got the green light for ourWorkIt! app. They love the idea of apersonalized audio workout coachand exercise tracker.Your personal trainerhands-free coachinginstant diary100's of downloadableroutines5Wednesday, October 9, 2013
Week 1OK, let's figureout what weneed to build.6Wednesday, October 9, 2013
Week 1. a page tomanage authors,users, and profiles.A phone app tocall out thesteps.OK, let's figureout what weneed to build.We'll needa server,home page,page to defineworkoutroutines.OK, here's aschedule. Let'sget going!UseradminmoduleWorkoutentrymoduleUser signup, !Week 1Week 2Week 3Week 4Week 5Week 66Wednesday, October 9, 2013
Week 2Where's mynew useradminpage?I spent 3 hourson it. Iuploaded itlast night.Were you workingon that? I may havecovered it up when Iuploaded my codethis morning!Where is thenew database?It's on mylaptop .that I left onthe shuttle7Wednesday, October 9, 2013
Week 3Lessee.whatto do next?Task listWednesday, October 9, 2013Validate emailsAllow 24-hour specialsAdd drag-and-dropAdd logout buttonFix transitionAdd multiple emailsFix typo on who we areAdd Facebook linkageReformat login formDo eurosAllow notificationsAdd sleep modeFix repeat glitchRefactor db schema8
Week 3Lessee.whatto do next?Eeny meeny.Fix transitionAdd multiple emailsFix typo on who we areAdd Facebook linkageReformat login formDo eurosAllow notificationsAdd sleep modeFix repeat glitchRefactor db schemaAdd average to statsAdd median to statsOnly let admins deleteReorganize css filesTaskUpdateliststats unit testsAdd Safari supportAnimate intro logoRemove premium linkUpdate Ruby gemsFind div-by-0 bugChange to daily logsValidate emailsAllow 24-hour specialsAdd drag-and-drop.this looks good!8Wednesday, October 9, 2013
Week 3Was that onthe list?Fix transitionAdd multiple emailsFix typo on who we areAdd Facebook linkageReformat login formDo eurosAllow notificationsAdd sleep modeFix repeat glitchRefactor db schemaThe logo Add average to statsAdd median to statsdances now! Only let admins deleteReorganize css filesTaskUpdateliststats unit testsAdd Safari supportAnimate intro logoRemove premium linkUpdate Ruby gemsFind div-by-0 bugChange to daily logsValidate emailsWhatAllowabout24-hour specialsAdd drag-and-dropthe Facebooklink?9Wednesday, October 9, 2013
Week 4Project progressreport.10Wednesday, October 9, 2013
Week 4Project progressreport.I did the UIDale didphone appKim did the DBKarl did theserver codeand ourproject is. toastIt's just ascratch. I'll beout of tractionin 5 weeks.10Wednesday, October 9, 2013
Week 5We presentnext week!UseradminmoduleWorkoutentrymoduleUser signup, !Week 1Week 2Week 3Week 4Week 5Week 611Wednesday, October 9, 2013
Week 5We didn't getthat far in theschedule.Can we demodownloading a routineand working out?We didn't getthere either.Can we atleast demogetting aroutine?We presentnext week!Signing on!What can wedemo?UseradminmoduleWorkoutentrymoduleUser signup, !Week 1Week 2Week 3Week 4Week 5Week 611Wednesday, October 9, 2013
Suddenly.12Wednesday, October 9, 2013
Well, that was adisaster. What arun of bad luck.13Wednesday, October 9, 2013
Well, that was adisaster. What arun of bad luck.We're yourGuardian Agiles.We saw youwere havingproblems.Who are thoseguys?Luck had nothing todo with it– watch!13Wednesday, October 9, 2013
This is classiccode chaos.It gets worseand worse untila projectcollapses.14Wednesday, October 9, 2013
You had toomany tasks tokeep track of.And no focuson what reallymattered.15Wednesday, October 9, 2013
Your busfactor was 1That's how fewpeople need toget hit by a busfor your projectto fail.16Wednesday, October 9, 2013
Here's yourbiggestproblem of all.Your schedulesaved the bestfor last, i.e.,never.17Wednesday, October 9, 2013
I guess we haveto try harder.18Wednesday, October 9, 2013
I guess we haveto try harder.Not harder.Different. One keyidea–early value–and a few practicescan help a lot.You're going toget a chance todo this again.We'll popin to help.Here wego.18Wednesday, October 9, 2013
Week 1. a page tomanage authors,users, and profiles.A phone app tocall out thesteps.We'll need aserver, homepage, page todefine workoutroutines.19Wednesday, October 9, 2013
Week 1. a page tomanage authors,users, and profiles.A phone app tocall out thesteps.We'll need aserver, homepage, page todefine workoutroutines.Your value isgetting lost infeatures and code.19Wednesday, October 9, 2013
Week1Start with adifferent question.20Wednesday, October 9, 2013
Week1Start with adifferent question.A userentering anexercise goalprofile.What areyour userscenarios?The ones youmust have inyour MVP?An expertauthoring aworkoutroutine.A user doing aroutine with thephone calling outthe steps.Great! Putthosescenarios intoa releasebacklog.A user finding anddownloading a routinethat fits her profile.20Wednesday, October 9, 2013
Week 1OK, we've got ourbacklog. Let's startcoding!Let's decidewhat to dofirst.Well, clearly weneed a page tocreate users.and a wayto author newworkoutroutines.Scenariosexpert authors routineuser adds profileuser downloads routineapp calls out routine stepsWednesday, October 9, 201321
Week 1Let's decidewhat to dofirst.OK, we've got ourbacklog. Let's startcoding!Scenariosexpert authors routineuser adds profileWell, clearly weneed a page tocreate users.and a wayto author newworkoutroutines.None of thesetest your corevalue prop!user downloads routineapp calls out routine stepsWednesday, October 9, 201321
Week 1What's the makeor break scenario?Scenariosexpert authors routineuser adds profileuser downloads routineapp calls out routine stepsWednesday, October 9, 201322
Week 1What's the makeor break scenario?A user doing aworkout with thephone callingout the steps.Then dothat first.If it doesn't work,nothing elsematters?Scenariosexpert authors routineDon't defer value.Build as if eachrelease might beyour last.user adds profileuser downloads routineapp calls out routine stepsWednesday, October 9, 201322
Week 1OK, let'simplementrunning a workoutroutine.We should be able toget that scenariodone in two weeksScenariosexpert authors routineuser adds profileuser downloads routineapp calls out routine stepsWednesday, October 9, 201323
Week 1OK, let'simplementrunning a workoutroutine.We should be able toget that scenariodone in two weeksThat's toovague. It'sgoing to slip.Scenariosexpert authors routineuser adds profileuser downloads routineapp calls out routine stepsWednesday, October 9, 201323
Week1Set hard deadlines.ZFR: zero feature release (MVP skeleton).All key parts (db, server, app, .) runningand talking to each other.One-week timeboxeswork well.only if neededZFRRelease 1Release 2Release 3FinalReleaseDemo!Week 1Week 2Week 3Week 4Week 5Week 6Each week isan internalrelease you canuser test.24Wednesday, October 9, 2013
Week 1In a week?How can wepossibly.25Wednesday, October 9, 2013
Week 1In a week?How can wepossibly.DTSTTCPW: Do the simplestthing that could possibly work.Focus onone new userfunction.DTSTTCPW!Don't build adatabaseeditor if a textfile will work.Backlog anythingnot essential forvalidated learning.Do you reallyneed user loginjust now?25Wednesday, October 9, 2013
Week 1OK, let's get started. I'll dothe UI, Kim the DB, .26Wednesday, October 9, 2013
Week 1OK, let's get started. I'll dothe UI, Kim the DB, .Don't dealout tasks.And don't silo!Silos: Separating developers byspecialized skills and functionality.26Wednesday, October 9, 2013
Week 1Swarm! Worktogether to get onestory done beforestarting another.Make just one queue,most important storiesfirst. Take the next one inline when you're ready, nomatter what it is.StoryUser canuploadgameTo DofileuploadWednesday, October 9, 2013avataredit pageavatarlist pageDonegameparseruserjointeamUserscan teamupUserscan editavatarsIn ProcesscreateteamThis will reducework in progress,and cross-train toimprove your busfactor.Agile Task Board: An project information radiator.27
Week 1At last, timeto code!I put the webserver on mydorm desktopwith FTP.Everyone, besure email theteam whenyou're workingon a file!Scenariosexpert authors routineuser adds profileuser downloads routineapp calls out routine stepsWednesday, October 9, 201328
Week 1I put the webserver on mydorm desktopwith FTP.At last, timeto code!Everyone, besure email theteam whenyou're workingon a file!Repeat after meDon't managecode manually!Scenariosexpert authors routineSource controluser adds profileuser downloads routineapp calls out routine stepsWednesday, October 9, 201328
Week 1Put everything, code,documentation,sketches, . in a sourcecontrol repository.Make sureeveryone checksout a copy atleast daily.A cloud solutionlike githubworks well.29Wednesday, October 9, 2013
Week 1. 2.30Wednesday, October 9, 2013
Week 2Let's start onthe nextscenario!We did it! We had tosimplify a lot but itworks. What a push.31Wednesday, October 9, 2013
Week 2Let's start onthe nextscenario!We did it! We had tosimplify a lot but itworks. What a push.Not yet.Somethingway moreimportant.Test what you've builtwith some real users.Wednesday, October 9, 2013Remember:Build–Measure–Learn.OK -- I can take care ofgetting this out to ourtest users.31
Week 2OK, some usersare usingRelease 1.Now for thenext scenario.32Wednesday, October 9, 2013
Week 2OK, some usersare usingRelease 1.Now for thenext scenario.Not yet.Reflectfirst!What didn't workout so well thisfirst iteration?Wednesday, October 9, 2013Why not? Whatchange might help?32
Week 2One of us didn'tuse the sourcecontrol system.33Wednesday, October 9, 2013
Week 2One of us didn'tuse the sourcecontrol system.OK, that happens.Why not? Whatwould fix it?"Try harder"is not a goodanswer.I'm on Windows. Ihad trouble usinggit in a commandwindow.I've installed a GUIplug-in which shouldmake it easier for me.33Wednesday, October 9, 2013
Week 2OK, we're testing,we've changedsome processes.Now for thenext scenario.Let's startcoding!Scenariosexpert authors routineuser adds profileuser downloads routineapp calls out routine stepsWednesday, October 9, 201334
Week 3. 4.35Wednesday, October 9, 2013
We did it. Everyweek, we pickedthe next mostimportantscenarios andmade it work.Thanks, GuardianAgiles!!!Remember: early value backlogs swarm scenarios timeboxes source control reflect and improveGood luck!Often it wasn't whatwe originallyplanned to do at all.36Wednesday, October 9, 2013
What about you?Could you use someGuardian Agiles?37Wednesday, October 9, 2013
Readings!!!!!!The Agile Samurai. Jonathan Rasmussen. PragmaticBookshelf, 2010, especially Parts I and IVJim Murphy's Agile For Startups slidesEric Ries' Startup Lessons Learned blogMike Cohn's Succeeding with Agile blogElisabeth Hendrickson's Agile Acid TestIntro to Extreme Programming38Wednesday, October 9, 2013
workout routines. OK, here's a schedule. Let's get going! User admin module Workout entry module User sign up, enter profile Download custom workout Workout Caller Demo! Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Wednesday, October 9, 2013
18.2 Lean and Agile Manufacturing Paradigms for Academia 242 18.3 Lean and Agile Manufacturing Paradigms for Consultants 242 18.4 Lean and Agile Manufacturing Paradigms for Practising Engineers 243 18.5 Lean and Agile Manufacturing Paradigms for Practising Managers243 18.6 L
How do Lean & Agile INTERSECT? 6 Agile is naturally lean and based on small batches Agile directly supports six principles of lean thinking Agile may be converted to a continuous flow system Womack, J. P., & Jones, D. T. (1996). Lean thinking: Banish waste and create wealth in your corporation.New York, NY: Free Press. Reinertsen, D. G. (2009). The principles of product development flow .
Agile Estimating and Planning by Mike Cohn Agile Game Development with Scrum by Clinton Keith Agile Product Ownership by Roman Pichler Agile Project Management with Scrum by Ken Schwaber Agile Retrospectives by Esther Derby and Diana Larsen Agile Testing: A Practical Guide for Testers and Agile Teams by Lisa Crispin and .
1. The need for an agile way of working 6 2. The need for an agile way of working 9 3. Agile Core Values - Agile Project Management Vs. 10 Agile Event Management 4. Agile principles 12 _Agile Principles of Agile Project Management 13 _Agile Principles of VOK DAMS Agile Event Management 14 5. Agile Methods 16 _Scrum in Short 16 _Kanban in Short 18
The most popular agile methodologies include: extreme programming (XP), Scrum, Crystal, Dynamic Sys-tems Development (DSDM), Lean Development, and Feature Driven Development (FDD). All Agile methods share a common vision and core values of the Agile Manifesto. Agile Methods: Some well-known agile software development methods include: Agile .
1.1 Purpose of the Agile Extension to the BABOK Guide1 1.2 What is Agile Business Analysis?2 1.3 Structure6 Chapter 2:The Agile Mindset 2.1 What is an Agile Mindset?7 2.2 The Agile Mindset, Methodologies, and Frameworks8 2.3 Applying the Agile Mindset9 2.4 Agile Extension and the Agile Ma
Agile World View "Agility" has manydimensions other than IT It ranges from leadership to technological agility Today's focus is on organizational & enterprise agility Agile Leaders Agile Organization Change Agile Acquisition & Contracting Agile Strategic Planning Agile Capability Analysis Agile Program Management Agile Tech.
AGILE TESTING For agile testers, test engineers, test managers, developers, technical leads. Ensure the production of effective and valuable software. Agile Fundamentals Agile Programming Agile Software Design Agile Fundamentals Agile Testing Agile Test Automation ICP CERTIFIED PROFESSIONAL ICP CERTIFIED PROFESSIONAL ICP-PRG CERTIFIED .
