Friday, December 26, 2008

Seasons Greetings !

0 comments
Seasons greetings to all known and unknown blog readers and wish you all the best from my heart!
Thanks to projectized blog for connecting you with me from every corner of the world and thank Dilbert who keep me laughing and giggling all year long… :)


So this is one of my favorites this year which may bring a smile to you today…(Hopefully :-) ) and waiting to see so many good stuff in 2009.





Wednesday, December 17, 2008

Project Communication in Outsourced Project Management

5 comments
We all know that, in average a project manager spend more or less 90% of his or her project management time for communication. Proper and effective communication is one of the most challenging areas in project management.. How about communication in outsourced project management..? that is any PM’s nightmare unless they manage it properly from day one.
This issue is not about language, either you do nearsoursing or outsourcing, nowadays most the professionals will speak good English. But poorly managed remote communication may increase the risk of project failures drastically. All aspects of remote communication should be carefully quality managed by a project manager who is in to outsourced project management. Unfortunately this needs quite lot of experience.
Over the years I’ve seen most the PM methodologies have matured, and processes has been introduced for project management.. New tools have come to the market., but still the challenge of remote communication remains the same.. How do we overcome it ?
Recently I had a chat with one of my project managers. He told me a story about a project he has managed while working in his previous company. It’s a very small sized project developed for one of the European countries. So him being the project manager sitting in the development company in Sri Lanka has communicated with customer via 600 emails. It gave me a fright.. Are we really doing something right here?
Have you heard about “Mad email Syndrome” which is very common in outsourcing operation. These are the symptoms;.
Project Manger from Venders company writes a mail to the customer about his questions regarding some requirement.. A nice email. Customer reads the mail., thinking why these people can’t even guess some simple thing like that …then he writes a reply in Blue color as comments for each question. ( yes we need to clearly separate the answer from the question)
Now that the Vendor's project manager who waited impatiently till he get all the answers to his questions receives the mail and he goes through the blue color comments made by the customer.. after reading that he find its disapointing and the customer has not answered half the things as he expected., most the points are not elaborated., so it creates much more questions for him now. Then what he does.. ? he uses another color., mostly seen is green , write comments in green color again under each blue color comments.. send this to the customer and CC to his whole hierarchy to save his back :-) and show them that he has still not got the answers right.
Customer receives the long email which is flashing in many color comments now.. He get really worked up.. certain symbols can give him a totally a different tone to the email. He write the comments in red color now.. and send it to the vendors PM again..

This doesn’t stop here… Is this situation new to you ? Im sure if you are in to outsourcing business you may have gone through this situation many times. This chain of email communication is a very strong risk trigger of project and relationship failure between outsourcer and outsourcee.. Why such a useful tool such as email can create this much of damage?
1. When communicating through emails , the other party doesn’t see your body language. They read exactly the meaning of word to word which may sound totally different to what you meant.
2. The other party don’t hear your tone of the voice. or your giggling . Recently I saw a customer commenting something like “Remove this field! “ with “!” what is that additional “!” is for ? these may create some unnecessary issues
3. Its very common that both parties think the other party is the idiot. They put less effort to understand each other. This may totally be different if you had a face to face discussion.

So how do you quality manage this remote communication? My advice for project managers are as follows;

1. Do not have email communication over 2 loops., if it goes over always try to use Voice via skype or telephone line. Or even use some tools such as Webex. Which is really good.(video con would be the best but unfortunately most of us do not have that facility )… Hmm How about Cisco TelePresence.???. I love to experience that !! :-)
2. Always read and re read your emails before sending.. do they mean something wrong to the reader.. make sure you communicate very clearly
3. Do not send too many emails. Try to summarize possible information in one email. Have your subject lines very clear.
4. If you need only 1 question mark have one .. But not three.. When you ask “can I have these replies by before end of business today? “ has a major difference between “can I have these replied before end of business today???????????”
5. Be very clear and elaborate on required points.. try to use tables as much as possible
6. Be warned when communication is not going right.. always ask help from your supervisors before it becomes too late.
7. Have the right attitude to respect the other party . if you read the mail in negative mind., you will end up with negative results.
8. Send customer status reports frequently., leave very little room for questions. Reports should be completed.
9. Always have project budgets to meet the customer face to face at least once in your project life. That will make your project communication much easier.
10. Understand that the time customer can spend for you is limited. That’s one reason why he or she outsource the project to you. Respect the fact and always think twice before you raising the question .Because you need to get the question right at the first time .

