"I think the biggest mistake we made in the last two years was betting to much on HTML5 instead of native." - Mark Zukerberg when asked about the biggest mistake he has made at FB.Watch the interview live on disrupt tv http://techcrunch.com/2012/09/11/watch-techcrunch-disrupt-sf-live-2/
Sorry, Just saw this blog now....
As we implemented Scrum we found ways to tweak the concept to get even more value and efficiency out of it.
Here are some blog posts I made at the time to explain:http://www.seanshadmand.com/2011/08/14/how-we-do-...http://www.seanshadmand.com/2011/08/03/team-city-...
To get to where we are there were three primary parts: 1. Get to a level of confidence and have running metrics on our output 2. Having confidence allows you to focus on completing tasks instead of fixing them. At this point we started making the time to develop, sync up, and deploy as short as we could. This was done by Making things as asyncrnous as we could. Avouding mid week or adhoc meeting becuase 1 person has a question 3. Making Short Cycle Scrum so that everything is borken up in tasks that are able to be produced and tested in less then a week. And with that, knowing that no "mistake" can be more than a week of "badness". This allows everyone to start making descisons fr themselves, the best they can, and then disucssing it in the beginning of next week.
With those aspects you can apply Scrum well to all parts of biz. Design, copy writing, marketing or development religiously make an effort for the following: - Have a metric to determine what success looks like across your mission - Make those metrics easily definable and brainless to re-apply - An ability to break up tasks into its atomic structure - Removing the need as much as possible, to "check-in" or "ask for guidance" in any way that holds up output
Sorry, Just saw this blog now.... As we implemented Scrum we found ways to tweak the concept to get even more value and efficiency out of it. Here are some blog posts I made at the time to explain:http://www.seanshadmand.com/2011/08/14/how-we-do-...http://www.seanshadmand.com/2011/08/03/team-city-... To get to where we are there were three primary parts: 1. Get to a level of confidence and have running metrics on our output 2. Having confidence allows you to focus on completing tasks instead of fixing them. At this point we started making the time to develop, sync up, and deploy as short as we could. This was done by Making things as asyncrnous as we could. Avouding mid week or adhoc meeting becuase 1 person has a question 3. Making Short Cycle Scrum so that everything is borken up in tasks that are able to be produced and tested in less then a week. And with that, knowing that no "mistake" can be more than a week of "badness". This allows everyone to start making descisons fr themselves, the best they can, and then disucssing it in the beginning of next week. With those aspects you can apply Scrum well to all parts of biz. Design, copy writing, marketing or development religiously make an effort for the following: - Have a metric to determine what success looks like across your mission - Make those metrics easily definable and brainless to re-apply - An ability to break up tasks into its atomic structure - Removing the need as much as possible, to "check-in" or "ask for guidance" in any way that holds up output Also, here are some free docs we read as we developed our process: "Scrum in Five Minutes" : http://cl.ly/221W3r3a0x1Y1b380R1A Google's Scrum tuning video: http://video.google.com/videoplay?docid=879521430... Fundimentals Library: http://scrumfoundation.com/library
