PMI Colombo Chapter Event - November.

Offshore project management and use of Agile. – Part 1

Its again Winter in North.. So we are busy here at Exilesoft, Sri Lanka with most the customers who visit us. That's one nice thing in offshore business, as much as we enjoy travelling Europe, it seems our customers have found a second home to come when the winter starts in their countries. This is an ideal time we get to work together again as collocated teams. For them its quite exiting to work with us as well as to extend their business trip for one week or so to have little relax time in this exotic Island, explore the culture and have a better understanding and stronger bonding between the customer and development teams. Altogether it’s an awesome experience for both the parties. I too enjoy such visits of our customers a lot.

In the same time, being in software offshore business is not easy. Unless you have the right relationship between the outsourcer and outsourcee, the offshore business can become really painful to both the parties.Software development itself is quite challenging even in collocated development environment. When it comes to offshore software development, we are adding some more complexities to it, simple reason is that an offshore development team faces the same complexities which an in-house team faces + much more . So the Project management in this environment by balancing this distant relationship is quite a challenging endeavor.

This series of articles which Im writing to ICPM, will be focused on the challenges in such offshore business and how we use Scrum (One of the Agile methods) at my current organization to overcome these mostly seen challenges in Offshore business. I hear you.. It’s a trade off. When we overcome some of the main issues., there will be other issues which we may face.. Its understood. Its all about how to overcome the most serious issues in such environment and deliver the right value to the customer without scraping the organization’s bottom line.

To manage these offshore/outsourced projects with distributed teams successfully, We first need to understand why Organizations outsource their software projects. By working twelve years in this industry I have seen the same reasons with most my customers who decided on outsourcing their projects to us irrespective of the size of their projects.

1. Skilled Resources
In Some of the countries , its quite hard to recruit skilled resources compared to others. May be its all about the availability of such skilled resources, the market competition as well as the difficulty of hiring such experienced resources only for one or two projects (Shorter time period).

2. Business Focus.
Even if they have these resources available to hire, if the organization’s main focus is not the IT business, it may not be always wiser to hire such resources and expand the IT departments which is not their primary business focus. As an example, a company in travel industry needs to be focused on travel business instead being focused on expanding its software development. So in this context, outsourcing its software development to an organization which focuses on software business can be a wiser move.

3. Protecting the Intellectual Capital
If an organization develop one of its core software products which will give them their competitive edge in the market, the last thing this organization may need is to have its developers who worked on this product to join its competitors with all the knowledge about the business. Some times when an organization hire people from the same country or state, there is quite a risk factor that the developers who work for this product may join their competitors when the assignment is over. But outsourcing this product to a country far away which doesn’t have such closer relationship with the other organizations in the same market may reduce the risk factor.

4. Cost
Most the organizations carry their cost benefit analysis before outsourcing its software projects to other companies. Its quite important that the cost difference to be a visible factor. However there is hidden costs in software outsourcing which I will discuss in a latter article under this series.

5. Round the clock / Extended hours of production
As an Example, if there are 2 distributed teams in an Organization in Norway and Sri Lanka, and if both team work their 8 working hours, the total production time expands to 12 hours as Norway is 4 hours behind Sri Lanka. This helps in some of the product development and software support work.

Its important that as the outsourcee we understand the key factors which enable the outsourcing business of the customer and deliver the expectations throughout development.

In the next part of the article, I will discuss the tiers of such software outsourcing and how the challenges increases in each tier. >>

P2P Conference 2009 - Agile Stream.

Monday :
Most the speakers who reached Cairo before the conference had a visit to Giza Pyramids and the museum on Monday which was quite fascinating , specially to get to know each other as some of us have never met before and in the same time to explore Cairo, History etc. We all had lots of fun together. What I mostly enjoyed was the camel ride !

Picture : Me and Giza Pyramids

