If some of the really hard core users who spend many hours trying to educate, work, create, collaborate and or play in SL were to spend a few hours with some of the key Linden Labs employees.. one on one..doing what they do..showing these talented Linden Lab people the pitfalls.. the needs, the it would be cool or useful if we could, just even how to sit down or put on a pair of shoes (Phillip did say it was difficult to do that). Then..and only then could they really come up with a viewer and platform that serves most people needs in a Fast Fun and Easy way.I have no idea how many Linden Lab employees use Second Life on a regular basis. Certainly very few of them are openly active members in Second Life communities. In any case, it made me wonder who is playing the customer role in Second Life agile teams.
The key to a successful Agile approach to software development is that the voice of the customer guides the entire process. Agile methodology builds software through a series of short iterations that are typically one to two weeks in length. At the start of each iteration, the person or acceptance team in the customer role sets the development priorities for the week and helps define the acceptance criteria that will be used to test whether the iteration's work is successful.
The Agile process breaks down if there aren't people on the acceptance team who have a deep, working knowledge of the end-user perspective. Although the resulting software will work well from the team's point of view, it may not be useful to the customer. A good analogy is a French cooking team trying to create a new dish for the Thai market. Although the resulting product will be delicious to the European palette, it may leave a bad taste in the mouths of the intended customer.
So I wonder who is playing that role on the Linden Lab Scrum teams. Any Lindens care to weigh in?