agile

9
So you want to build something differently http://forum.nationstates.net/viewtopic.php?f=23&t=221515&start=75

Upload: chipoludnie

Post on 14-Dec-2014

126 views

Category:

Technology


1 download

DESCRIPTION

Prezentacja Tomasza Wiszkowskiego z Google, wygłoszona 23.04.2013 na spotkaniu CHI Południe - społeczności branży user experience.

TRANSCRIPT

Page 1: Agile

So you want to build something differently

http://forum.nationstates.net/viewtopic.php?f=23&t=221515&start=75

Page 2: Agile

Agile will change everything● All is going to be just freaking awesome just like that!

● One simple rule will fix all your current and new projects!

● People will simply organize themselves like bees in a hive!

● Code will be pure and defect-free!

● We'll keep all the deadlines!

● No more productivity issues!

● Fixed costs, fixed time, fixed everything!

● Well established process!

● $$$

So... ever seen Equilibrium, the movie? 1984 maybe?

http://metropolisoftomorrow.tumblr.com

Page 3: Agile

Let's get down to earth

● It's a challenge for everybody, but most of all - for managers

● Can't be done like flipping a switch - changes take time

● There is no single recipe: it's not about how to implement agile: it's about understanding who your team members are.

● Code will be defective if you don't write tests (sorry).

● When not done properly, your team will loose their velocity

● Deadlines may be still hard to reach (but you'll know earlier).

● Projects will be complicated and complex anyway (that's the way things are, dude)

● There is no fixed process. Don't even think about one.http://spawnvscrow.xanga.com/

Page 4: Agile

What's so challenging?

● Change way of thinking - drop old habits.

● Accepting the roles: PO, TL, SM.

● Empowering people: involve team.

● Listening to your people and discovering their strengths

● Allow the team to form

● Try Hard? or Try Good?

● Use your team members strengths. Quick? Thorough? Good!

● Stick to the roles. Don't assume you know better.

● Consistency - if you do something - do it

http://plan-delegate-manage.com/effective-delegation-means-employee-engagement/

Page 5: Agile

a bit of theory

● so.. what is it all about?

● A word on Manifesto: breaking the old rules.

● and what is an iteration? sprint? backlog?

● how is the process defined?

● ok, so.. how is that different from waterfall?

● kanban...?

● how rigid is this methodology? can we go beyond that? kaizen

● Extras (pair programming, extreme programming...)

● Variants (Software Craftsmanship etc)http://i-used-to-have-this.link/but-i-rearranged-the-slides/and-forgot-to-copy-it/sorry

Page 6: Agile

Use the flow, dude

What is this flow anyway?Mihaly CsikszentmihalyiOptimal ExperienceClear Goals + Immediate Feedback + Optimal Challenge

Don't wake people, unless you really need to

Holy sh!t, it's that late already?How interruptions take people out of flow:○ daydreaming○ context

http://www.shmula.com/flow-economy-of-motion-and-thought/427/http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Challenge_vs_skill.svg/300px-Challenge_vs_skill.svg.png

Page 7: Agile

How we started

● A bunch of guys with no idea about agile or scrum,

● How kanban replaced pretty much everything not related to actual work?

● Replacing meetings!

● Using feedback to improve work

● Emerging focus teams

● How people found their flow

● How we managed to go through the tough times.

● How we got more folks

● Our special forceshttp://lounous.com/?p=3405

Page 8: Agile

what we figured

● keep together people who think differently

● keep perspective - keep your options

● allow people to plan their work. The more involved they are, the better results!

● share with your team any news that is relevant to the project they work on. Do not isolate them!

● use strengths! Even if some appear as weaknesses - identify what your guys are good at!

● stick to the primary roles. Don't assume anything.

http://tammyworld2012.blogspot.com/2012/07/ascending-mt-everest.html

Page 9: Agile

boosts & benefits

● take advantage of the fact you are the owner of the process

● mixing work that needs to be done before (ux) and after (tests) can be organized much better than in regular flow

● expecting evidence of work (documentation, source) benefits whole team, not just individuals who did something

● team works much better when everyone knows well what they need to do to reach the goal

● short sprints help take turns if things don't go well and measure team velocity

● teams tend to organize themselves internally which boosts things up even further