Sunday, December 07, 2008

Team Work.. Again.. :-)

0 comments


Who said geeks are boring ?? :-D

Saturday, December 06, 2008

All work and no play ???

2 comments
few readers recently asked me the question.. "Why do you make such noise about planning Poker..We have been doing this all the time even long before SCRUM became popular.. we have been discussing with all our teams when estimating Instead having poker cards and playing poker.. …”.. Yeah.. Ok I will answer..
1. When you discuss with the teams about estimation at the meeting without poker.. Fine.. But will everybody’s opinions be highlighted? Or is it still the voice of few people in the team? Think about the last discussion you had with your team.
2. Sometimes work is uninteresting.. Have you heard that before? (Specially the estimation Yaiiik.. to me that’s not a very interesting part of PM J ) But that depends on exactly how you engage with those activities..Playing poker can help in this a lot. It’s fun!
3. When you just discuss with the team about the estimation for a functional point or for the user story, they just answer.. But there is no way that you can visualize their thinking with some relative weight at the time of the discussion.. This is where your Poker card set helps. And the each individual try to reason out their decision with lots of valuable points as they are exposed with the card they play every time.
4. Further this can eliminate chaos which happens in most the planning meetings. Can think lot more.. But these are the main reasons why I encourage my teams to play poker at the product backlog and the sprint backlog planning meetings.
I read an interesting paper by Jason Yip today about Project release planning with Poker..But this is not with our card set.. This is with real tokens.. J Interesting … you can find the paper here…
http://hillside.net/plop/2007/papers/PLoP2007_Yip.pdf

Wednesday, November 26, 2008

4 comments
Ok.. its kinda sad thing.. This time Im very unlucky with Amazon.. I ordered the book., Agile Estimating and Planning (Robert C. Martin Series)
by Mike Cohn. A book which I really wanted to have with me after going through many of his blog posts and the book reviews..
But it was never delivered to me. So I made the complain to Amazon.. they sent it again.. Didn’t receive yet.. its over one month now :( ....disappointing … Not a problem with Amazon.. but Im sure its something to do with our internal postal process.. As I checked with one of my colleagues and he said that they dont deliver the books to our doorsteps now . we have to go to a central post office and collect it .. ...:-( whyyyyy ????????????..............But I didnt get a letter like that either... So I dont know......

Do I raise the issue again.. hmmmm..

Tuesday, November 25, 2008

Team Work :-)

0 comments
Good Luck Guys !!

Thursday, November 06, 2008

Good Bye..

0 comments
Michael Crichton had died ??? No I dont think he will die ever....What can I say.. Cant find any words..

Wednesday, November 05, 2008

SCRUM practitioners in Sri Lanka ?

4 comments
Today I heard some good news.. We are building some SCRUM community in Sri Lanka ? I heard that one company has already sent 2 IT professionals for Certified SCRUM master training to India and there is another company who has got some professionals down for training their whole team..Its very happy to see that SL IT industry is spending on PM profession more and more nowadays..I still can remember how hard it was for me to learn SCRUM when I practiced it first in 2005 with my very first SCRUM team..(Thanks to Dina Scott who gave me all the help at that time :) ).It has changed now to the positive side.. Its never too late. Recently another group of people in one reputed company went to Philippines for a very good SCRUM training too..
Not Only SCRUM I see lots of professionals get enrolled with PMI too.. The Only problem with PMP certification is that one needs to have minimum of 5 years Experience by managing farley good projects to face the exam well and lengthy study cycles. But for Scrum Master training its just 2 days course most the time.
Ok., for a newbie who is confused on for what to spend time and money its like this…
PMP certification is offered by PMI institute USA and it’s the largest Project Management institute in the world at the moment.
PMP exam covers almost all the aspects of Project Management, Starting from Ethics, soft skills PM technical skills etc …. And the framework is industry independent.
But SCRUM training covers only How you practice SCRUM. The basic guidelines. So you cannot expect to be a certified Project Manager by learning only SCRUM.. I think both these certifications together comes very handy for any good Project Manager in Software Industry.. Its matter of how you find time for all these :) Anyway I wish if we have enough SCRUM professionals in SL to build a SCRUM community.. Most the countries has that. Yes We have a PMI Colombo chapter already..

