Skip to main content

There's no place to hide in XP!

I have not met a single person who doesn't acknowledge the inherent values in XP when we talk about the values and not "this thing called XP". It is obvious to *anyone* who has enough years of experience behind them.

* The challenge then they often face in accepting XP/Agile is their own conflict-of-interest. *

You see, XP and Agile are brutal if you are lazy or if you are (or have become) mediocre. There's no place to hide in XP- everything is exposed. You can't create the anecdotal "job security hacks" so that you can't be replaced- because there are others in your team who know your code and can replace you if you're not pulling your weight. Or if you're a contractor, you now risk being caught for overbilling if you don't have "velocity" commensurate with the hours you're billing.

I speak, of course, from my experience as a programmer.

But more currently, I speak from my experience as the founder of a startup- as the employer, the product manager, the project manager, the requirements analyst and ... the customer. The engineers who "get it" are those who are passionate about "doing the right thing", are hard-working, and definitely above average, if not smart. The smart engineers who failed despite our best efforts were typically either washed out senior engineers (unwilling/unable to learn anymore) or had the fatal combination of inexperience & intransigence.

Succeeding in XP is not easy. It requires intensity and focus.
And merely "working hard" is no substitute for productivity.

There's no place to hide in XP.

"Well, it may be all right in practice, but it will never work in theory"
- Warren Buffett, on the attitude of his alma-mater Columbia University towards his method of investing.

Comments

Popular posts from this blog

Splitting User Stories vs. Rally's "split" feature (that has nothing to do with it!)

Agile tool Rally has a "split" feature it recommends to handle "unfinished work" in a Scrum Sprint: Manage Unfinished Work - Split user stories ( new link ) Below are my observations on the "Split" feature in Rally (followed by a few excellent articles on Splitting User Stories):   This "split" feature in Rally has numerous problems: 1. Nothing to do with Splitting User Stories It has nothing to do with "Splitting a User Story" which is an advanced but fairly well-understood field in Agile, and a tool for Product Managers to use in one of the two scenarios: The Product Manager does it before an Iteration commences (i.e. during backlog creation or release planning) to create User Stories by business value that are right-sized, i.e. they can be comfortably implemented inside an iteration; The Product Manager does it in Iteration Planning or in the middle of an Iteration to reduce scope by removing/simplifying accept

Entrepreneur Committee - Advisory Board of SVASE

For whatever it is worth, I would like to announce to my millions of would-be readers that I have been invited to join the Entrepreneur Committee on the Board of Advisors to the Silicon Valley Association of Startup Entrepreneurs . And I have accepted. If you're a hi-tech entrepreneur, I would love to hear your suggestions on what I can do in my "official" capacity to make SVASE a better organization for startups.

Test Trimming: A Fable about Testing

While browsing the web randomly, I found this very cool article on the value of testing. Says the author, Gerald M. Weinberg: "Throughout my career, I've watched in dismay as one software manager after another falls into the trap of achieving delivery schedules by trimming tests. Some managers shortcut test work by skipping reviewing and unit testing in the middle of their project. Others pressure the testers to "test faster" at the end. And, most frequently, they just drop planned tests altogether, hoping they "get lucky." I've written several essays about the dangers of test trimming, but nobody seems to understand, so I asked myself, "What am I doing wrong?" Perhaps I wasn't practicing what I was preaching. Perhaps I was trimming tests myself. Perhaps my writing needed more testing! So, I wrote a story about taking shortcuts and read it to my granddaughter, Camille."