Northeast PHP 2013

Metodologías ágiles para el desarrollo de aplicaciones

Michael Stowe  · 

Presentación

Vídeo

Transcripción

Extracto de la transcripción automática del vídeo realizada por YouTube.

HP 537 certified and I was over 10 years of PHP hacking experience in those 10 years he has had the privilege of building numerous websites and applications including applications for the medical field law enforcement window bleeding audio and lighting killers

large and small nonprofits and numerous industrial companies he's also spoken at numerous conference conferences publish multiple articles on PHP and security is not active member of a loss desire cousin and helps organize MN bhp Twin Cities software engineers

and the Midwest PHP conference like how it works is developer advocate at constant contact or a strives to help developers grow and connect every day and most importantly this like second year at HP site be here as you mentioned from the Midwest I'm from

Minnesota I will say ya sure you betcha by 50 times please don't make fun of me and secondly the way here has a Boston accent please see me afterwards you still waiting for it if i can get this guy to work here I'm not spend a lot of time on this clip

with this presentation the purpose of this is Lily over what is agile methodology movement in the workplace I'm not a project manager i'm a developer and so you're gonna hear the growing pains from a developer who has worked a company that was

very good at advil or company that was very good at waterfall there's no such thing and we're getting company to decide to go from waterfowl to agile to extreme agile which is also not good the only thing with really really quick is I am a developer

depakote constant contact I promise I'm not going to be advertising but the cool thing about constant contact is I told my boss I want to this presentation it was like okay you build a couple Ike two months like yes because you want to this presentation

on agile methodology yes what does that have to with casting couch nothing is are you going to talk about any guy no okay have fun so they've been really supportive really encouraging so at the end of my have a tweet for constant contact please think that

one let me appreciate this unless I just bored y'all your mind anybody was awake i'm still tweet so in the beginning why a job imagine you're going to take a trip and you want to go so you go to a store you buy a compass you buy your map you got

everything you're ready to go the only catch is once you start you can't stop so i hope you got the right map if you're like me you bought a map for Burlington Massachusetts when you're trying to go to burlington vermont horrible story Bradley

knows about this and hopefully you have the right supplies because if you don't you're kind of screwed so this is pretty much how we're developing products are coming we're developing products it was we're got build this product we have

three months to do it and hopefully this works and hopefully we have the right team members and hopefully we don't have any problems or 80 bucks point lawyer of programmers all right throw steven lee i'm just kidding how many of you have never made

a bug in your programming I know barely has he's like yes got it yeah there's always something there's always a twist there's always a track and the problem is usually we find these twist and turn it's too late to go back so our phone methodology

as we start off with hey we're going to build requirements again we're takin feels very good at waterfall that meant i got 200 page binder that said this is what we're building and it was detailed by a guy there's screenshots there's text

this is what this line should say and hopefully I doesn't change design it we're going to coat it we're going to test it and hopefully hopefully hopefully it works otherwise our timelines in jeopardy and then we're going to employ and maintain

it pipe it will do a freelance work or work for clients how your clients have said you know I want this and every project you'd open it like yes that's exactly what I wanted you guys to be was like no there's always changes and that's probably

barf all is that there's no accommodations like these changes there's no flexibility or as hell if none will kick said it hopefully i pronounced that way cuz i didnt no plan survives contact with the enemy it's always going to change so was agile

a jello simply means let's be flexible let's take it as it goes agile encourages a couple different days the first thing it encourages is individuals and interactions over processes and tools with waterfall we're saying okay this is our process

these are the tools were using this is how it's gonna be done Angela says no let's look at the people we have let's look at how they interact let's use the strengths of each of our team members to build the best product a great example this

is let's say failure on the same team they can walk with okay let's see we got these two guys we got Mike and probably can rarely you do all the PHP work you do all and Cody Mike you just stay away it's in a corner that would be a good reaction

because that way they know they're not gonna have any bugs from me I tried the other ideas working software over comprehensive documentation you give all the documentation in the world but what good does it do you if your software doesn't work the

project I had at the one company 200-page binder we got done six-month project it took it to market nobody wanted it it wasn't what they were looking for wasn't what they need it and by this time way too late customer collaboration over contract negotiation

when people ever had that one client each lost rifle and then you look and see if the police are watching we're gonna look at it st. okay instead of saying okay this is the contract this is what you asked for this is what you get or cuz it will won't

you take a look at it as we go so after brilliant they get to see what we're building they can see does it meet the requirements and if they change your mind hey we can take care that right away and then responding to change we're gonna be flexible

if they change the mind of my own things or be able to address that now to do mind that with the agile manifesto we're not getting rid of the things on the right we're not saying hey we don't get a plan we're not saying hey we don't use

processor tools / just saying we're going to put more emphasis on things on the left and really focus on those so what is an tell development this is my chart to scare people what we're going to start with is strategy and then we're going to start

with that strategy were to start making releases this is input iterations and they're asian goes to daily and continuous integration what this means is rather than building a project and then shipping it out we can build a project that continuously make

changes to it continuously upgrade it to say fix bugs so it's a workout living work versus a done deal network of maintaining and way an tell does this its first we're going to get a vision of project I want to build the shopping cart now with waterfall

we're saying okay I'll build a shopping cart so let's plan the customer login is how this is going to work and now we're going to have wishlist let's find all the details for that agile says on bill shopping cart and in that shopping cart

you know I kind of want a login customer portal I want to wish list but that's all the liquor is okay customer portal wish list that's as far and dentists we have to go at this point we're saying we want these features we have to decide how to

do the features we don't even have to figure out how long these features are going to take now the best way to think of this is think of have deck of cards so we got 52 cards here we're going to say what cards are the priorities what's important

we could say well hey we got the joke around why the Joker's on there just simply a good card king queen those review our big and foreign cars maybe it's the wish but it's going to be a way to check out I don't know that's kind of part

with a ecommerce system and sort of say those are things we need to get done first those are things we're going to focus on and then we can put the other cards in future iterations and say hey these are our wish list items these are things we want to do

but they're not as high of a priority so if you look at iteration backlog basically what you have is you have your top items again they're just very simple stories usually once you log in and see past orders if you wants to check out and these are

we all are other stories were saying hey you know we want to have the ability to same time to wish list we want to be able to compare prices once we have this prioritized we can then say where the tasks for these items this is where we're now making the

requirements we're saying okay so for them to login we got to have a login form we have to have a my account page so you can put down the individual tasks and we can actually break you down even further and say Bradley I want you to program this in PHP

movie UX personal okay the u.s. person is not here they're going to take care of you know the front end design for NOAA scientists individuals and saying this is what we need to accomplish and how long we think is going to take to accomplish we're

[ ... ]

Nota: se han omitido las otras 4.758 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.