Skip to main content

Agile Project Management

by Jim Highsmith (978-0321219770)

Agile Project Management (APM) was recommended to me by Allan Kelly, when I wanted to lean more about it and try and get a few pennies to drop. Allan's more than a little bit of an expert on project management and Agile in particular, so I take his recommendations seriously.

It's a good book. I know I say this about a lot of books, but it's probably more verbose than it needs to be. The first two or three chapters are a general discussion about project management and how APM differs and has more to offer.

Chapter 4 to Chapter 8 is a discussion on the principals and practices of APM. This is where the really interesting and informative material is. Given what I've heard about Agile, I was surprised by the fact that being an Agile project manager is a full time job and there is a fair amount of documentation, even if it is mostly to keep external stakeholders happy. What's important is to get the right amount of documentation and that is also made clear in the book. APM also encourages some upfront planning, but again just enough, so that the team has a clear vision of where the project is going. However, even these chapters I felt were verbose.

I feel I understand APM far more than I did before, but that there's still a lot to learn, that is mostly likely to come by doing. Although APM is meant to handle change, it still seems that change has to be controlled within an iteration. I still feel there's something I'm missing there.

Comments

  1. Thanks for the name drop!

    While I can believe that large agile teams need a dedicated project manage I wouldn't expect a small team too.

    In some ways the role of the project manager is to ensure what has been asked for gets delivered. In Agile you replace delivering "the specified requirements" with delivering value. The important point being that what is delivered can, and does, change often.

    Therefore while the project manager role is reduced the product owner or manager role in increased.

    Unfortunately, in the UK at least, the Product Manager role is at best misunderstood and at worst not understood - people think you meant to say "Project" but accidently said "Product". The words may only be 4/7s different but the way the way the tasks are performed are completely different.

    ReplyDelete

Post a Comment

Popular posts from this blog

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...

RESTful Behaviour Guide

I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as  Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resour...