Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Upcoming SlideShare
How to survive in Agile world
Next
Download to read offline and view in fullscreen.

Share

Agile

Download to read offline

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

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

Agile

  1. 1. So you want to build somethingdifferentlyhttp://forum.nationstates.net/viewtopic.php?f=23&t=221515&start=75
  2. 2. 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!● Well 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
  3. 3. Lets get down to earth● Its a challenge for everybody, but most of all - for managers● Cant be done like flipping a switch - changes take time● There is no single recipe: its not about how to implementagile: its about understanding who your team members are.● Code will be defective if you dont write tests (sorry).● When not done properly, your team will loose their velocity● Deadlines may be still hard to reach (but youll know earlier).● Projects will be complicated and complex anyway (thats theway things are, dude)● There is no fixed process. Dont even think about one.http://spawnvscrow.xanga.com/
  4. 4. Whats 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. Dont assume you know better.● Consistency - if you do something - do ithttp://plan-delegate-manage.com/effective-delegation-means-employee-engagement/
  5. 5. 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
  6. 6. Use the flow, dudeWhat is this flow anyway?Mihaly CsikszentmihalyiOptimal ExperienceClear Goals + Immediate Feedback + Optimal ChallengeDont wake people, unless you really needtoHoly sh!t, its that late already?How interruptions take people out of flow:○ daydreaming○ contexthttp://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
  7. 7. How we started● A bunch of guys with no idea about agile or scrum,● How kanban replaced pretty much everything not related toactual 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
  8. 8. 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 projectthey work on. Do not isolate them!● use strengths! Even if some appear as weaknesses - identifywhat your guys are good at!● stick to the primary roles. Dont assume anything.http://tammyworld2012.blogspot.com/2012/07/ascending-mt-everest.html
  9. 9. 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) benefitswhole team, not just individuals who did something● team works much better when everyone knows well whatthey need to do to reach the goal● short sprints help take turns if things dont go well andmeasure team velocity● teams tend to organize themselves internally which booststhings up even further
  • betlejewska

    Jul. 2, 2014

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

Views

Total views

261

On Slideshare

0

From embeds

0

Number of embeds

1

Actions

Downloads

4

Shares

0

Comments

0

Likes

1

×