Development Process (using Trello) by Daniel Lopes

28
Our development process using Trello Lunch ‘N’ Learn Sessions by

Transcript of Development Process (using Trello) by Daniel Lopes

Page 1: Development Process (using Trello) by Daniel Lopes

Our developmentprocess using Trello

Lunch ‘N’ Learn Sessions

by

Page 2: Development Process (using Trello) by Daniel Lopes

Agile

It promotes adaptive planning, evolutionary development, early delivery, continuousimprovement, and encourages rapid and flexible response to change.

Page 3: Development Process (using Trello) by Daniel Lopes

Agile

Being Agile “It’s all about empowering thedevelopers/designers to do as much as possible,as quickly as possible.”

It’s about freeing the team from depending onother people – as Product Managers/Clients – toget things done.

It’s about managing code, not people. Agileincreases speed and responsiveness and reducesstress.

Page 4: Development Process (using Trello) by Daniel Lopes

DISCLAIMER

And that’s why our process itselfit’s also – up to some point - flexible.

Page 5: Development Process (using Trello) by Daniel Lopes

SAY HELLO TO

Page 6: Development Process (using Trello) by Daniel Lopes

EPICSTORY

TASK

Page 7: Development Process (using Trello) by Daniel Lopes

A TRELLO CARDEPIC

STORYTASK

Page 8: Development Process (using Trello) by Daniel Lopes
Page 9: Development Process (using Trello) by Daniel Lopes

A CHECKLISTIt should be theacceptance criteria

EPICSTORY

TASK

Page 10: Development Process (using Trello) by Daniel Lopes
Page 11: Development Process (using Trello) by Daniel Lopes

A CARD / DOCUMENTfor more complex projectsEPIC

STORYTASK

Page 12: Development Process (using Trello) by Daniel Lopes
Page 13: Development Process (using Trello) by Daniel Lopes

Cards move fromleft to right

Page 14: Development Process (using Trello) by Daniel Lopes

Each list represents a differentstage of the project

Page 15: Development Process (using Trello) by Daniel Lopes

More Notes

• Cards in list are priotized, being the top oneswith more priority;

• Etiquette: never have your face in more thantwo cards at a time;

• When testing a feature card, post a newchecklist ticket for each bug (Task), and send itback to Next Up list. If not, create a new cardfor the bug.

Page 16: Development Process (using Trello) by Daniel Lopes

More Notes

• No central chokepoint for deploying tostaging: everyone can do it;

• Work is done in a feature branch. Not in adevelopment branch;

• Hotfixes go directly to master.

Page 17: Development Process (using Trello) by Daniel Lopes

Team communication

• Kick of call at the beginning, to discuss goalsand big picture (it’s not a planning session!);

• Daily stand up on the first 1/2 weeks of theproject are ok;

• Ad-hoc meetings, which should include onlythe people that need to be on the call;

• Overdo async! A.K.A ,, &

Page 18: Development Process (using Trello) by Daniel Lopes

Client communication

• The team communicates directly with theclient;

• Have weekly reports (meetings) with theclient, with a fixed format agenda. Have fewpeople in the meeting;

• Always document requests and agreementson a card.

Page 19: Development Process (using Trello) by Daniel Lopes

Lead developer – Daily checklist

• Resolve needs and roadblocks;

• Manage workload:• Do not let team members work on many cards

concurrently;

• If someone has been working in for several dayson one card without commiting code, ask him orher to split the card into smaller tasks.

Page 20: Development Process (using Trello) by Daniel Lopes

Lead developer – Weekly checklist

Backlog grooming – Instead of doing na iterationplan with the complete team, take a smallergroup of people and do “backlog grooming”.

This means making sure that your upcomingtasks have good descriptions, use cases, anddesign materials.

Page 21: Development Process (using Trello) by Daniel Lopes

What has beenchanging

Page 22: Development Process (using Trello) by Daniel Lopes

Less Scrum, More Kanban

• No more weekly iteration plans – Pull tasksfrom the prioritized backlog whenever you areready to work on them;

• Backlog prioritisation is done asynchronously.

Page 23: Development Process (using Trello) by Daniel Lopes

Continuous Deployment

Be constantly releasing new code (preferablydaily).

Even non-finished features!

Page 24: Development Process (using Trello) by Daniel Lopes

Continuous DeploymentThis results in:

• Fewer bugs, and easier to find, because youhave less new code to look through;

• The ability to release features without beingblocked by testers or product management;

• The final “unveil” release is much less stressfuland more reliable, because new features havebeen integrated, tested, and deployed (forsome audiences) for some time before theunveil.

Page 25: Development Process (using Trello) by Daniel Lopes

Automate and measure more

• We must automate-all-the-things that can beautomated: testing, deploying, merging, etc.

• Developers/designers should be empoweredwith all the tools for monitoring as: servererrors, financial results, number of releasedfeatures, number of bugs, etc. the unveil.

Page 26: Development Process (using Trello) by Daniel Lopes

Want more tips or to knowmore about us and our work?

SIGN UP FOR OUR NEWSLETTER!

But first, here’s a little headsup…

CLICK!

Page 27: Development Process (using Trello) by Daniel Lopes

Whitesmith

We are a web and mobile product development studio founded in 2013 and based in Coimbra (Portugal) and London. From Service Oriented Architecture and Internet of Things to Web & Mobile apps, we converge into solving real problems with great user experience. We are more than simple designers & developers - we are an empowered team of problem solvers.

CLICK!

Page 28: Development Process (using Trello) by Daniel Lopes

Lunch-n-Learn

Each Friday, a member of our team shares a topic of his interest, whether it’s something related with technology, business or evenlife-hacking. This is our way of learning something new eachweek and sharing a little bit of ourselves.Now we are sharing some of our knowledge with you!

This Lunch ‘N’ Learn session was hosted by

Daniel Lopes

Role Business and CodeSecret weapons Business development, project management, blazing, fast, resilienceSide projects Radio Broadcaster at RUCInspirational quote "Every man I meet is my superior in some way. In that, I learn of him." -Emerson

CLICK!