When we reached the hotel it was bit late, Before I went to the room, I met Dave Prior (Immediate past chair of PMI IT & Telecom Sig), It was so exiting to see him as we have been knowing each other through articles , blogs and emails for quite a time. He was amazing.
At night Emad ( the host of P2P and the CEO of Brisk Consulting wanted to meet all the speakers in order to give an overview of the conference. Except me all the others were from eitther USA or Canada. After the meeting , others proceeded to the Dinner but I was tired and full with late lunch so I went to bed.

Tuesday
The conference started officially on 3rd Tuesday with Keynote speeches by some of the ministers of Egypt Government and some industry experts. It was quite interesting to see how Egypt government has understood the importance of proper project management expertise in the region. The afternoon sessions were more focused on PMOs and Maturity of PMOs in General.
There we met Ricardo Viana Vargas (PMI Board of Directors Chair) Dave introduced me to him and gave him a reminder about one of my articles which they have referred before with regard to Agile and PMBOK. Jesse who was with us didn’t forget to tease me about the PMI April issue and me being the cover girl ( oh I'm blushed ) in front of him. And we had a little chat. I was so impressed to hear how open he is to Agile and Scrum while heading PMI, It was very impressive. I thought to bring this up in the Colombo chapter discussion next time.
Dave proposed that we should grab a coffee and do a practice run of my first presentation with himself and Jim as I was little nervous about the presentations among all the very experienced speakers.. But they were quite happy with the practice run so their comments gave me lots of confidence before presenting to the audience.
Dave gave me more info on Transition of the PM in Agile which he thought would be the questions from the Audience.

We started the Scrum sessions by 4th November. This segment was conducted by James Cundiff- Jim( Managing Director Scrum Alliance, Dave Prior, Jesse Fewell, Bob Tarne and me. It was an amazing experience to work with such people and we were a great Cross functional Scrum team. we conducted most the sessions with some discussions ,questions and answers.

The Amazing thing in this sessions were that, we , speakers had arguments about certain concepts openly in front of the audience. It was never a stiff speeches we see in normal conferences. As a team we turned it around. As a team we made it very agile , open and direct. Jim mentioned his opinion on daily scrum which Dave and Myself disagreed openly, Jesse had a conflicting idea about initiating an organization with Scrum against my opinion. We all had certain arguments on how to position a PM in this transition .. Very upfront.. This was amazing and most the audience gave lots of encouraging comments about the way we handled it . There you go....They got the idea of Scrum not being a very prescriptive method.. In RUP you never argue on how to write a use case or a PFD.. So that was an eye opening for the audience. Thanks Jim for starting this conversations.

Jim and Dave opened the session by explaining the basics of scrum. they got some volunteers from the audience to play a game for the attendees to understand the effectiveness of initial one time planning Vs Iterative planning. Then the next session was mine. I had to present the Organizations moving from waterfall to Agile , the challenges they may face in this transition. I touched main areas in the presentation such as Why Moving to Agile, (there I had a great story to convince the audience with real pictures to support the story)Which Agile methods to be selected , In Which layer of the Organization to be aproached first, (there I explained the core cultures of organistions and how to spot the right layer based on the specific culture ) then the most important part, how to handle the people in this transition, such as customer, Technical staff, Management and specially the project manager. Phew !!! You know what.. I got a blue screen.. Why MEEEEE!!!!!!!!!!!! But somehow I managed to not to click "my Panic button". so all were ok and I got some good comments about the presentation.
lessons Leaned : Have story cards in your hand , when ever you go to a presentation.. If your computer make troubles, still you can continue without an issue.

After the coffee break, Dave presented about "Reluctant Agilest" quite an interesting presentation about a story how painful agile can be when not embraced in right way.
There after, Jesse took over and he explained "Agile PMO" how agile a PMO could be. Very informative presentation on that aspect and he showed his maturity in managing PMO through out the presentation with live examples.
Then the Audience was lesser for the second session after the lunch break and Bobs presentation was to address the knowledge management for Agile projects. Im sure which has been a very interesting presentation , But I missed it as I went out of the room to get ready for my next presentation on the same day which is Outsourced Project management and challenges in Agile.
I think that was the best presentation I ever made in my life. It all came from my heart as this is what I have been doing for past 12 years. I discussed about outsourcing issues openly in 5 key areas and how we have used Agile to overcome these issues in my current company. Which was the presentation that I have got most the positive feedback so far. ( Most the delegates commented to me at the next day coffee break that they have never known Sri Lanka as such a software offshore destination.. Hmm I was happy..)We closed the day with my presentation.

We had an awesome night that day .. With all the speakers and some of the other people , we had lots of fun. The night was too long .. Me and Jesse who had to take the next day morning sessions were half dead when we reached the hotel around early morning the next day.

3rd day started with Jesse’s presentation on Agile vs PMBOK, which audience had many questions which they needed to clarify. Again I missed most the parts of this presentation as next I had to present my last presentation on Effective communication in Agile. I explained the difference between agile communication and the traditional project communication. In the same time I got some real project examples to show how Agile communication can go wrong with such informal methods. According the audience they had a good presentation from me.. But to be honest I think I was not with my full energy for this presentation compared to others. The next session was a very interesting one by Bob about the user stories and the last session was by Jesse about the Agile contracts. There he explained how fix price works in Agile contracts which is the case in most the real world projects. Interesting !!!

We had the round table discussion afterwards, all 5 of us together.. it was very nice...

Picture : closing dicussion by all the Agile speakers (from left to righit ) Jesse Fewell, PMP, CST, Dave Prior (CST, PMP, Immediate past chair of PMI IT & Telecom Sig ), me, Bob Tarne PMP and James Cundiff( Managing Director Scrum Alliance )

At night some of the speakers went for a dinner in Nile cruise while me , Dave, Jim, Andrew and Bob conducted a retrospective about the Agile stream of the conference. It was time well spent.
After the retrospective again we had a late night.. Not that late as previous night as Jim had to catch his flight back home , Emad and Nora (the hosts ) invited us to taste a real Egyptian Dinner at a real nice exotic Egyptian restaurant.. It was really a nice experience..
After that we said Good bye to each other.. It was such a sad thing to leave such wonderful people whom we worked together for few days as a team.
My flight is today evening.. Only Dave and myself were left in the hotel with the hosts as all the other speakers have left. We both had a small breakfast meeting at Marriot to discuss what we can do in the future together, specialy my interest to become a CST and upcomming PM conference in colombo which will be really good.

Are you a good Scrum master ?

Scrum master is a servants leader .. We say this all the time.. So Scrum masters .. how good you rate yourself as a leader is scrum project. check out this matrix introduced by Bob Hartman (Agile Bob)

1. Listening – actively listening to what others are saying
2. Empathy – feeling the pain and thrills of others
3. Healing – helping others after they have been hurt
4. Awareness – understanding the big picture
5. Persuasion – persuading others to do what is right
6. Conceptualization – helping the team understand
7. Foresight – seeing problems before they arise
8. Stewardship – helping the team use resources most effectively
9. Commitment to growth of others – helping others improve
10. Building community – helping the team become more than a
group of individuals

Microsoft Dynamics AX team

We have openings for a Microsoft Dynamics AX consultant and few AX developers from Sri Lanka or India, if anyone.. Please send me the CV to twi@exilesoft.com

PMI Colombo chapter Open Forum Oct - 2009

The Guest Speech: Challenges to be faced when move from Waterfall to Agile.
Speaker: Mr. Finn Worm-Petersen, CEO Exilesoft
Date: 8th October 2009
Venue : Taj Samudra Hotel 5 PM – 7 PM
RSVP: Please call Vajira on 0714353787 to reserve your seat (None members fee Rs. 500)

You can earn 3 PDUs under Category 4 by participating the event.

World is bigger.. Its bigger than SCRUM..

Did you hear about the facebook addicted criminals story on Sheryl's keynote speech at Advertising Week! (She is the COO of Facebook. She explained a true story of a criminal entering to a house, seen facebook in the computer. Logged in to it but didn’t log out ! :) He must be a Facebook addict like me.
Ok where did this Facebook story came up.. Ok.. Now I can remember , I saw someone’s FB status said today that treat every problem as an opportunity. I believe in it ! I have been always whining about my home only weekends.. But now Ive kept my whining aside and learned to use it as an opportunity to spend little time on reading..
Never mind all that.. Lets get in to the point.. Scrum and Kanban.. I see some heated up discussions going on….!. Its sad that some people believe that scrum is a god given solution to all the problems.. Scrum is great and it works in the right context! But not in all the contexts. I saw an article published by Crisp.se, they ask what do you think is the best tool … Fork or spoon? Good example. I know It’s a senseless question. So if you ask me again what’s best Scrum or Kanban I would say it’s a senseless question.(But I admit that I have not used Kanban in practice) But if you ask what’s much more prescriptive, definitely I can see that Scrum is more prescriptive than Kanban. However all the agile methods are much much less prescriptive than waterfall methods and that’s why those are mostly referred as light weighted methods. When the prescriptiveness is less in a tool, one should use more creativity and brain to make it work, but you get less constraints and high freedom.
Scrum works perfectly in product development.. But I can foresee its definitely going to be failed when you cannot plan proper sprints, when you can’t have that committed time for committed user stories. The best example is maintenance projects. How long you can commit to ? 1 month sprint ? 2 weeks sprint .. No.. most the time you cant go beyond 1 day I suppose.
In the article written by Henrik Kniberg, about how you can make scrum works with Kanban, he describes the adaptiveness and prescriptivenss of various methods beautifully. There he compares RUP , XP, SCRUM , KANBAN, and another Agile method called Do what ever :) ( which most of us are frequently used to :)) He rates the Prescriptive to adaptiveness scale of these methods as RUP (highest 120+ ) XP (13) Scrum (9) , Kanban (3) and Do what ever as 0 . As he says “RUP is pretty prescriptive – it has over 30 roles, over 20 activities, and over 70 artifacts, this may be one reason why RUP implementations end up being heavy weighted compared to Agile methods such as SCRUM and XP”

The main difference between XP and scrum is that , XP stress on how to do work such as test driven development and pair programming.. But Scrum doesn’t tell us about how we should do development. So scrum is definitely going to be more adaptive than XP.

Lets look at RUP and SCRUM now.. Most the time Im in firing line about Scrum as most my colleagues are coming from "sort of RUP" environment. I had an interesting discussion today with a PM friend from my PM network, he said RUP is like a dish with too much of salt and SCRUM is like a dish with too less salt. You will not eat both as it is.. there are so much you should take out when you are implementing RUP , same time you need to add bit more essence to SCRUM when you are implementing it in practical environment. (Read my previous post about SCRUM and test cases/use cases.)

Ok looking back to Kanban, Kanban also looks very attractive to a less process person like me LOL

The main differences Ive understood In Kanban compared to SCRUM is that;
1. Scrum tells you when to do planning , when to do the retrospective when to do the next sprint planning.. in Kanban you do as you see the requirement for it
2. In Scrum you are focused on delivering what you are committed to sprint, you do your best.. deliver what you can , next sprint you see how to improve, you measure this by velocity of a sprint, in Kanban you limit your Que in a workflow state. As an example you can say you can’t have more than 2 to do items in the item dashboard at any given time. But in Scrum you commit to user stories and you control the work to do by committed user stories.
My personal view is that Scrum is somewhat lean(But I know there are lots of arguments over this at the moment.) However Kanban is much more Lean than Scrum for sure.
Kanban don't stress about time boxing as far as Scrum revolves around it , Kanban cares about lead time.
To me as I read Kanban can be scaled much easier for multiple teams. But I need to experiment more on that.

I think this is one reason why I think Kanban can be a help in maintenance type of projects when Scrum becomes challenging.. However today there are lots of mix marriages.. Mix when you want to get the best out of them.. I had a waterfall team who had 15 min stand up meeting every morning.. Im going to have scrum teams who will use use- cases for user stories from RUP process. Now I don’t mind combining Kanban with Scrum when its needed.. ! All what matters is the success of the project. All these are tools for you to use them right to get in there.

Following diagram is taken from http://www.infoq.com/articles/hiranabe-lean-agile-kanban

International Project Managers day 2009.

International Project Managers day is scheduled for 5th November. ( Cool :) Like Moms day , Fathers day, valentine’s day. … PMs who are always in firing line also should have a day for them I believe :)
There is a very good webcast program which you can join on 4th and 5th November.. the great project management professionals such as Gregory Balestrero - President and CEO, Project Management Institute are scheduled to give speeches on this.
You can find more info on this at http://www.iil.com/ipmday2009/webcast.asp

