milking cows the E way

Client has 2 cows and u need to milk them

1 First prepare a document when to milk them (Project kick off)

2 Prepare a document how long you have to milk them (Project plan)

3 Then prepare how to milk them (Design)

4 Then prepare what other accessories are needed to milk them (Framework)

5 Then prepare a 2 dummy cows (sort of toy cows) and show to client the way in which u will milk them (UI Mockups & POC)

6 If client is not satisfied then redo from step 2

7 You actually start milking them and find that there are few problem with accessories. (Change framework)

8 Redo step 4

9 At last milk them and send it to onsite. (Coding over)

10 Make sure that cow milks properly (Testing)

11. Onsite reports that it is not milking there.

13. You break your head and find that onsite is trying to milk from bulls

14. At last onsite milk them and send to client (Testing)

15. Client says the quality of milk is not good. User Acceptance Test)

16. Offsite then slogs and improves the quality of milk

17. Now the client says that the quality is good but its milking at slow rate (performance issue)

18. Again you slog and send it with good performance.

19. Client is happy..

By this time both the Cows have aged down and can't milk

ok... the idea is there... for what exactly im unsure of yet, but its there!

and secondly, i think you might want to actually define what its supposed to mean

CTO

CTO

It is in tech humour................it is having a go at structured methodologies (SSADM, PRINCE2, CMM, Catalyst etc............) and formal lifecycle project management.

Looks like it was written by an OO freak with all the enthusiasm for documentation of a C++ programmer :cool: :D

Cheers