Monday, September 20, 2010

SharePoint Saturday LA – great event

A second SharePoint Saturday Event in California took place in LA last Saturday at the Hilton LAX. The organizing committee chair Karuana Gatimu and co-chair Christian Buckley, once again put a great community conference. Owen Allen did a very insightful keynote on the transition of SharePoint to a business management platform. Needless to say I loved to hear him talk about ACM and CM utilizing SharePoint as a solution platform.

The sessions were a mix of repeats from SharePoint Saturday East Bay and local speakers, covering a variety SharePoint topics. I did once again my talk on when and how to use SharePoint and Silverlight, with excellent attendance and great feedback.  For those that joined the session follow the links below to download the slide deck and other resources.

Client Object Model on Channel 9

Using the Silverlight Object Model

Saturday, September 11, 2010

SharePoint Saturday East Bay – Recap

Another great SharePoint Saturday Event  in San Ramon. The organizers Christian Buckley, Michael Noel, the sponsors, and the volunteers did an excellent job in providing a top notch facilities and amenities for the event. Global 360 was a gold sponsor of the event.

Lots of great sessions on SharePoint virtualization, search, governance and other hot SharePoint topics. I was really thrilled to do a new session on when and how to use SharePoint and Silverlight. For those that attended the session follow the links below to download the slide deck and other resources.

Client Object Model on Channel 9

Using the Silverlight Object Model

Friday, September 03, 2010

Agile Tips: The End Game

Making short iterations work is hard. First the team has to find the right amount of work and commit, only to be confronted with reality and find out that the estimates are not what they meant them to be.

In the first days of the iteration (T-8) the top priority stories get tackled, and somewhere in the middle of the iteration (T-5) the team has a pretty good feel, of which stories have a good chance to get accepted, and which may fall off the iteration or get split.

This last part of the iteration is what our team calls the End Game. The End Game starts 3-4 days (T-3) before the end of the (2 weeks) iteration. This is when we start deciding, which stories can be accepted, which  may be split, and which may be moved to the next iteration. The rule of thumb we adopted is that once we enter the End Game, we do not take new stories if there are other stories in the works that have higher chances of acceptance.


This simple rule helps the team concentrate on completing top priority stories and the associated bugs first and then move onto new work. We found that this leads to a much better outcome rather than have many stories open at once and than struggle to split them or move them to the next iteration.

Another effect of adopting the End Game rule is that it raises the team awareness of what it takes to complete the stories with highest chance for acceptance. This is when team members that have completed and accepted their assigned stories, start asking the question: “How can I help other stories so they get accepted?”.

Tasks get reshuffled, pairs form to tackle difficult tasks, conversations with the product owner take place to set priorities. Work gets done-done.