recapitulando: de métodos ágeis até lean startup

recapitulando

de métodos ágeis até lean startups

pedro axelrud

about.me/pedroaxl

catarse.memeurio.org.br

@pedroaxl

festivaldeideias.org.br

pedro axelrud

about.me/pedroaxl

panop.it

spicing customer relationship with the social stu!

Mailee.meSocialee.me

@pedroaxl

agile manifesto

Individuals and interactions over processes and tools

Working Softwareover comprehensive documentation

Customer colaborations over contract negotiation

Responding to change over following a plan

all about peopleeveryone wishes to do a good job

summary

eXtreme Programming

reviewing values

do what is needed, but no more.

maximize the value created.

take small simple steps to our goal.

mitigate failures as they happen.

simplicity

Everyone is part of the team and we communicate face to face daily.

We will work together on everything from requirements to code.

communication

We will take every iteration commitment seriously by delivering working software.

We demonstrate our software early and often then listen carefully and make any changes needed.

feedback

Everyone gives and feels the respect they deserve as a valued team member.

Everyone contributes value even if it's simply enthusiasm.

Developers respect the expertise of the customers and vice versa

respect

We will tell the truth about progress and estimates.

We don't fear anything because no one ever works alone.

We will adapt to changes when ever they happen.

courage

practices

As a user closing the application,I want to be prompted to save anything that has changed since the last save so that I can preserve useful work and discard erroneous work.

user stories

planning poker

first the developer writes a failing automated test case that defines a desired improvement or new function,

then produces code to pass that test and

finally refactors the new code to acceptable standards.

test driven development

"disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior"

Advantages include improved code readability and reduced complexity to improve the maintainability of the source code.

refactoring

the four variables

evolutions

It extends TDD by writing test cases in a natural language that non-programmers can read.

behavior driven development

Feature: Division In order to avoid silly mistakes Cashiers must be able to calculate a fraction

Scenario: Regular numbers * I have entered 3 into the calculator * I have entered 2 into the calculator * I press divide * the result should be 1.5 on the screen

behavior driven development

lean ux

just the ux process

concept prototype validateinternally

testexternally

learn iterate

all about flattening the maintenance costassumption: committed people

summary

scrum

reviewing roles

who ensures the process is followed, removes impediments, and protects the Development Team from disruption

scrum master

who represents the stakeholders and the business

product owner

a cross-functional, self-organizing team who do the actual analysis, design, implementation, testing, etc

development team

sprint

backlog sprintuser storyuser storyuser story

1 point

3 points

5 points

user story 3 points

user storyuser storyuser story

1 point

1 points

3 points

user story 1 point

meetings

sprint planning

daily meeting

sprint retrospective

15m

3h

what have you done since yesterday?

what are you planning to do today?

any impediments/stumbling blocks?

what went well during the sprint?

what could be improved in the next sprint?

all about an empirical process to deliver quality software oftenassumption: committed people and flat maintenance cost

summary

lean startup

part 1: problem/solution fit

part 2: product/launch fit

part 3: product/market fit

are you ready to learn from customers?

do you have a problem worth solving?

have you built something customers want?

scale

all about validating business assumptions and maximizing the delivered value.assumption: committed people, flat maintenance cost and deliver quality software often

summary

what do you need? committed people flat maintenance cost quality software delivered often validate business assumptions maximize delivered value

result: scalable business model

conclusion

gist.github.com/pedroaxllearn more

obrigado!pedro@panop.it

kudos to @joaomilho