Part Time Agile

Preview:

DESCRIPTION

 

Citation preview

Part TimeAgile

Dima MalenkorollApp

Any applicationOn any deviceAnywhere

Our Story

The team of one

More of us

Into the future

IN THE BEGINNINGThe team of one

ProductMarket, Tech

Users, Social

OpsHosting

Linux, DNS, …

ClientFlash

JavaScript

ServerPython

X Window

WebPython

JS, CSS, SQL

ProductMarket, Tech

Users, Social

OpsHosting

Linux, DNS, …

ClientFlash

JavaScript

ServerPython

X Window

WebPython

JS, CSS, SQLULTIMATE CROSS FUNCTIONAL TEAM

Cross-functionality

Leve

l of a

bstr

actio

n

Variation in tools and methods

Code

Systems

Products

Markets

Wide cross-functionality

Deep cross-functionality

6-12 months 15-30 minutes

Impact horizon

The Fallacy of “Deep” Cross-functionality

AS IT GOESNow and then: a team of 5

I switched to full-time

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

Contractors- UI/UX designer- PR/Marketing specialist

“Get Together” Lunch

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

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

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

F

Short Iterations Focus- 1 week- Bug fixes + Focus

Not more than onemajor feature per component/direction

Cross-functional Features

Major Development: Working TogetherRelied on “agility” too much

Different schedules:

Coding sessions Design Up Front

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

Syndrome of a Small Team

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

Remember this sign - %

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)

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

GOING FORWARD

What We Plan Next

Get back to weekly releases

Automate everything

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

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

Get in touch!@dmalenkodmalenko@rollapp.com

Recommended