The Regenerate Web

facilitating the regeneration of software teams

User login

Syndicate

Syndicate content

Services


Add to Technorati Favorites

Project

- 1My campus life
- delivery (3)
- duration (1)
- effort (3)
- estimation (4)
- Iterative (1)
- measurement (1)
- metrics (1)
- Planning (2)
- PMI (1)
 - PMBOK
- Progressive Elaboration (1)
- risk (1)
- Rolling Wave (1)
- schedule (1)
- task (2)
- velocity (6)

Management

- Boss (1)
- consensus (1)
- influence (1)
- leader (5)
- meetings (1)
- Motivation (1)
- process (1)
- Time Span (1)

Browse archives

« July 2010  
Su Mo Tu We Th Fr Sa
        1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31

Analysis

- abstraction (1)
- metaphors (1)
- modeling (3)
- requirements (5)
- research
- semantics (1)
- Analysis (1)

Who's online

There are currently 0 users and 1 guest online.

Learning About Stuff

Last Friday, I went to a presentation by Martin Fowler. You may know Martin From some of his books, or from his participation in the Agile Alliance, or from his role as Chief Scientist at Thoughtworks.

Early Delivery - Part 2

| |

Early delivery has been considered the first commandment of agile.  In the principles behind the Afile Manifesto, the first paragraphs says:

Early Delivery

Glen Alleman of the Herding Cats Blog in his post "Make Speed Not Haste" has once again taken an agile concept out of context.  In this case, it is about "early delivery".  

Procrastination vs. Iteration

| | | |

In his excellent management skills blog, Tom Foster posts a brief series on Procrastination. Brad, a middle manager, procrastinates and brings the organization to a state where they are months behind on a major project. Tom spends a lot of time talking about time-span, as a predictor of management qualification. I appreciate this, as it has made me more aware of my limitations.

Why velocity isn't as bad as Glen says

| |
Glen Alleman of the Herding Cats blog is one of the most experienced project managers I have ever read.  His background is amazing.  He is bright, and has practical knowledge of projects that I will never have.  However, he is missing the point on agile and velocity.
I recently read his post "Simple Never Is" and have this response to offer.

Metaphors in Requirements

|

This week I was asked to review job descriptions for analyst roles within our IT function. The roles were "Analyst, Business Systems", and "Senior Analyst, Business Systems".

The person who asked me was looking for my opinion because I am strongly opinionated, blunt, and have experiencing hiring and leading business analysts and requirements engineers. She wanted to understand the difference between an analyst and a senior analyst.

Requirements Success Factors

| | |

Last January my role was redefine, and since then I have been managing two teams covering diverse aspects of two software programs. The first team is responsible for requirements, functional design, quality assurance, and the second team is responsible for support.

I'm Back

I didn't realize how long it has been since I posted. I have enjoyed sharing my thoughts, but this last year has been a real challenge. I have truly had a year of death-march-groundhog-day at work, while away from work I have been consumed by some personal activities that have been really taking a lot more time than I expected. Nothing catastrophic, yet. Just stuff. It happens.

I just wanted to drop a post and let you know that I am back - I never really left, but every time I had something to post, it was pretty negative, so I just didn't.

Priorities

|

Priorities - a cautionary tale

Earlier this month was the first time in twenty years that I have not gone to work late on the first day of my kid's school.  Don't get me wrong, I still have kids in school, it is just that due to a conflict between other work and personal schedules, I needed to schedule a critical meeting at work this morning.  

Losing It... and Finding It Again!

Losing It...  (and Finding It Again)

Just dealing with the facts of a meltdown are not enough.  Last week, I had such a meltdown.  The circumstances are less relevant than the damage and subsequent damage control that such an event can cause.  

In a phone conversation with a liaison from a software consulting firm that I employ, I lost my temper.  I said things that threaten the relationship, that could make working with this person, and his firm much more difficult.