jump to navigation

Notes on Agile Product Ownership in a Nutshell March 9, 2015

Posted by willhlaw in Administrivia, Productivity.
Tags: ,
add a comment


Above is an illustration from the video ‘Agile Product Ownership in a Nutshell‘ that uses the RSA animation technique. Below are the notes highlighting key points made during the video as well as some other points drawn from additional resources. This post will be a good read for Product Owners, both new and experienced, as well as any team member on an Agile Scrum team that wants to revisit the basic principles and possibly realign their team.

Roles in Scrum
PO – Product Owner carries the vision, says no or yes to customer requests, prioritizes, and responsible for building the right thing.
SM – Scrum Master is the coach, responsible for building it fast and fast feedback cycles with the users.
Other Roles
TL – Technical Lead is responsible for building the thing right, talks closely with customers and other teams, but still encourages self organization.
CPO – Chief Product Owner organizes multiple POs and interdependencies.
Development Manager hires, mentors engineers, creates culture, and knows when to step in and lead discussion on branching strategy or versioning [1]
Key Points
Product backlog becomes Team backlog when working on multiple products (new products, old products, O&M, etc)
Value = knowledge value + customer value.
Knowledge value is gained early to reduce risk. Knowledge user stories are UI mock ups, trade study, spikes, prototypes, etc.
Stories have an estimate for effort & value so priority = value / effort. This should make it easier for PO to prioritize Team backlog.
Velocity goes down overtime due to technical debt, architecture decisions, getting behind on automated testing. It is the team’s job to correct. However, how is this investment effort tracked? This question is asked and a lot of the sources below were found here.
  1. Be transparent by explaining benefits of paying down technical debt so that PO can prioritize. [4]
  2. Have a separate Improvement backlog that is internal that is adds a tax to each sprint (e.g. 10-20% of velocity). [5] [6]
  3. Do not obsess over it, basically just pick one and fix the broken stuff already [7]. Also, consider adding to the definition of done (DoD) that the work is done only if it does not add any technical debt.
Charts [2]
Time vs customer value curve = knowledge value, customer value focus, trim the tail
Time vs delivered stories
– fixed scope
– fixed time
– fixed scope and time -> no, let’s decrease scope (b/c can always extend time and not the other way around)
Reasons for Scrum:
– team motivation (not overworked, pressure from above, lack of input or control of march)
– deliver value in sweet spot of the triple constraints (time, cost, quality) Venn diagram
– more accurate predictions and expectation management
– standard metrics to evaluate team improvement and tech choices
Points measure effort [3]
Effort should translate to time, and is influenced by uncertainty and complexity.
  1. How much effort to get to that building? Answer for runner and cripple is one.
  2. How much effort to get to farther away bldg? Answer for both is two, since it looks twice as far.
  3. How much effort to get to farther away bldg where there is a chasm of lava and a small walkway? Answer for both finally agree that it is a 4, since they will have to be extra careful and may drastically slow their progress.
  4. How much effort to get to close bldg while singing Gangnam Style? Answer for both finally agree that it is still a 1, as the extra complexity doesn’t really have an effect on the effort that causes a slowdown.
[1] Development managers vs scrum masters, Dan Radigan at Atlasian, https://www.atlassian.com/agile/effective-management-across-agile
[2] Agile Product Ownership in a Nutshell, Henrik Kniberg, Youtube video – https://www.youtube.com/watch?v=502ILHjX9EE, Transcription – http://blog.crisp.se/2012/10/25/henrikkniberg/agile-product-ownership-in-a-nutshell
[3] Story Points Are Still About Effort, Mike Cohn at Mountain Goat Software, http://www.mountaingoatsoftware.com/blog/story-points-are-still-about-effort
[4] How to translate “business value” of things that are technically important, Matthias Marschall at Agile Web Development & Operations, http://www.agileweboperations.com/how-to-translate-business-value-of-things-that-are-technically-important
[5] Effective Steps to reduce technical debt: An agile approach, Bastian Buch at Codovation, http://www.codovation.com/2012/06/effective-steps-to-reduce-technical-debt-an-agile-approach/
[6] Scrum Strategy – The Dev Team Improvement Backlog, Professional Scrum Trainer at Scrum Crazy, http://www.scrumcrazy.com/Scrum+Strategy+-+The+Dev+Team+Improvement+Backlog
[7] Do agile right – Delivery – Technical Debt, Atlassian, http://www.scrumcrazy.com/Scrum+Strategy+-+The+Dev+Team+Improvement+Backlog