Online Exam for Certified Scrum Master

the Scrum Alliance Board of Directors (Board) has decided to move forward with the launch of the online Certified ScrumMaster (CSM) exam on October 1. For more details Visit Scrum Alliance web page.

Scrum and Documentation.(use cases/ test cases). ?

I know I was suppose to write few posts totally focused on practical aspects of user stories. But I thought to write this post first, because last week I had an interesting discussion at office which could be really useful to other agile practitioners as well.
We were talking further about agile testing. Especially with Scrum. We do have a separate well focused QA team managed by an experienced QA lead. In our model, the QA department is independent from any projects and they directly report to the Project Director. So how does this model work with SCRUM? I find sometimes its bit contradicting with concepts. We know Scrum has cross functional teams and each developer is responsible about their Quality. However, there can be testers too working in scrum team full time, they will be team members within the scrum team and coordinate with the scrum master. But if the QA department runs separately how do we do that? We had 2 options. Running 2 scrum teams for same project, you can call it scale up scrum, one for QA and one for Development, then have scrum of scrum everyday to synchronize with 2 teams. The 2nd option was for QA team to give permanent QA resources to each scrum team and they will apart from the QA department. In that case it would be an organizational change as well as we will be losing the concept of the power of an independent QA team who certify the delivery before delivering to the end customer.We thought of maintaining the same independent QA team and still to run Scrum ( if you don’t like me calling scrum for this method.. sure .. you can call it something different.:). ) But then the biggest problem is that how the QA team members get the knowledge of the product? Because, in a Scrum team the documentation is very less. We don’t create lengthy specifications and pass them over the wall. Then how does my independent QA team get this knowledge from the development team who participate the Product backlog planning meetings and sprint planning meetings.The following are the points we discussed;
1. One QA member of the QA dept participate the product backlog meetings as well as sprint planning meetings.
At the product backlog planning meeting, the assigned QA member with the team will decide which user stories will need use cases. Further, we discuss about using some very light weighted use case only when required. You can find a good article on some light weighted use cases for Scrum in http://breathingtech.com/2009/writing-use-cases-for-agile-scrum-projects/