Tuesday, November 04, 2008

SCRUM ... Issues.. ?

0 comments
I had an interesting SCRUM discussion lately.. With one of the visitors who came to office. We had some point to discuss the PM frameworks and then we were discussing SCRUM in detail. He came up with some interesting point …
Will SCRUM kill the creativity of the development teams… ?
Developers produce piece of code.. in SCRUM we go up to the atomic level planning..so this specific task can be done in X number of hours.. true.. But if there is no such time boxes can they be much more creative…….I mean if we don’t look at the daily velocity of the graph… what would it be?
HmmmmmHmmmm….. Hm…. I was stuck…. Yeah there is a point..
While going home I was thinking about this...
I think its like this .. In SCRUM we discuss what the customer wants in detail and in more detail at the Product backlog meeting as well as in Sprint planning meetings.. So we understand what our customers expectations are to a greater extend. So what we all do is producing what customer wants.
No matter what the methodology or framework we use, we design the architecture and we develop the code..With long planned frameworks what I see is that the developers have more time for creativity.. true.. But it enables more risk of over engineering.. Which result much more risk of sacrificing quality or delivery times at the latter stage of the project which results the project failures. May be soem most important part of the project ... who knows...Especially those long planed methodologies commit on specific strict deadlines.
In this case I think by using SCRUM one can eliminate those over engineering and risk of schedule overruns at the latter stage..In the same time it enables the “Defined creativity” :-)

if somebody needs to be much creative about a features or a piece of code, they can even discuss this at the daily scrum meeting.. making it transparent.. adjusting the calories of the sprint backlog. “Yeah I hear you techies.. That’s not the tech thingies work right ...LOL...!!! But unfortunately that’s the way the “bottom line” works :-) there are tradeoffs
Now that I wrote about this, I need to explain few problems I see in SCRUM.. I see some of the practitioners believe scrum like a religion.. But thats not right.,.. As I say in my own words. SCRUM is not god given.. Its still evolving as a framework and still we see many issues.. Following are some of the issues I saw when practicing scrum.
Agile doesn’t fit for everybody . we have few left alone people when we introduce Agile Practice to corporate
The customer needs to be well educated.. Yeah .. they say “Think Agile” but never works that way.. need proper discussions and the understanding with the product owner before providing that much of transparency. Otherwise this will make your project and life miserable.
In the same time it’s a stress to commit to 8 hour work tasks everyday.. I know few guys who plan their sprints with 6, 7 hour tasks. May be that’s a solution.. but teams need to mature a bit to work with that.
Sometimes introducing gaps between sprints also helps and teams needs to be cared more when practicing scrum.

Sunday, October 19, 2008

Dealing with difficult people...

2 comments

Today I got a very good opportunity to go through one of Margarat Meloni's online lectures about dealing with difficult people.


Im not so bad when it comes to dealing with difficult people..:-) been there done that !

But this lecture of Margarat is absolutely useful not only for project managers .. but for every corporate worker. She explains how someone shoul deal with "difficult Mammals" very professionally.

As project managers we work with different types of people every day.. People with different attitudes, different levels of knowledge, different level of maturity, different nationalities etc.. So working with all the people is not same every day. We find some jerks some times.. But she explains how we shouldn't be another jerk in such situations.

Some times we think people are difficult.. but may be we are difficult too.. But if you want to know how you get away with all these corporate difficult situations as professionals without loosing the focus on our goals and work.. I recommend you to go through the lecture.

Specially in Sri Lanka we dont find such PM soft skills improvement lectures easily.. So this may be an alternative to improve your PM skills... Just check that out...

Saturday, October 18, 2008

Implimenting SCRUM in my new company

