Stakeholders Actively Participate When you are requirements modeling the critical practice is Active Stakeholder Participation. There are two issues that need to be addressed to enable this practice - availability of project stakeholders to provide requirements and their and your willingness to actively model together. My experience is that when a project team doesn't have adequate access to project stakeholders that this is by choice. You have funding for your project, don't you?
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.
Nowadays, though, they differentiate between "good" cholesterol and "bad" cholesterol, as if we're supposed to be able to distinguish them somehow. 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.
Up until maybe a year ago, I had a pretty one-dimensional view of so-called "Agile" programming, namely that it's an idiotic fad-diet of a marketing scam making the rounds as yet another technological virus implanting itself in naive programmers who've never read "No Silver Bullet", the kinds of programmers who buy extended warranties and self-help books and believe their bosses genuinely care about them as people, the kinds of programmers who attend conferences to make friends and who don't know how to avoid eye contact with leaflet-waving fanatics in airports and who believe writing shit on index cards will suddenly make software development easier.
That's the word I'm looking for. My bad-cholesterol view was that Agile Methodologies are for chumps. It turns out there's a good kind of Agile, although it's taken me a long time to be able to see it clearly amidst all the hype and kowtowing and moaning feverishly about scrums and whatnot.
I have a pretty clear picture of it now. You'll only find seminars about the Bad kind of Agile. 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 permission to cut my balls off.
If I say I was just kidding, say I told you I'd say that. If I then say I'm Tyler Durden and I order you not to cut my balls off, say I definitely said I was going to say that, and then you cut 'em right off.
I'll just go right ahead and tell you about the Good Kind, free of charge. It's kinda hard to talk about Good Agile and Bad Agile in isolation, so I might talk about them together.
But I'll be sure to label the Good kind with a happy rat, and the Bad kind with a sad dead rat, so you'll always know the difference. This step is optional. Thank goodness that doesn't happen at your company, eh now? Interestingly, this is also exactly how non-technical companies like, say, Chrysler handled software development.
Except they didn't hire the engineers. And then it'd all fall apart and the contractors wouldn't get paid, and everyone was really miffed. 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. It's one of the more spectacular failures of XP.
None of the Agileytes likes to talk about it much, but let's face it: 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. Tell me that's not an infomercial. It's embarrassing even to look at the thing. Well, they make money hand over fist, because of P. Barnum's Law, just like Scientology does. Can't really fault 'em. 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:Draft: Manifesto for Agile Scientific Research Some scientists even questioned whether scientific discoveries and the published paper aren't the same thing!
Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks.
Oct 18, · What are some topics for a research paper on Agile Project Management? Update Cancel. ad by Aha! Is there a project manager in Agile Scrum?
What is Agile project-related documentation? How do I write a research paper for software project management?
Any general research suggestions for software project management? Large Scale Scrum (LeSS) Large-Scale Scrum is adapted from the book Practices for Scaling Lean and Agile Development, by Craig Larman and Bas Vodde.
It is defined as regular Scrum plus “a set of additional rules and the set of tips that we have seen work in large multi-team, multisite, and offshore agile development initiatives” (LeSS Company, a).
A backlog is a list of features or technical tasks which the team maintains and which, at a given moment, are known to be necessary and sufficient to complete a project or a release. 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.
A daily stand-up, or daily scrum, is an integral component of a sprint to keep agile teams on task. Here are things teams shouldn't be doing during.