A discussion on rating and finding dishes to improve your restaurant experience September 3, 2012

Posted by willhlaw in Administrivia, API, Food.
Tags: ,
add a comment

Photo from http://www.spain-recipes.com/spanish_tapas.html



Finding the best dish.

Last night, I was with some friends at a greek tapas restaurant in Washington, DC, Cava Mezze. The menu has several small plate items and everything looked delicious. We had eaten at another Cava restaurant at least once and forgot what we had ordered and what was good. That is when I wished there was an app I could pull up on my phone to see what our friends thought of particular menu items. One did not exist, but we all thought at the table how useful that would be. I had heard of startup companies starting to digitize restaurant menus so that I knew the dishes would soon be available, if not already, as APIs. We then ideated about a dozen ways we could build an app that would be useful for finding recommendations on specific menu items and dishes as well as incentivizing users to rate the food they just ate.

Here is a summary of my morning market research into the possibilities of aggregating menu information or using an app that you can quickly discover how good a particular dish is at a nearby restaurant.

I started at the programmableweb and opened up every single “food” API in a tab that mentioned food data, dish, or menu. I later looked at popular Q&A site Quora.

all menus – Has a sophisticated restaurant and menu api that offers hundreds of thousands of restaurants and you can search menus by city.

All Menus appears to be very developer friendly and even offers an interactive documentation api site. Documentation is also enhanced by Mashery and interestingly, their support contact has a grubhub address. Perhaps because their search results has buttons to online ordering that point to GrubHub.

chownow – Digitizes restaurant menus to offer mobile and Facebook ordering.

Chow Now has an API that is private so you have to contact them for access and documentation.

food genius – A Chicago startup that started out as a “netflix for foodies” but ended up pivoting to deliver data to the restaurant industry. They get their data from other parts of the web, particularly grubhub. Checkout this video where they use their API to find the best curry in Chicago. They are involved with conferences and other food innovators at the food+technology blog site. This is where I learned that there is a lot of activity in this arena.

Food Genius encourages developers to use their API to create consumer apps and to start, they have created a website, foodgenero.us which gather’s people’s tastes on dishes and also donates to Feeding America to end hunger.

Captured from http://foodgenero.us/

Food Genius is very developer friendly and they offer examples in python, node.js, and php. Nice work.

food spotting – This is the app that we were pretty much thinking of last night. It provides a social way to discover a dish that you want and provides a pretty easy way to review dishes. They have even gamified it through a concept called Guides that individuals can create, almost like songlists, and even offer badges for others to win if they “spot” enough of the foods on the guide. I never realized finding, eating, rating food could be loved so much.

Food Spotting’s API is language agnostic, Restful and seemingly developer friendly.

grub hub – GrubHub appears to be the premier website and app for ordering food online. GrubHub allows you to rate a restaurant with a star system but it also shows reviews from Yelp. The ordering for each menu item is detailed and they make it a point to tell you the delivery or pickup availability. GrubHub’s home page allows you to search a location and an optional keyword for restaurant name, food genre, or food type. The search results offer a list view and a map view.

Captured from home page http://www.grubhub.com

Grub Hub has little information on an API and according to the founder’s response on quora, their semi-API (I have no idea what that means) is Private and you have to contact them.

locu – This is an up and coming startup that is focused on offering restaurants easy ways to publish their menus online. I am not sure where they are getting their menu information. More information will be revealed most likely when they fully launch.

Locu has an API that is still in private or in early access mode and it used to be called menuplatform.com because that now redirects to lucu.com