2. Once the product backlog planning is over , the QA team member who participated the product backlog meeting will educate the QA dept head about the scope of work in QA dept with regard to the project.
3. In the sprint planning meeting, when the team decides of which vertical to be focused on, the team will create those use cases only for the specific selected vertical for the particular sprint. For that sprint, the sprint should have tasks and enough space to complete the use cases. In this case sometimes we may have to go away from our usual 2 weeks sprints to 4 weeks sprint.

4. Once the team finishes the required use cases, they will sign in to development tasks. The QA will have tasks to create the test cases during the sprint. So now we have test cases too.
5. Once the iteration is done (At the end of the sprint), the development team delver the shippable product increment to the QA department. , One of the tradeoffs is that this will delay the customers immediate delivery at the end of the iteration by few days.. But as a company, we need to assure the quality of what we deliver to the customer by our focused QA unit. I think this is better , so in this way, customers product quality is basically assured 2 times. Which enable us to deliver a very good quality product to the customer.

6. This QA dept quality checking also can be time boxed to few days as there cannot be such a bottleneck for the product owner to test the vertical.

I can see we can eliminate few practical problems in Scrum model by using few extra steps. Because we all may not have that “Luxury of right context” for scrum in real world business.

Scrum... never ending questions !! “yeah It’s a framework :)

