Instead of reading one more article on Agile, let's see conversation that takes place in an Agile team during their Daily Scrums.
Let me introduce you to our Agile team under observation.
 | King Frog - Agile Lead |
 | Tom - Agile Developer |
 | Missy - Agile Developer |
 | Hog - Agile Developer |
10:30 a.m : Day begins .....
| : Let's start with our Daily Scrum |
| : Who would like to start? |
| : I would! Yesterday, I completed test cases and implementation for my XML configuration module. Today I plan to integrate it with the system. I do not have any road blocks. Basically my world rocks! |
| : I was supposed to work on the Mysql DAO module, but I got stuck with a Mysql transaction problems. I have written to the Mysql forum, I expect a resolution by today. This means by yesterday's task of integration with system does not complete and I will have to work on it today also. |
| : Ohh!! that means I can not start with my service layer. Well I wrote the interfaces for the service layers yesterday and today I wanted to write the implementations, based on Mysql DAOs provided by Hog. That means I can not work on what I planned for today and tomorrow :(. |
| :So do you have any thing else on plate, which can be done in 2 days time? |
| : Well, yes indeed, I was coming up to that point. I was planning to write client code for my service layer. I was to myself write a stubs for the Mysql DAO. This will help me test the client code also. I was planning this at a later time, but looking at the situation now I can very well continue on that task for today and tomorrow. /my immediate plan would be : Today I work on the DAO stubs and tomorrow on the implementing and testing client code for my service layer. |
| : Good to know, you yourself could plan out things for you |
| : Well that's what I have learnt working in Agile for a year. I know I have to contribute deliverables instead of just doing my tasks. I also know I am responsible for it. |
| : Great!! My turn now, Yesterday I did code review for Tom and wrote test cases for Hog (in pair programming). Today, I am preparing the deliverables which we will demonstrate to the client in Tomorrow's call. |
| :But the Final Delivery is months ahead, What's the point in doing a demo now? |
| :This way we will know early whether the client approves these features, if yes great. Even if there are some changes, it won't cost us so much at this course of time. In the worst case if the client doesn't want a particular feature to be put in at all (after getting a feel of it), only 1-2 weeks of work is wasted. |
| : So we have the meeting with the client tomorrow? but I heard that he is out of town and won't be available for tomorrow's meeting. |
| : Ohh! yes I remember now. Well in that case, let me send him a audio video recording of the demonstration. This way the client would be up to date on the most recent deliverable. Also, I will reschedule the meeting some other day in this week itself. Getting a feedback from the him on our deliverables is very important for our Agile Story to succeed. Lets get started on our work, Team!! Ribbet !! |
Did you observe?
1. The conversation indicates the team's approach is bottom up
2. Changing prioritites is accepted in a very positive way
3. Individual contributors play a bigger role, than just focusing on one's own task.
4. Every one is watchful for risks coming up from dependencies, also every one seems to be able to come up with mitigation plans
5. Client involvement is on a high priortity
6. Every one knows what every one else is doing
No comments:
Post a Comment