meetjs summit 2016 - controll the chaos

42
Control the chaos working in team by Bartosz Grzegorczuk @BGrzegorczuk

Upload: bartosz-grzegorczuk

Post on 15-Jan-2017

175 views

Category:

Lifestyle


0 download

TRANSCRIPT

Page 1: Meetjs summit 2016 - Controll the chaos

Control the chaosworking in team

by Bartosz Grzegorczuk @BGrzegorczuk

Page 2: Meetjs summit 2016 - Controll the chaos

!ey call me Mutha’ F*cka Jones

http://www.moviestarspicture.com/photos/jamie-foxx-filmography/Jamie-Foxx-in-film-Horrible-Bosses-2-2014.jpg

Page 3: Meetjs summit 2016 - Controll the chaos

John Kovalsky

http://i.imgur.com/KxPrM.jpg

Page 4: Meetjs summit 2016 - Controll the chaos

https://platecultureblog.files.wordpress.com/2015/04/question-marks-11.jpg

Page 5: Meetjs summit 2016 - Controll the chaos

Communication

Page 6: Meetjs summit 2016 - Controll the chaos

Chinese whispers

http://myitforum.com/myitforumwp/wp-content/uploads/2012/07/whisper.png

Page 7: Meetjs summit 2016 - Controll the chaos

Chinese whispersExecutives

Project Managers

DevelopersUX

Analytics

Page 8: Meetjs summit 2016 - Controll the chaos

Sources of communication problems• variety of people • different perceptions & viewpoints • different domains • language barriers • people rotation

link czy coś

Page 9: Meetjs summit 2016 - Controll the chaos

Communication problems

http://image.slidesharecdn.com/lundbergmediaworkshoppersuasivecommunicationexcerpt-100917105512-phpapp02/95/persuasive-communication-3-728.jpg?cb=1423129947

Page 10: Meetjs summit 2016 - Controll the chaos

What can we do?

Page 11: Meetjs summit 2016 - Controll the chaos

Different specialists• Testers • Designers • Analytics • Business/Management • Developers • Public relations

Page 12: Meetjs summit 2016 - Controll the chaos

Testers

https://escaperoute.files.wordpress.com/2011/01/software-testers-breaking-code.jpg

Page 13: Meetjs summit 2016 - Controll the chaos

Communication with testers• Use bug tracking system (Redmine, Jira) • Omit direct emails - they are evil! • Agree best form of tickets • Establish common jargon • Set proper bugs priorities

Page 14: Meetjs summit 2016 - Controll the chaos

Communication with testers• Use bug tracking system (Redmine, Jira) • Omit direct emails - they are evil! • Agree best form of tickets • Establish common jargon • Set proper bugs priorities

Page 15: Meetjs summit 2016 - Controll the chaos

Communication with testers• Use bug tracking system (Redmine, Jira) • Omit direct emails - they are evil! • Agree best form of tickets • Establish common jargon • Set proper bugs priorities

Page 16: Meetjs summit 2016 - Controll the chaos

Communication with testers• Use bug tracking system (Redmine, Jira) • Omit direct emails - they are evil! • Agree best form of tickets • Establish common jargon • Set proper bugs priorities

Page 17: Meetjs summit 2016 - Controll the chaos

Communication with testers• Use bug tracking system (Redmine, Jira) • Omit direct emails - they are evil! • Agree best form of tickets • Establish common jargon • Set proper bugs priorities

Page 18: Meetjs summit 2016 - Controll the chaos

Designers

http://www.moooi.com/sites/default/files/styles/designer/public/designers/jaimehayon.jpg?itok=1NCkeq8_

Page 19: Meetjs summit 2016 - Controll the chaos

Communication with designers• Choose suitable files repository (Dropbox) • Organise repository structure • Explain them things • Propose alternative solutions • Ask questions • Use style guide tools (SourceJS, InVision)

Page 20: Meetjs summit 2016 - Controll the chaos

Communication with designers• Choose suitable files repository (Dropbox) • Organise repository structure • Explain them things • Propose alternative solutions • Ask questions • Use style guide tools (SourceJS, InVision)

Page 21: Meetjs summit 2016 - Controll the chaos

Communication with designers• Choose suitable files repository (Dropbox) • Organise repository structure • Explain them things • Propose alternative solutions • Ask questions • Use style guide tools (SourceJS, InVision)

Page 22: Meetjs summit 2016 - Controll the chaos

