Browse by Tags -

Browse by Tags

How healthy is your code?

Technical Debt is not simply an Agile buzzword more than it is a fact of software development. Just like any other debt it imposes negative ramifications on the software and significant loss is revenue. I hate to get touchy feely but I think what I am about to say holds the most weight when presented...

Posted to AgileJoe (Weblog) by Joe Ocampo on 08-21-2008
Grapevines and Agile make great Wine...

I couldn't resist the title. By this point in most of your careers you have been exposed to the grapevine exercise. This exercise is geared to show you how one thought through many control points gets distorted and misrepresented. I believe this is true for the majority of conversations out side...

Posted to AgileJoe (Weblog) by Joe Ocampo on 06-24-2008
Matrix Resource Management and Agile

I have been having an ongoing discussion lately concerning matrix management styles and how they conflict with Agile Project Management. If you look at the traditional "Iron Triangle", resources are estimated, in that change is expected in the resource allocation depending upon task and assignment...

Posted to AgileJoe (Weblog) by Joe Ocampo on 06-23-2008
Hanging your code out to dry

I was speaking with Marcus Bratton the other day about code reviews. We both agreed that they are very valuable but finding the time is probably the most difficult aspect of any code review. Paired Programming helps to eliminate the need for code reviews but paired programming caries waste of its own...

Posted to AgileJoe (Weblog) by Joe Ocampo on 03-27-2008
Passionate about People!

Over the last couple of weeks I have had time to observe many aspects of myself and of the development community. One of the epiphanies I had was that I am passionate about people more than coding. I love to mentor other developers. I love to mentor future development managers. I love to coach others...

Posted to AgileJoe (Weblog) by Joe Ocampo on 01-02-2008
Customer Perception Model: Know thy customer

It's important to know how your "working" software is being received out in the field. Immediate customer feedback is one thing during a release but what about after the code actually gets out into the field. How are those users feeling! Enter the Customer(field) Perception Model: As you...

Posted to AgileJoe (Weblog) by Joe Ocampo on 12-17-2007
User Story Templates

A couple of people emailed me and asked me what the story cards looked like on our information radiator . It is important to note that these story cards are only drafted after extensive modeling and feedback sessions during our modeling week. We don't use them in the traditional XP fashion and caution...

Posted to AgileJoe (Weblog) by Joe Ocampo on 12-09-2007
Information Radiators: Make life visible

A couple of people have asked me how we track our work for our iterations. We basically use a somewhat simple information radiator . Information radiators serve to quickly give everyone on the project team a quick indication on what needs to be done, what is being worked on, and what has been done. Information...

Posted to AgileJoe (Weblog) by Joe Ocampo on 12-08-2007
When passion becomes dogma is it elitism?

From Wikipedia Passion is the emotion of feeling very strongly about a subject. Dogma is the established belief or doctrine held by a religion, ideology or any kind of organization, thought to be authoritative and not to be disputed or doubted. Elitism is the belief or attitude that those individuals...

Posted to AgileJoe (Weblog) by Joe Ocampo on 11-14-2007
There is always time for TDD

I just finished reading Dean Wamplers post on Why you have time for TDD (but may not know it yet...) . He brings up excellent's points that Agilist struggle with when trying to convey to a client on why they need TDD and how they can justify spending the time to do it. A must read.

Posted to AgileJoe (Weblog) by Joe Ocampo on 09-30-2007

Page 1 of 2 (16 items) 1 2 Next >