Agile in Your Life + Building NomNom Finder

Agile In Your Life

Hala Saleh http://www.halasaleh.com

@HalaSaleh1

Who Am I? •  Hala Saleh, CSM, CSP, PMP

•  History/Evolution:

Developer -> QA -> PM -> Agile Coach/ Consultant

•  Today: All of the above (ok, maybe minus Developer)

PLUS:

© 2014 Hala Saleh www.halasaleh.com

Ice? What Ice?! •  Find a partner, and take 5 minutes to find out

some cool stuff about them:

1.  If you could only eat one food for the rest of your life, what would that food be?

2.  If you had to choose 3 movies to watch for the

rest of your life, what 3 movies would you pick? 3.  What about your work/school gets you excited?


Agile Whaaat?


•  Show of hands: On a scale of 1 – 5, how familiar are you with “agile” development?

1.  Not familiar with agile at all 2.  Heard about it, not familiar with details of any specific

methodology 3.  Moderately familiar, can name/describe at least 1 agile

methodology/framework at a high level 4.  Familiar, can explain details of at least 1 agile

methodology & can name others 5.  Very familiar, can explain details of more than 1 agile

methodology & have experience implementing at least 1

HISTORY AND BACKGROUND Agile Methodology:


What does ‘Agile’ mean to you?


Quiz: What is Agile?!

•  Working in groups of 3 – 4 people, write down what you think Agile is in no more than 2 – 3 sentences. (5 minutes)

•  Share!


The BA (Before Agile) Era: A Brief History

•  In the beginning, there were factories •  Manufacturing had a known set of

requirements, and needed a highly repeatable process

•  The answer: A linear, sequential process model that produced predictable results every time


Along Came Software

•  In the 1960 and 70s, the software development industry inherited the manufacturing process model

•  The “Waterfall” model for software development:

Development

Tes9ng

Deployment

Maintenance

Requirements

Design


Then Came Trouble

•  For cases where requirements and technologies are known and do not change, waterfall works (sometimes really well!)

•  But software is complex. And customers of software are

even more complex.

•  Requirements and technologies now change faster than ever before.

•  Development teams need to be able to adapt and

respond to change in order to be competitive and fast to market.


Enter: Agile

•  In the 1980s and 90s, new software development methods emerged that were more lightweight and responsive to change.

•  In 2001, a group of 17 software development

experts and thought leaders met in Snowbird, Utah.

•  The goal: Figuring out how to better develop

software. •  The result: The Agile Manifesto (set of values)


VALUES AND PRINCIPLES Agile Methodology:


The Agile Manifesto “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

•  Individuals and interactions over processes and tools

•  Working software over comprehensive documentation

•  Customer collaboration over contract negotiation

•  Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.”* *Source: agilemanifesto.org

Agile Principles •  The Agile Manifesto is based on 12 principles. See here:

Agile Principles •  Discussion: Key Agile Principles and Takeaways


Agile: Defined

•  Agile (traditional definition): An iterative and incremental approach to developing software that incorporates continuous feedback loops, adaptability, and collaboration.


Agile: Not Just for Software! •  Agile methodologies are being used in

industries including: – Marketing, Sales, Insurance, Legal practices,

Academics, and even: Manufacturing!

•  Cool examples: – WikiSpeed - Manufacturer of ultra efficient, low-

cost cars: WikiSpeed Video –  Family Life: Agile Parenting Video – Electro-Mechanical Manufacturing: Case Study – Agile in Academics (Higher Ed)


Agile: RE-defined

•  Agile (redefined): An iterative and incremental approach to achieving an end-result (product, project, goal) that incorporates continuous feedback loops, adaptability, and collaboration.


Agile Manifesto for Education

•  Students and relationships over class plans and tools

•  Making progress over comprehensive documentation

•  Student collaboration over grade/ assignment negotiation

•  Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more. © 2014 Hala Saleh www.halasaleh.com

Self-Organizing Teams: Why?

•  What do you think of when you hear the term “self-organizing team”?

•  Self-organizing teams are 30 – 50% more

productive* •  Self-organizing teams are motivated – People are motivated by a sense of contribution,

personal growth, and autonomy –  See

Drive: The surprising truth about what motivates us

•  Accountability! * Source: Esther Derby © 2014 Hala Saleh www.halasaleh.com

Agile At My House


COMMON FRAMEWORKS Agile Methodology:


Common Agile Frameworks


Agile Frameworks: Common Themes

•  Iterative AND incremental •  Emphasize collaboration (with customer,

stakeholders, other team members)

•  Empower teams (self-organization, cross-functional team members)

•  Responsive to change

•  Create a culture and environment that values PEOPLE over PROCESS


SCRUM: A HANDS-ON INTRO Agile Methodology:


Scrum. (Scrum?!)

•  In Rugby: A scrum is a team pack where everyone acts together to move the ball down the field of play.