Someone had an argument with me about something I mentioned about scrum at some place.. ( Ok I would call it a “discussion” :-)) I love when someone challenges me on something what I talk about..!
Ok the “conversation” I had is this;
I said the scrum project starts only when the Product backlog is ready !! Im sure Im correct.. Ken Scheber said it better way than me.. (Obviously he should! )…“The minimum plan necessary to start a Scrum project consists of a vision and a Product Backlog “sounds clear..!
The point is that, in business we position ourselves as a total solution provider in software. Specially in Outsourcing business where we are in to , the product owner becomes a role from the customer’s business manager or a product manager. Because the total understanding and the product vision is very difficult to be transferred to someone outside the geography boundaries to a person who doesn’t have much understanding about the business climate where the product will be marketed at.
We all know that Product owner is never a part of scrum team. Ok then, do we leave the product owner to create the product backlog in that case? The product owner has enough time and knowledge to do the groundwork which is required to come up with the product backlog? Don’t we have to do it for him?
May be I had a too quick and confusing answer to him as always J
I thought this would help many readers who are bit confused about this pre stage of scrum. The point is Yes ! Scrum doesn’t stop the team getting involved with doing necessary mind mapping work, wire frames , usecases and other background work to help the product owner to get the user stories of the product done.. But those will not happen within the scrum project. In scrum project everything is time boxed. We have a planning meetings within defined time , we have tasks to be executed ( sprint) within defined time and we have a scrum day within a defined time. So we know exactly how time is taken for these specific user stories to be developed in scrum. However, the pre tasks such as helping the product owner to get the user stories ready can be done with the team involvement, and then the question is actually “when the team can get involved with the process”, It can be anywhere but the latest is the product backlog planning meeting . Then the question comes.. How long the team need to come up with the user stories? I don’t think any Scrum guru can give an answer to that..( I learned during my CSM that there is an easy answer for all the difficult questions in scrum – the answer is “it depends”)
Actually the time needs to take to come up with user stories really depend on the knowledge of the product, availability of other stakeholders to work with product owner, business environment, and many other factors. I don’t think the time you spend to come up with Product A for 100 user stories will have any relationship to a time you need to come up with Product B 100 user stories. Otherwise there could be already set benchmarks in the industry for time to create user stories. Which is never the case.
Another area which I find bit confusing is that, in our waterfall projects we do lots of micro management. We need to track time based on various functions such as how much time we spent on testing , how much time we spent on coding, how many bugs we got etc. But in a scrum project, Ive never seen or have come across such micro management or related data as everything is measured based on verticals. As an example , coz in a scrum project testing and many other cross functional work happens within the user story.. I was thinking a lot about that.. while scrolling up and down through sprint backlogs. As I see….. ok if you want to find how many hours you have signed in to testing related tasks, you can really get in out of the sprint backlog. So there you go.
But again, in a scrum project what’s more important? Achieving the product vision and delivering the verticals within time boxes or work with past data of project X to determine project Y ? Estimation based on historical data is totally out of scrum. But true enough when we are dealing with real business world, we cannot assume that all the customers will be thinking “Scrum”.. So we may have to collect some data too based on various functions..if all of sudden the PO comes and say.. you know your guys make too many bugs and due to that they couldn’t get the right velocity or guy X makes too many bugs.. I know all scrum practitioners may say NO.... But I see the fact!. You need to do bit of “SMA “ in real world :D