Communication with designers• Choose suitable files repository (Dropbox) • Organise repository structure • Explain them things • Propose alternative solutions • Ask questions • Use style guide tools (SourceJS, InVision)

Page 23: Meetjs summit 2016 - Controll the chaos

Communication with designers• Choose suitable files repository (Dropbox) • Organise repository structure • Explain them things • Propose alternative solutions • Ask questions • Use style guide tools (SourceJS, InVision)

Page 24: Meetjs summit 2016 - Controll the chaos

Communication with designers• Choose suitable files repository (Dropbox) • Organise repository structure • Explain them things • Propose alternative solutions • Ask questions • Use style guide tools (SourceJS, InVision)

Page 25: Meetjs summit 2016 - Controll the chaos

Business / Management

https://www.youtube.com/watch?v=BKorP55Aqvg

Page 26: Meetjs summit 2016 - Controll the chaos

Communication with business• State requirements (Preserve things in writing) • Avoid technical conversation :) • Visualise things • Inform about possible delays • Require feedback or more autonomy • Set priorities (needs vs wants)

Page 27: Meetjs summit 2016 - Controll the chaos

„Without requirements or design, programming is the art of adding bugs to

an empty text file”

Louis Srygley

Page 28: Meetjs summit 2016 - Controll the chaos

Communication with business• State requirements (Preserve things in writing) • Avoid technical conversation :) • Visualise things • Inform about possible delays • Require feedback or more autonomy • Set priorities (needs vs wants)

Page 29: Meetjs summit 2016 - Controll the chaos

Communication with business• State requirements (Preserve things in writing) • Avoid technical conversation :) • Visualise things • Inform about possible delays • Require feedback or more autonomy • Set priorities (needs vs wants)

Page 30: Meetjs summit 2016 - Controll the chaos

Communication with business• State requirements (Preserve things in writing) • Avoid technical conversation :) • Visualise things • Inform about possible delays • Require feedback or more autonomy • Set priorities (needs vs wants)

Page 31: Meetjs summit 2016 - Controll the chaos

Communication with business• State requirements (Preserve things in writing) • Avoid technical conversation :) • Visualise things • Inform about possible delays • Set priorities (needs vs wants) • Set priorities (needs vs wants)

Page 32: Meetjs summit 2016 - Controll the chaos

Communication with business• State requirements (Preserve things in writing) • Avoid technical conversation :) • Visualise things • Inform about possible delays • Set priorities (needs vs wants) • Require feedback or more autonomy

Page 33: Meetjs summit 2016 - Controll the chaos

Communication with business• State requirements (Preserve things in writing) • Avoid technical conversation :) • Visualise things • Inform about possible delays • Set priorities (needs vs wants) • Require feedback or more autonomy • Inform about progress (Gantt, Kanban)

Page 34: Meetjs summit 2016 - Controll the chaos

Developers

https://www.youtube.com/watch?v=BKorP55Aqvg

Page 35: Meetjs summit 2016 - Controll the chaos

„You can’t have great software without a great team, and most software teams

behave like dysfunctional families”

Jim McCarthy

Page 36: Meetjs summit 2016 - Controll the chaos

Communication of developers• Set responsibilities • Establish conventions (Linters - JSLint) • Write documentation (Docs generators - JSDoc • Standups • Changelog

Page 37: Meetjs summit 2016 - Controll the chaos

Communication of developers• Set responsibilities • Establish conventions (Linters - JSLint) • Write documentation (Docs generators - JSDoc • Standups • Changelog

Page 38: Meetjs summit 2016 - Controll the chaos

Communication of developers• Set responsibilities • Establish conventions (Linters - JSLint) • Write documentation (Docs generators - JSDoc • Standups • Changelog

Page 39: Meetjs summit 2016 - Controll the chaos

Communication of developers• Set responsibilities • Establish conventions (Linters - JSLint) • Write documentation (Docs generators - JSDoc • Standups • Changelog

Page 40: Meetjs summit 2016 - Controll the chaos

Communication of developers• Set responsibilities • Establish conventions (Linters - JSLint) • Write documentation (Docs generators - JSDoc • Standups • Maintain Changelog

Page 41: Meetjs summit 2016 - Controll the chaos

Any thoughts?

Page 42: Meetjs summit 2016 - Controll the chaos

!anks!

Bartosz Grzegorczuk [email protected]

@BGrzegorczuk