2 comments
I changed the job.. So what ?????
Changing the job was sort of a nerve breaking decision
But ….I did it again !..
not too bad .. for the 3rd time of my career:-)
With this decision I had to let go many things what I had.. Instead I got very interesting challenges and another new bunch of cool guys to work with....!..
Ok So I started at the new company.. I’m lucky enough it’s a startup so the start was not that hard. Lots of things to do at once… understanding the team members, skills, Projects, conflicts, risks, problems , issues…way forward , new processes (and more than anything getting used to some HR processes which I have never got used to J ) you name it !
I really appreciate the project centric culture which we are trying to build at the new company. But this needs little time to mature… No matter what.. Healthy corporate culture is very important for the people to be focused on their projects and not on other unnecessary facts and politics which I have”0” tolerance level...
Did you ask what I like the most about my new company?? Its my Note book bag.. :D Kind a cute…
Anyway that’s a different story..
What I thought to write here is that the experience of introducing SCRUM as the PM Framework to a totally new organization.
Its really a good experience. I started with one small team.. Who was quite corporative to adopt to a new way of doing things.. We created a very simple product backlog with all the user stories which need them to go through their research work. The PM (New SCRUM master )was very corporative and he found few cards which we could number as the Planning Poker card set. We started to play.. it was bit harder at first time.. But when it comes to 4th or 5th User story level the team was progressing so well. I was so thrilled to see all the silent team members talking in the planning poker session to back their idea about the user story weight.
Once we finished measuring the product backlog team created the Sprint back log. This project has only one sprint and that’s also 10 days.. Im happy that we started with a very small product backlog.
At the time of Sprint back log planning I could see some instant improvements from the team members. They worked so hard and actively as a team to get the sprint backlog planned. They decided to have the scrum meeting at 9 AM every morning..
Ok the very first Scrum day came … I was waiting… to observe their daily scrum meeting..few guys came .. they were having BF.. it was around 9.45AM still some guys are missing.. I thought.. I made a BIIG MISTAKE… Forget about scrum !! It doesn’t work…
I waited patiently till all the team members get together.. Had a very straight forward discussion.. To my surprise every team member accepted the importance of daily meeting at a specific time.. and they decided to have the everyday stand up meeting at 9.30 AM..
Ok lets see..
The next day the situation was so much better.. Almost all the team members were at office on time ready to have the meeting.. I got a skype message from the SCRUM master to come and observe the meeting.. It was a great start.. From that day onward the team progressed very well.. Understood the value of SCRUM, and value of their own team members.. Working on time boxes etc.. Currently they are about to complete the burn down of the sprint and seems they had a very good sprint.
Ok .. I think 10% of things I wanted to do was done with it.. the next task is to standardized the templates, artifacts and document the process and add them to the company process library..
The Next team situation was so much different. The Project was already initiated and that’s bit of a complicated case which I will study more and write in my next post…

Sunday, September 21, 2008

Planning Poker - the problem continues…

3 comments
Sorry guys still I didn't find sufficient answers to post here for the previous post I posted about problems when playing Planning poker.. I will provide answers once I find some good and logical explanations..
Now I have a new problem…. There you go… :
When Playing planning poker the team express ideas in front of the product owner to come in to a conclusion about the weight of user stories, clarifications, etc.
We do not have programmed robots in our teams to have same level of knowledge and skills. Though SCRUM is for good for good developers, ( Or even Software development is good for good developers according to Ken Schwaber - SCRUMforTEAMSYSTEM) in reality we get a mix to our teams..
So after observing the discussions going on …there is a product owner who says… Look I don't want guy X and Y in this team.. I need another like guy Z instead of X and Y . then we can burn down the back log more faster in sprints.. You guys agree to burn down only this amount in this sprint because your guys are not experienced. In traditional Project management what we do is we colour all our user front ending with really experienced and good guys and get the project delivered some way or the other. In SCRUM as we produce this much of transparency, Anybody who faced this issue and could you please explain how to overcome this issue..?

Saturday, September 20, 2008

101 post

2 comments
Oh I really cant believe this .. Today Im writing my 101 post and its about something really cool..

Its hard to believe that I have earned some money from the blog.. And I received a gift card from Amazon :-).. So I can look forward to own some very good books..