User stories - Do they need a format ?

Every person whom I meet teaches me how much I don’t know about some subject. Either its about the world, history, culture, religion, different industries… whatever it is…This happens to me all the time when travelling. I have some luck to have good company most the time while travelling or in transit. Those strangers ended up being my “friends” frequently.

This time when I was travelling from Frankfurt to Doha, Some stranger fell in to conversation with me after seen my notebook bag ( I think I have mentioned about this notebook bag before in this blog J ) He assumed that I work for an IT company and he is an Agile management consultant based in Denmark and travelling to Doha for some assignment. You can imagine now.. a conversation in a long flight extended by 1 hour delay J

It was very interesting to know about various experiences we both had with Scrum and he was quite used to many other agile methods which I have never been exposed to before. However we both agreed that Scrum is the most popular Agile (According to him.. “The well marketed and money making Agile”) right now.

Talking about various experiences I asked his experience about user stories. This was some challenging area in Scrum projects. Getting the user stories right…

I always believed its better to have the standard for user stories “ As a “, “I need to “ “So that I can”.. In this way the requirements become much clearer to everyone and we may not miss the users what their expectations etc.. But he disagreed. I was surprised, but he had a valid argument on this. Example: As a Job applicant I want to post my CV to the job portal so that the prospective employers can view my CV in PDF format”