•  In Agile: Scrum is the most widely-adopted agile framework


Scrum Framework


Scrum Artifacts: Product Backlog

•  Prioritized list of work items: tasks, requirements (user stories). (A.k.a Stuff That Needs To Get Done)

•  Prioritization is mostly value-driven (i.e. Biggest

Bang for the Buck): –  In software: What items have the highest business

value? –  In education: What curriculum items have the highest

educational value?

•  Dynamic: Reprioritized/revisited constantly


Product Backlog Example


Priority Product Backlog Item Descrip6on

1 As a student of Advanced Algebra II, I need to complete my weekly assignment by Tuesday at 9 pm

2 As a student of Mrs. Jones’ piano class, I need to prac9ce for 45 minutes 3 days a week

3 As a student in Advanced Biology, I need to write a term paper by June 10th, 2014

4 As a crea9ve wri9ng student, I need to prac9ce free wri9ng in my journal once a day

5 As an aspiring soPware engineer, I need to spend at least two hours prac9cing and learning new technologies

Sprint Backlog: An Example

• Read Chapter 6 of Algebra textbook •  Solve Review Ques9ons •  Solve Chapter Ques9ons

P: 1 Title: Algebra Homework As a student of Advanced Algebra II, I need to complete my weekly assignment by

Tuesday at 9 pm

•  Prac9ce Pages 13-‐14 in Piano book (Monday) •  Prac9ce Pages 20-‐22 in Piano book (Wednesday) • Review Pages 13-‐14 AND 20-‐22 in Piano book (Friday)

P: 2 Title: Piano Prac9ce As a student of Mrs. Jones’ piano class, I need to prac9ce for 45 minutes 3 days a

week

•  Finish reading last chapter of Fluorescent Plant Life • Write outline for Mutant Plant Life research paper

P: 3 Title: Biology Term Paper As a student in Advanced Biology, I need to write a term paper by June 10th, 2014

•  Sprint Goal: Finish weekly assignments on time and finish outline of Biology paper


Product Backlog: User Stories

Title As a <user>

I want to <action>

so that <benefit>

Priority: Size:

Front:

Back (Acceptance Criteria):

Acceptance Criteria: When <user does X> Then <Y should happen> When <user does X> Then <Y should happen>


Scrum Artifacts: Team Task Board


Scrum Activities: Daily Scrum

•  Also called “Daily Standup”

•  3 Questions:

–  What did you do yesterday?

–  What will you do today?

–  Is there anything blocking/ impeding you?

•  Time-boxed to 15 minutes

•  NOT for status, rather for peer accountability and

coordination/ collaboration © 2014 Hala Saleh www.halasaleh.com

Scrum Activities: Sprint Review/ Demo

•  Team shares what they’ve accomplished

•  Review shows real progress

•  Product Owner either accepts or rejects

work items at the review

•  Rejected items get put back into the

backlog (may be reprioritized) © 2014 Hala Saleh www.halasaleh.com

Scrum Activities: Sprint Retrospective

•  Regularly and frequently, reflect as a team on

what is/is not working

•  Whole team participates

•  Goal is to identify and acknowledge:

– Things that are going well

– Things that could be improved

–  Specific actions the team can take to improve © 2014 Hala Saleh www.halasaleh.com

Retrospectives: A Deeper Look

•  Learn how to facilitate retrospectives; they are a

powerful tool.

–  Read: Agile Retrospectives: Making Good Teams Great

(Esther Derby, Diana Larsen)

•  Retrospectives can be a great addition to a project-

based learning environment

•  Retrospectives contribute to continuous improvement

•  Retrospectives are part of a powerful Inspect-and-

Adapt cycle © 2014 Hala Saleh www.halasaleh.com

Retrospectives: An Example

BUILDING NOMNOM FINDER Agile in Your Life:


NomNom Finder: Find Food Trucks now


NomNom Finder: Birth of an idea


NomNom Finder: Team Gets to Work


NomNom Finder: 52 Hours Later


RESOURCES Agile in Your Life:


Presentation Links

•  WikiSpeed - Manufacturer of ultra efficient, low-cost cars: WikiSpeed Video

(http://www.youtube.com/watch?v=x8jdx-lf2Dw) •  Family Life: Agile Parenting Video (http://www.ted.com/talks/bruce_feiler_agile_programming_for_your_family.html) •  Electro-Mechanical Manufacturing: Case Study (http://agile2010.agilealliance.org/files/A%20Non-Software%20Scrum%20Experience%20PDF.pdf) •  Agile in Academics (Higher Ed) (http://cf.agilealliance.org/program/files/9604.pdf) •  See Drive: The surprising truth about what motivates us (http://www.youtube.com/watch?v=u6XAPnuFjJc)


Agile in Your Life + Building NomNom Finder

Software

Transcript of Agile in Your Life + Building NomNom Finder