I've only worked at one shop that did Agile and I'm pretty sure they "did it right". We had a great SCRUM master that would not allow cross-talk and would do multiple scrums so that there was never more then 8-10 people on a scrum at a time. Easily no more then 5 minutes.
The SCRUM master was then the one that had to deal with the scrum of scrums and all that crap so as a developer all we were ever asked to do was make estimates based on stories. The POs were really scolded if the devs ever came back with a "I don't understand this" so they made sure their stories were complete. They also paid big money for Jim Highsmith to come in twice a year and evaluate their process... I'm sure that helped keep things in line. -J.J. On Mon, Aug 4, 2014 at 10:19 PM, LRS Scout <[email protected]> wrote: > > I thinking anything trying to be pure to dogma or intent fails > automatically. > > Chaos rules supreme. > On Aug 4, 2014 9:33 PM, "Scott Stroz" <[email protected]> wrote: > >> >> If you have a PM, they should be setting priority, not the developer(s). >> >> When done the right way, agile can be a great way to work. Problem is, very >> few do it the 'right' way. Often times when it is 'custom' agile that is >> when it fails. >> >> As I noted earlier the one huge drawback I have experienced is that people >> tend to be lazy with requirements gathering because 'we are doing agile. We >> can roll with any changes' . >> On Aug 4, 2014 9:16 PM, "Eric Roberts" <[email protected]> >> wrote: >> >> > >> > I just hate agile...period. I cringe whenever a recruiter brings that up >> > in >> > the listing of job requirements. The thing I don't get is having the >> > developer rank the importance...well unless I am getting paid extra to >> also >> > be the project manager...I don't care...just tell me what we need to do >> and >> > what order you want it done. Don't waste my time with all this crap. >> If I >> > wanted to do all of this I would be a manager....something I don't want >> to >> > have any part of. Most of this shit is just an utter waste of my time >> as a >> > developer. >> > >> > Our scrum meetings are what we did yesterday and what we are doing >> > today...we have a pretty big team, so it does take a while. My main >> > complaint is with Sprint planning and lack of any substantial >> > documentation...why am I involved in that. Managers...do your job and >> > leave >> > me out of it. Most of what I am doing in my current position are bug >> > fixes, so that seems to work ok since there is no real designing of >> things >> > going on...just fix the defects and work on enhancements within the >> current >> > framework. >> > >> > I did a gig at Motorola at the beginning of the year. I was building a >> > new >> > tool from scratch. I asked them how they wanted it designed...th4ey told >> > me >> > to just build it and do it however I would build the tool...what I felt >> was >> > best. They wanted to give the developers as much leeway as possible. >> So I >> > built the tool...after waiting almost 3 months to get my logins...a >> > completely different rant...which put me behind already... Also, other >> > parts of the system that needed to get built that my part depended on >> were >> > not getting built in time, so I ended up having to build something that I >> > could use to push and pull data, which turned out to be different from >> how >> > the other developer that was actually building that part envisioned it. >> I >> > turned it in and they said, well no...we want this done this way and that >> > done this way. I am like, well WTH didn't you tell me that to begin >> with. >> > Had I had that information, I would have structured things a lot >> > differently. This was a total train wreck caused by their implementation >> > of >> > agile and not having a coherent plan on how they wanted the application >> > designed and structured. Just leaving it to the developers and then >> > bitching when the developers didn't guess the right way is not a way to >> run >> > things. So then we end up being late on the deliverables. I ended up >> > getting let go because I just had no good way to tie in the project with >> > all >> > the new changes with the way I had originally designed it. What an utter >> > cluster fuck. My other experiences with agile have not been that much >> > different. I have never worked in a shop where agile works as it says it >> > is >> > supposed to work on paper. I think agile processing should be banned >> > completely and anyone that even brings it up should be tarred and >> feathered >> > and run off of the planet. >> > >> > Agile purity...LOL...I think that is a mythological state... >> > >> > -----Original Message----- >> > From: Scott Stroz [mailto:[email protected]] >> > Sent: Monday, August 04, 2014 7:14 PM >> > To: cf-community >> > Subject: Re: Sometimes... >> > >> > >> > Hour long 'scrum', regardless of the reason, is doing it wrong. >> > >> > PM should be giving client a briefing based on the daily scrum or if >> client >> > insists on being on call, they should play by the 'rules'. >> > >> > Sounds like client doesn't understand how the daily scrum is supposed to >> > work and that no one is willing/able to explain it. >> > On Aug 4, 2014 1:10 PM, "GMoney" <[email protected]> wrote: >> > >> > > >> > > He might be under similar constraints that my project is given. The >> > > client deemed our project "essential" and "critical", and they want >> > > observation and updates daily.....so we are forced to have our clients >> > > on the phone with us for our daily standups. You can imagine how this >> > > complicates things. >> > > >> > > Agile scrums can be corrupted just like any other process...we've had >> > > hour long stand-ups because the client steers them that way. Eric >> > > probably has some similar externality that is butchering his Agile >> > purity. >> > > >> > > >> > > On Mon, Aug 4, 2014 at 12:05 PM, Scott Stroz <[email protected]> >> wrote: >> > > >> > > > >> > > > Hour scrum? >> > > > >> > > > Yea...you are doing it so very wrong. >> > > > >> > > > If our daily scrum is more than 5 minutes, I get antsy. >> > > > >> > > > >> > > > On Mon, Aug 4, 2014 at 12:10 PM, Eric Roberts < >> > > > [email protected]> wrote: >> > > > >> > > > > >> > > > > We have an hour meeting every day for our scrum, plus a >> > > > > retrospective >> > > > and a >> > > > > scrum panning session during a new sprint. Those meetings can go >> > > > > up >> > > to 2 >> > > > > hrs...I think it is just an excuse for management not to do it's >> > job... >> > > > > >> > > > > -----Original Message----- >> > > > > From: Scott Stroz [mailto:[email protected]] >> > > > > Sent: Monday, August 04, 2014 10:41 AM >> > > > > To: cf-community >> > > > > Subject: Re: Sometimes... >> > > > > >> > > > > >> > > > > Again....if you spend that much time in meetings, you are not >> > > > > doing >> > > > 'agile' >> > > > > correctly. >> > > > > >> > > > > >> > > > > On Mon, Aug 4, 2014 at 8:32 AM, GMoney <[email protected]> wrote: >> > > > > >> > > > > > >> > > > > > AMEN!!! >> > > > > > >> > > > > > Our shop is going full blown Agile, and the meetings are driving >> > > > > > me >> > > > nuts. >> > > > > > >> > > > > > >> > > > > > On Fri, Aug 1, 2014 at 6:07 PM, Casey Dougall - Uber Website >> > > Solutions >> > > > > > < [email protected]> wrote: >> > > > > > >> > > > > > > >> > > > > > > LoL, that is priceless. >> > > > > > > >> > > > > > > I'm so glad our team isn't agile. Waste of frigging time that >> > is... >> > > > > > > >> > > > > > > 2 days a sprint wasted to meetings. >> > > > > > > >> > > > > > > Working with the agile process I see LOL >> > > > > > > >> > > > > > > -----Original Message----- >> > > > > > > From: C. Hatton Humphrey [mailto:[email protected]] >> > > > > > > Sent: Friday, August 01, 2014 1:14 PM >> > > > > > > To: cf-community >> > > > > > > Subject: Sometimes... >> > > > > > > >> > > > > > > >> > > > > > > Sorry, have to vent. Work's being a bit more "bang head >> > > > > > > here"-ish than usual. Guess the next skills I need to develop >> > > > > > > to advance my career are telepathy, time travel and insomnia. >> > > > > > > >> > > > > > > Happy Friday, folks! >> > > > > > > >> > > > > > > Until Later! >> > > > > > > C. Hatton Humphrey >> > > > > > > http://www.eastcoastconservative.com >> > > > > > > >> > > > > > > Every cloud does have a silver lining. Sometimes you just >> > > > > > > have to do >> > > > > > some >> > > > > > > smelting to find it. >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > >> > > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > >> > > > >> > > >> > > >> > >> > >> > >> > >> >> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-community/message.cfm/messageid:371920 Subscription: http://www.houseoffusion.com/groups/cf-community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-community/unsubscribe.cfm
