PHP Team Organisation

PHP TEAM ORGANIZATION

samedi 30 octobre 2010

AGENDA

Acknowledge the human factor

Organise your team

Raise the competences of everyone


WHO IS SPEAKING?

Damien Seguy

Raise elephpants

Expert services manager at Alter Way group

[email protected]


mailto:[email protected]


YESWE TAKE

QUESTIONS


INDUSTRIALISATION


TEAM FUNCTIONS


TEAM FUNCTIONS

Project style

Analyst

Developper

Tester

Doc writer


TEAM FUNCTIONS

Project style

Analyst

Developper

Tester

Doc writer

PHP style

Database architect

Core PHP

HTML integrator

Test writer


TEAM FUNCTIONS

Project style

Analyst

Developper

Tester

Doc writer

PHP style

Database architect

Core PHP

HTML integrator

Test writer

Agile style

Product owner

Technical expert

Manager

Team members


HUMAN FACTOR

Juniors are silent

Seniors are oral

You don’t have time to check all the code all the time

You need to work as a team


What we do well

What we want to do

What will push forward the project


What we do well

What we want to do

What will push forward the projectCame to us

Proje

ct su

cces

s

Our desires


What we do well

What we want to do



What we do well

What we want to do


MoltBé


What we do well

What we want to do


Do better

MoltBé


What we do well

What we want to do


Evangelize

Do better

MoltBé


What we do well

What we want to do


Evangelize

Say no Do better

MoltBé


AGENDA

Learn to say no

Learn to do it better

Evangelize


DO IT BETTERWeekly meeting

GurusCompetition


TECHNICAL MEETING

Weekly meeting

Gather all your team for technical time

1 hour, dedicated to technics, tools, methods

Outside project pressure


WEEKLY MEETING

1 hour only

Everyone must attend, tasks will wait

Assign a note taker

Works as training

Make sure everyone talk during the meeting


WEEKLY MEETING

Subjects

Discussion of future stuff : new version, techno...

Specific training on tools, methods

Read indicators (audits, PI, etc..)

Review reference documents

One question each (helps prepare for the meeting)


CHOOSE YOUR GURU

Terms appeal to dev, makes man. laugh

Find him inside

Hire one from outside

No full time needed


NAME DOMAIN GURUS

Create domain experts

specific domain

Unit test, IHM, database

Willing team member

Name it after he has taken the responsability.


HEALTHY COMPETITION

Number of unit tests

Lines of code

Number of method

Number of commits

Code_Sniffer violations

Mystery objective


HEALTHY COMPETITION

Have a prize

Not money : bad idea

Free time, the big screen, the PHP mascot, doing a study on the new tech...

Keep this friendly


LEARN TO SAY NO5 minuts meeting

Short cyclesReferences


5 MINUTS DAILY

Early in the morning, regular schedule

Done standing up : no dozing or typing

Everyone talk :

Today’s goal

Yesterday’s progress

Main blocking problem


5 MINUTS DAILY

Helps junior organizing their project

First step for project planning

Give a start to the day with the team

Sharing with the team members

No need for preparing : may reduce email syndrom


SHORT CYCLES

Make the full cycle from dev to version

Perfection come from practise

Include the whole cycle from spec to end user. No more ‘hoster is late syndrom’

Fight the tunnel effect


REFERENCES

Document gathering your conventions

Better shared as Wiki,

Coding, security reference, commit policy, conception document


REFERENCES

Document objective

Executive summary (3 paragraphs)

List of the conventions you set up


REFERENCES

Name

Description

What happens if this is ignored

Example, anti-example

Way of checking this convention : manual, automatic tool, search + refine...


PHP MANTRA

Don’t forget to produce your PHP mantra from them

Short version of your conventions

4-7 points to always always remember


EVANGELIZEChristianize

Tag your codeCross audit


CHRISTIANIZE

Give a cool name to your project :

Project Jaguar, the Alpha Team, Army of Ants

Debian Lenny, Microsoft Longhorn, OSX Lion

http://online-generator.com/name-generator/project-name-generator.php

Most of the time, someone else will choose it : fight for it!






CHRISTIANIZE

Get a mascot

Plush toy, poster, T-shirt, etc.

Helps member identifies with the project


TAG YOUR CODE

Documentation on PHP doc

Tags comments and extract them

Review them easily


<?php // @todo must handle time zone $heure = date("Hhi");

// @security this date is wrong

// @attention : this is not yet internationalized print("<font size="2" face="Arial"> $heure .</font>");

// @emptyelse

// @review #damien please, I'm not sure of this

// @security @performance @PHP5 @audit we don't do this here ?>


TAG CODE

Just like we tag URL, images, etc.

More specific that just a comment

Spot untagged comments

Leave notes to yourself, for later



CROSS AUDITS

Set up the reference

Team up everyone two by two

Review every commit by the other dev

Spend afternoon on reviewing code

Why not try pair-coding?

Shares knowledge, serves as training


SUMMARY

Learn to say no

Weekly meeting, gurus, competition

Learn to do it better

5 minuts meeting, short cycle, references

Evangelize

Christianize, cross audit, tag your code



D A M I E N . S E G U Y @ A LT E RWAY. F R!http://www.slideshare.net/dseguy/




http://www.slideshare.net/dseguy/

http://www.slideshare.net/dseguy/

THE END


DIFFERENT CYCLES

Dev cycles is not the same as others departments

30 % of production time is max

50 % of time in coding is max

Book time ahead, report everything until you’re done


20%

10%

10%

10%

50%

Coding Test Doc Review Production


BUDGET TIME

Always double your estimation

10% tests, 10% haggling, 20% unforseen, 10% new tech

50% coding (your estimatio)


I like my tools to be with short ROI

Have the regular task, and the emergency one. An emergency tool used all the time becomes a regular task.


3 TEAM MEMBER

Senior

Junior

Middle


VCS

Live with it

Center of your life

All automated tools will work on it

Gather SQL, deployment, code, data, etc.


Documents

PHP Team Organisation