part time agile

22
Part Time Agile Dima Malenko rollApp

Upload: dima-malenko

Post on 19-Nov-2014

2.308 views

Category:

Technology


2 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Part Time Agile

Part TimeAgile

Dima MalenkorollApp

Page 2: Part Time Agile

Any applicationOn any deviceAnywhere

Page 3: Part Time Agile

Our Story

The team of one

More of us

Into the future

Page 4: Part Time Agile

IN THE BEGINNINGThe team of one

Page 5: Part Time Agile

ProductMarket, Tech

Users, Social

OpsHosting

Linux, DNS, …

ClientFlash

JavaScript

ServerPython

X Window

WebPython

JS, CSS, SQL

Page 6: Part Time Agile

ProductMarket, Tech

Users, Social

OpsHosting

Linux, DNS, …

ClientFlash

JavaScript

ServerPython

X Window

WebPython

JS, CSS, SQLULTIMATE CROSS FUNCTIONAL TEAM

Page 7: Part Time Agile

Cross-functionality

Leve

l of a

bstr

actio

n

Variation in tools and methods

Code

Systems

Products

Markets

Wide cross-functionality

Deep cross-functionality

Page 8: Part Time Agile

6-12 months 15-30 minutes

Impact horizon

The Fallacy of “Deep” Cross-functionality

Page 9: Part Time Agile

AS IT GOESNow and then: a team of 5

Page 10: Part Time Agile

I switched to full-time

Part-time team- Web developer- Server developer- Client developer- Plugins developer

Contractors- UI/UX designer- PR/Marketing specialist

Page 11: Part Time Agile

“Get Together” Lunch

- Every week- Not a meeting!- Good for brainstorming

Page 12: Part Time Agile

Weekly 1:1s- Feedback- Discussions- A little bit of status

Check out Manager Tools podcasts on this topichttp://manager-tools.com/taxonomy/term/7

Page 13: Part Time Agile

F

Short Iterations Focus- 1 week- Bug fixes + Focus

Not more than onemajor feature per component/direction

Page 14: Part Time Agile

Cross-functional Features

Page 15: Part Time Agile

Major Development: Working TogetherRelied on “agility” too much

Different schedules:

Coding sessions Design Up Front

Page 16: Part Time Agile

Major Development: New Components- Deployability is a feature- 1st one you should deliver

Page 17: Part Time Agile

Syndrome of a Small Team

Small problem for a large team can be a large problem for a small team

Remember this sign - %

Page 18: Part Time Agile

Wiki Is Your Friend- “Interactions … over documentation” *

I remember that we already discussed this.

Yep, me too. What have we decided? **

1. Describe idea in Wiki2. Send e-mail “Hey! Here is what I’m up too. Let’s discuss”3. Discuss and correct4. ???5. PROFIT!

* A little bit frivolous quite from Agile Manifesto** Characters from Geek and Poke (http://geekandpoke.typepad.com)

Page 19: Part Time Agile

Issue Tracking vs. Status Assessment- Tracking is about ensuring a process is executed- Status is about seeing the whole picture

Check out http://trello.com

Page 20: Part Time Agile

GOING FORWARD

Page 21: Part Time Agile

What We Plan Next

Get back to weekly releases

Automate everything

A/B testing and “scientific” data to drive product development

Page 22: Part Time Agile

That’s it!- Questions?- Suggestions?- Ideas?

Get in touch!@[email protected]