open dining – Offers a platform for restaurants to create a digital menu and ordering system for us on mobiles and Facebook. This is a lot like chownow. Their API is developed and targeted towards ordering apps.

open menu – Openmenu.org and Openmenu.com wants to become the industry standard. There is a simple search (with no map) for a dish around a certain location.

Open Menu has a format specification for the restaurant and for their menus. Their APIs are fully developed, as it is the org’s main goal, and examples are provided only in php.

Captured from home page http://www.singleplatform.com/

single platform – This New York company looks like it has a very strong backing and claims to be the world’s largest provider of menu items. They seem to be concentrating on signing up Washington, DC businesses because on their homepage, they highlighted a local cafe that we love, Lost Dog Cafe. This link points to a w.singlepage.com URL but interestingly enough, Lost Dog Cafe also has a GrubHub menu. I bet that the Lost Dog owners were searching for an online solution and when they checked out SinglePlatform, the singlepage was automatically created.

Singe Platform has a private API that requires registration before you get any documentation so essentially no information is available.


Start using foodspotter and grubhub now. Follow getfoodgenius and locu. Watch the industry as the open and platform menu players grow. Use the apps and APIs and then see where the experience falls short and consider developing an app that fulfills that need. For instance, consider an app with augmented reality that shows the highly rated items as you point your phone’s camera at a restaurant’s menu to help you decide what to order.

Top 12 Ways to Being a Mensch (aka – a good professional) September 11, 2011

Posted by willhlaw in Administrivia.
Tags: ,
add a comment

Enchantment by Guy Kawasaki

Paraphrased from, http://www.openforum.com/idea-hub/topics/the-world/article/how-to-be-a-mensch-in-business-guy-kawasaki and taken from the author, Guy Kawasaki’s book, Enchanment: The Art of Changing Hearts, Minds, and Actions.

Mensch is a German word for “human being”, but its Yiddish connotation far exceeds this definition. If you are a mensch, you are honest, fair, kind, and transparent, no matter whom you’re dealing with and who will ever know what you did. Bruna Martinuzzi, author of The Leader as a Mensch: Become the Kind of Person Others Want To Follow, compiled a list of ten ways to achieve menschdom. Here is Guy’s summary of her insights:

  1. Always act with honesty.
  2. Treat people who have wronged you with civility.
  3. Fulfill your unkept promises from the past.
  4. Help someone who can be of absolutely no use to you.
  5. Suspend blame when something goes wrong and ask, “What can we learn?”
  6. Hire people who are as smart as or smarter than you and give them opportunities for growth.
  7. Don’t interrupt people; don’t dismiss their concerns offhand; don’t rush to give advice’ don’t change the subject. Allow people their moment.
  8. Do no harm in anything you undertake.
  9. Don’t be too quick to shoot down others’ ideas.
  10. Share your knowledge, expertise, and best practices with others.

Guy also adds two more ways to achieve menschdom:

  • Focus on goodwill. Mensches focus on goodwill – that is, positive actions that make the world a better place. People distrust those who focus on improving their own position and who denigrate others.
  • Give people the benefit of the doubt. People are good until proven bad, which is only proven after several bad experiences.

I have a looong way to become a Mensch, but I think these are excellent principals to live by and do business by.

FPWeb Hosting Badge July 8, 2010

Posted by willhlaw in Administrivia.


Tom Brauch and the nice guys over at FPWeb.net are hosting the sharejPoint.com website free of charge.  They do so because they feel that non-profit sites like sharejPoint that promote free, open source solutions are a great benefit for the SharePoint community. 

So the guys on the jPoint team have finally updated the master template to include the above banner, and I have also added the banner below to the jPoint blog page. 


Which banner do you like better? 

I have moved my blog because DisQus had no love for WSS October 13, 2009

Posted by willhlaw in Administrivia.

DisQus comments were not working in IE7 (worked fine in Firefox and Chrome) on my WSS site over at http://www.sharejPoint.com/willhlawblog so I decided to move my blog over to https://willhlaw.wordpress.com.  I even submitted a help ticket to DisQus.