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

Venture Quotes for a softening economy

Guess who said the following? "There's a lot of hot air and arrogance in the (VC) business that we all would be better off without" "...useless pontificating in front of entrepreneurs working harder than (VCs)..." "...VCs who constantly speak of deals and projects , reveal their self-interest and slight the labor and dreams of the entrepreneurs" If you think it's some disgruntled entrepreneurs who don't "get it", think again. In the past, I've made some pretty strong but heartfelt things, and I could have said the above, but I didn't . Read on here to learn who uttered these pearls of wisdom.

User Stories: you're not Agile without them

Failure to effectively transition to Agile development is often based on a fundamental failure to understand what a User Story is. Allow me to explain. The most important aspect of a User Story is that it's an independently *schedulable* unit of requirement (feature). The key to achieving the "independently schedulable" characteristic of a user story is that you express it in terms of how a "user" would use it. This leads you to a unit of functionality that's implemented end-to-end (UI to backend) that a user can actually interact with. Not surprisingly, because of the focus on how a user would think about a feature, a user stories are highly readable - and could very well be written by the users themselves. However, the other important and less obvious aspect of a User Story is the emphasis on communication with the end-user and getting confirmation on the acceptance criteria. Describing all the requirements as User Stories for a decent sized product is