Reading List One question frequent asked about Agile methods is: Once the contract is signed a development period follows where everyone argues about what is actually in scope, what is out of scope, and what constitutes a change request to the contract. But eventually the work is done, and after some heated debate, the customer formally accepts the software and payment is made.
Good Agile, Bad Agile Scrums are the most dangerous phase in rugby, since a collapse or improper engage can lead to a front row player damaging or even breaking his neck.
It was easy to remember.
And it was weird when they switched it up on us, because it was as if the FDA had suddenly issued a press release announcing that there are, in fact, two kinds of rat poison: Good Rat Poison and Bad Rat Poison, and you should eat a lot of the Good kind, and none of the Bad kind, and definitely not mix them up or anything.
My bad-cholesterol view was that Agile Methodologies are for chumps. I have a pretty clear picture of it now. And if in the future you ever find me touring around as an Agile Consultant, charging audiences to hear my deep wisdom and insight about Agile Development, you have my writing agile contracts to cut my balls off.
Contract or outsourced development is one situation in which a team will need to augment conversations with documentation. This article will show one technique I’ve used for writing contracts to cover contracted agile development. The goal of this article is to share experiences and the model for organizing and operating distributed Agile teams that evolved from these efforts, but the main message is much simpler: Agile is the best way with distributed teams. Sep 27, · Most people take it for granted that you want to pick a date. Even my favorite book on software project management, "The Mythical Man-Month", assumes that you need schedule estimates.
This step is optional. Interestingly, this is also exactly how non-technical companies like, say, Chrysler handled software development. So some of the consultants began to think: When a company said "we want features A through Z", the consultants would get these big index cards and write "A" on the first one, "B" on the second one, etc.
Then when the customer wanted to add something, the consultant could point at the wall and say: Which one of these cards do you want to replace, BOY? So the consultants, now having lost their primary customer, were at a bar one day, and one of them named L.
You know where the real money is at? You start your own religion. Well, people pretty quickly demonstrated that XP was a load of crap.
Take Pair Programming, for instance. The rationale was something like: But the thing is, viruses are really hard to kill, especially the meme kind.
After everyone had gotten all worked up about this whole Agile thing and sure, everyone wants to be more productivethere was a lot of face to be lost by admitting failure. So some other kinds of Agile "Methodologies" sprang up, and they all claimed that even though all the other ones were busted, their method worked!
I mean, go look at some of their sites. Well, they make money hand over fist, because of P. Some people are just dying to be parted with their cash. The rest of us have all known that Agile Methodologies are stupid, by application of any of the following well-known laws of marketing: Why not take it inside the companies and sell it there, to the developers?
And that, friends, was exactly, precisely the point at which they went from "harmless buffoons" to "potentially dangerous", because before they were just bilking fat companies too stupid to develop their own software, but now the manager down the hall from me might get infected.
Observe that it must be a slippery problem, or it all would have been debunked fair and square by now. About the best you can do is gather statistical data across a lot of teams doing a lot of projects, and try to identify similarities, and perform some regressions, and hope you find some meaningful correlations.
But where does the data come from? People want fad diets to work, oh boy you bet they do, even I want them to work. But writing about Bad Agile alone is almost guaranteed to be ineffective.
Quitting a viral meme is harder than quitting smoking. One of the many problems with Bad Agile is that they condescendingly lump all non-Agile development practices together into two buckets: Waterfall is known to be bad; I hope we can just take that as an axiom today.
But what about so-called Cowboy programming, which the Agileers define as "each member of the team does what he or she thinks is best"? Is it true that this is the only other development process?6 Agile Contracts Primer necessarily trust the expectations of the anticipated outcome and is mandated to deal with most anticipated outcomes—good and bad.
The third value of the Agile Manifesto is customer collaboration over contract benjaminpohle.com-rally, when first reading this, a contract lawyer will take note, react, and perhaps think, “That’s nice.
A lawyer writing a contract for an agile project (most commonly, done with Scrum) needs to grasp the key ideas before she can articulate an agile contract. We suggest that legal professionals study.
Contract or outsourced development is one situation in which a team will need to augment conversations with documentation. This article will show one technique I’ve used for writing contracts to cover contracted agile development.
Product Designer & Researcher, ThoughtWorks. Diana is a designer, researcher and strategist who produces digital products using an Agile . Quick post to point out two other blogs I recommend you read.
User story mapping is an essential practice for every agile team. Have a read of Understand What Your Customers Want with Agile User Story Maps to get some background and then follow up with Anatomy of an Agile User Story Map for the details.
We are uncovering better ways of developing software by doing it and helping others do it. These are our values and principles.