Thanks to all you readers for reading my posts..Clicking the adds, Purchasing the Podcast.

More than anything Im so grateful for having patience with me for all my never delivered promises.. and specially reading not perfect language..

This blog helped me to network with most the known professionals around the world.. Im so happy about that. The knowledge we share is so valuable.

Thank you blog! Kiss kiss.. :-) Hug too... !! you are 100 posts rich.. ! ( some of them must be crap though ;-)


Friday, September 19, 2008

Problem I faced with Planning Poker

2 comments

I copied this cartoon from www.implementingscrum.com.. Im a cartoon freek.. and thrilled to see SCRUM in cartoons...:-)

We played planning Poker for the 1st time and following are the problems I faced.. I will find the answers for these questions from experts and post them here later..

1. When Moderator reads 1 story we kept playing Poker and came out of an estimation to that specific story., But when we went through the PB more and more., team wanted to revise the previous story estimates again as its a comparative thing., How do you handle this situation?
Do you get the team to analyze the PB before coming to Planning poker so they will be more or less accurate with their comparative guess with other user stories in the rest of the product backlog?

2.There was one user story which we had to purchase some device for that. Scrum master ask where do we do the procurement management, planning , Cost estimation etc, Will SCRUM has some guidelines for procurement management for the project.

3. Customer who acted as the product owner didnt have answers for some of the questions.. there were situations such as I need to check with my infrastructure guys.. I need to ask my BI manager etc. How do you tackle that situation?

4. for certain stories we felt that we need the use cases or further analysis before thinking of their weight. ..

5. Looking at from the Project Office I saw many team for many projects they had different type of assessments. As an Example., same story "User needs to log in to the site and fill the registration form" was rated by the Team A as 5 and Team B as 20.. so how do I compare and see each team performance from the top when I look at my teams product burn down charts?

Comparison of SCRUM Vs PMBOK

5 comments
Comparison Of Pmbok And Scrum
View SlideShare presentation or Upload your own. (tags: backlog scrum)
* credit http://projectized.blogspot.com as the source
* do not publish it (in print or on the web)
* do not circulate it (please direct people to this address)

Thursday, September 18, 2008

How to play Planning Poker

0 comments
Planning Poker is a game which help us to do planning in Scrum. We can use it for adding the weight to the user stories.
Ok this is how it is played..
1. Scrum master get ready with the Planning Poker card pack for each member of the team who participate this session
a. Those cards should have numbers such as 0,1/2 ,1,2,3,5,8,13,20,40,100. (Why these numbers ? Let me find out and tell you .. : )
b. Write the Numbers large so it is visible when needed.
2. Appoint a moderator (Can be anybody)
3. Ask the Product Owner to come to the Session ( He doesn't play Poker)
4. Moderate Read out the 1st User story
5. Team members question the Product Owner about the story and Product owner answer them
6. After all questions are answered, each estimator privately selects a card representing his or her estimate.
7. When everybody is ready all the members put selected card to the table.
8. There can be major variations., one member may have selected 2 while the other person has selected 5
9. Then they give reasons for selecting those numbers. One may think there is some additional research needed to perform the task., another may have thought much more easier way to do that task
10. Once all these points are discussed and asked the questions from the product owner, again the team play the Poker - This time its expected it to be more similar numbers
11. Of the numbers are not quite satisfactory it goes through another round. In normally you play the game for 2 rounds per story point. But there is no rule for that.
12. In last round if everybody comes with 3 and only one person comes with 5., we ask him or her whether she is agreeable to estimate the weight points as 3. If she agrees , we have no issue., if she doesn't agree we need to listen to the reasons.
i. Planning Poker brings Multiple experts opinion to the table
ii. It has the team buy in for the final decision
iii. Averaging Individual estimates lead to better results
iv. Its more fun than just traditional project estimation by Project Managers and few senior members of the team

- This idea is extracted from Mike Cohn's Agile estimation and planning.
Be a PMP
 

PROJECTIZED. Copyright 2008 All Rights Reserved Revolution Two Church theme by Brian Gardner Converted into Blogger Template by Bloganol dot com