His argument was that its always difficult to stick with real users in user stories. As an example; you want to have date widgets in an application, so that do you write “as a designer I want to use the list of widgets so that “…….. ??? Where is the real user in this user story? ? I couldn’t agree less. Because I just completed a project initiation where there were many many user stories which I couldn’t think of mapping to my standard template originally but I had to do it by force with tweaking them by using developers, designers , architects as types of users which may not be the best case.. He also had the same experience .. One of his initial product backlogs 80% of the time it has been “ As a product owner “ which doesn’t make any sense…J

But then.. Million dollar question.. Why Mike Cohn standardized that user stories in a standard way? Didn’t he see this problem? I don’t think so .. Need much more thinking and reading on this.. may be some times not using standards would be better than using standards if they are not meaningful.. I will definitely do a follow-up post on this..

Anyway bottom line out of scrum is that speak to anyone who try to make a conversation with you…never know what they will come up with J

Yeah Im not a person who can live with open ended questions.. So Im chasing answers:

28th June..

Follow up today : I purchased the book from Amazon "User Stories Applied: For Agile Software Development " by Mike Cohn

29th June

I found this article :

Missing Dimention of user stories : Interesting thoughts:

Another Scrum project initiation

Very interesting project to work with some cool robots :-) and nice people. and more than anything the office is located in a beautiful area..I love this trees houses, plants, flowers..and seen 2 apple trees today while walking to find the train station . its a picture book enviorenment outside :-) and I love them all... Ok..I had a good start today. The customer is located in Norway. Working with other nationalities for some challenging tasks specially working in the project initiation stage where you need to understand the project context and stakeholders clearly and come up with the best customized model for the right context and drive everyone towards it.. That fascinates me all the time. This time it was not that hard as Ive experienced with some projects before.. Most the facts were straight.. When I listened to all the discussions going around I spotted some mostly used keywords by the people;
- Working with Verticals
- Collaborative team- Prioritization- Incremental product deliveries- fear for the risks with offshore model- Difficulties of limiting the scope or defining at once- The visibility of the value out of work.
Further I observed there seems high degree of commitment and enthusiasm by the customer team for the project. So now that its clear I wouldn’t go for any waterfall project initiation in this context. You can see that very clearly. We agreed on Agile (ok - scrum) due to many reasons.
Working with Offshore model is never like working with collocated teams. Offshore itself is very challenging when it comes to Software projects. The biggest problem you experience in offshore model is that isolation after initial study at customer location which leads to most the project failures. The old saying “Out of sight is out of mind” is proven again and again in most the offshore projects. Therefore it’s a key factor that we need to use a work model which doesn’t give that chance of getting isolated though you are in a different geographical location. Scrum facilitates that.
IBM scrum community guide for scrum in distributed team context gives lots of insights about distributed teams using scrum even with teams where there is no overlapping time zones. But I don’t think that’s a good idea anyway unless one team is willing to scarifies their off time – It’s a different discussion anyway.. Point here is that you can see many distributed teams around the world moving towards agile due to this “Out of sight” risk factor.
Ok coming back to my project, the team model, either its going to be 2 scrum teams in 2 locations and working for verticals and then doing scrum of scrums or whether both country resources working in one team with one scrum master and product owner. Both the options its important that you share one product backlog and commit to stories instead having 2 product backlogs.
I have chosen the 2nd option by keeping provision to go for the 1st option when the teams start to grow. We can scale up the model when there were more team members are added to the teams.
Identifying the product owner and the scrum master is another important thing as you identify the Project manager in waterfall project initiation. I always agree with scrum experts that Product owner is the most difficult role to be played in a scrum team.
Product owner is a person who needs a mix of skills, he needs to have a good business vision, Project skills and he is the person who has the final “say” of the product in a scrum team by coordinating with many other stakeholders. Compared with traditional work we did before this is like Scrum team is transferring the risks of requirements outside the team to the Product owner (Yes its Risk transferring up to an extend I should say )
In this project I managed to spot a Product owner after our initial discussions and thank god he agreed to play the role. ! Im so happy about that because I saw that clear idea about what they need is mostly lies with him. So his main tasks would be now to create themes, assigned values with other stakeholders, prioritize them.. After that we will be discussing about his release plan and then set the product backlog accordingly.
Identifying scrum master – in this team model should he be in Norway or in SrI Lanka. Looking at the current context we decided that the scrum master should come from Norway team. Which is a good decision for the model 2 right now. Further he has experience using scrum so it will be a good choice. I have 4 more days to go.. Not full days.. its challenging to do the rest of the tasks left to complete during rest of the days.. I need to structure my time well to prioritize on what I have to do. Stakeholder reporting and training team on scrum values and disciplines is another vital task requested to do at the initiation. Need to look at the risk analysis too. So I have few busy but “my kind of work” ahead :-)

