Typemock: Past, Present and Future
Eli Lopian of Typemock answers a few questions on Typemock origins and where Typemock is headed.
Tracking change and innovation in the enterprise software development community
Posted by Abel Avram on Jul 03, 2008 01:00 AM
In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum. He tells how Google started with no engineering management, then gradually introduced Scrum without spoiling the development culture formed over the years.
Google removed all low level engineering management back in 2001. They formed lots of small teams of 2-3 developers which constantly took the leadership of their team. They were responsible for what they were doing, including fixing bugs in production code without asking anyone about that. That created a special development culture in which everyone was feeling completely responsible for his contribution to the company and no one was expecting a boss to tell him what to do next. Later on, they started to gradually introduce Scrum step by step and forming organic management whose primary role was to support developers' activity and not supervise them. There are only two basic rules at Google: code reviews and every developer maintains a web page with information about his current work and his plans for the following 3 months.
The main problem Google was facing back in 2001 was missing the deadlines. As a reaction, they introduces backlogs and burn down charts. Then daily meetings. They were still missing dates. After a thorough investigations they discovered that a large number of features were work in progress. So, they started to minimize work in progress. Later they introduced iterations, and included testing tasks in the backlogs. Eventually they started creating release burn down charts.
The entire presentation is 1 hour and 8 minutes long. Jeff answers questions during the last 15 minutes of the presentation.
Gamma's Jazz platform's first implementation: Rational Team Concert (Trial Download)
Evolutionary Design through Agile Development Podcast
SCM Best Practices for Continuous Integration
The Agile Business Analyst: Skills and Techniques needed for Agile
Scaling Agile on large teams & Being Agile every day Tracks @ QCon SF Nov 19-21
Eli Lopian of Typemock answers a few questions on Typemock origins and where Typemock is headed.
Scott Ambler talks about actual data resulting from surveys made during 2006-2008, showing how Agile is perceived and implemented within organizations.
From QCon 2008, Daniel Moth presents on using Visual Studio 2008 and .NET 3.5 to create compelling rich Windows applications.
Joshua Kerievsky, founder of Industrial Logic, talks about Industrial Extreme Programming which extends XP by including practices dealing with management, customers and developers.
Amazon Web Services (AWS) Evangelist Jeff Barr discusses SimpleDB, S3, EC2, SQS, cloud computing, how different Amazon services interact, origins of AWS, AWS globalization and the March AWS outage.
Cloud services have helped bring virtualization to the forefront. Its full power however, also includes other benefits such as high availability, disaster recovery, and rapid provisioning.
John Lam talks about his path to dynamic languages, some of the problems of making IronRuby run fast, and how the DLR helps with implementing languages.
VMware Infrastructure 3: Advanced Technical Design Guide and Advanced Operations Guide provides a wealth of practical insights into setting up virtualization in todays corporate environments.
1 comment
Reply