Management - Do you know who has authority?
Last updated by Brady Stroud [SSW] 7 months ago.See historyOK, once a project gets going, you can end up dealing with many people on the client side. From the Boss to the Business Decision Maker (we call them the "Product Owner") through to Mary the receptionist (aka "users"), everyone has something to say about the software as it is being developed. However, when you are working on a Time & Materials basis in a rapid development environment with continually changing specs, you have to be certain that the work you are doing is authorised by the person who signs the cheques.
| To: | John, Bob Northwind |
| Cc: | Sophie |
| Subject: | Changes Requested by Sophie |
(CC'ing the Product Owner Bob)
To Myself
As per my conversation with Sophie, she has requested the following changes to the application: modifying the report ContractRenewal to include the "MaidenName" field from the ClientContact Table, and positioning right next to the LastName field.
Hi Bob
Please let us know ASAP if you don't want this problem fixed.
Thanks, John
Figure: Sample Change Request Confirmation email
So, say Alan from Accounts would like the Username and Password authentication to have a "remember me" checkbox for the Accounts module. This sounds reasonable, but it doesn't mean that you should charge right in and start coding. The following is the recommended approach to governing this process:
- At the beginning of the project an employee from the client is assigned as Product Owner. This person has full authority as to what work is "in" or "out". Every new item of work should be visible to the Product Owner. (CC is your friend, @mention is your friend)
- Whenever someone who ISN'T the Product Owner makes a request for work, the Product Owner must be CC'd. For example, if Mary the receptionist has not done this, the developer sends the email again to himself, and CC's the Product Owner (and of course other relevant people).
- Note: The assumption is made that the task is good to go, so it is the Product Owner's responsibility to reply ASAP if they don't want the problem fixed.