Will Scrum scare away the PM .. I say BIG NO

Recent past this has been a very painful discussion in many organizations moving towards Agile.. What are we to do with our PM? Is he/she going to be a Product Owner, Scrum Master or will work as the developers of the team with his skills of development , testing etc. ? All that is fine.. But don’t forget about the Planning, Leadership, Risk Management and Project knowledge what your PM has gained over the years which is really helpful even in a scrum team for a medium to large scale projects. I understand there is no logic in converting PM to Scrum Master unless he understands and capable of playing this “servant based leadership” (they call it ) role.
Look at the following Scenario what we need to do when following a scrum project from top to bottom,

Product Vision -Themes -Values -Roadmap -Release plan -User stories -Product backlog - Sprint Backlog - Daily Scrum

Most the early stage work is the main responsibility of the product owner, however when you look at making release plans based on business values, budgets, stakeholder requirements, PO needs lots of support from the team as well as support from an experienced project manager would be invaluable. PM comes with lots of experience in foreseen risks, keeping team together with good spirit, protecting team from outside disturbances, being visionary about the project and specially some instincts about team skills J , So in that case I think a PM skills can be used in many ways as a very important role for scrum teams specially if there are many scrum teams involved in a project. One way to position him is to be outside of the team, acting a coaching role to help the PO in various scenarios throughout the project. But if the PM can be converted to a good scrum master who will serve this "Servant based leadership" the value he or she can provide is really good when compare with a techie who has no much experience of looking at the project perspectives becoming a scrum master.. I think its all about a mentality change which needs to play this new role by using your valuable skills. There are quite lot of opportunities for a skilled PM in agile environment either outside the team as a coach to work with PO or inside the team as a Scrum master.

WOW !!! is Scrum Alliance is all about money ???

I was thinking of upgrading my Scrum master status to Scrum Practitioner and I did the case study which was provided to gain the status., Following is the email I receieved from Scrum alliance today after inspecting the case study...

Hi Thushara,Congratulations! Your application has been approved. The next step is to submit payment of $250 to complete the process. You can do so by clicking on the link below.

http://www.regonline.com/csp_applfee2009



Once you've submitted payment your profile should be updated within one week. Your SA profile will show your new CSP certification status and your certification will be effective for a duration of 2 years. If you have any questions regarding your profile, please direct them to @scrumalliance.org.


Feel free to contact me if you have questions.



Warm Regards,

Scrum Alliance Certification Administrator


I think when you think "Agile " this fee is way out :-)
And further if you are interested to get CST , in SL money you got to pay Rs 80K + and again this CSP validity is only for 2 years. Im thinking whether its worth to upgrade to CSP or not now. Becuase I have to maintain many professional titles from various professional bodies and the anual charges to maintain them is already too much.. :-) and I rarely use the titles.. unless the rule says its a must :-)