Why Agile Teams Fail – Erik Doernenburg
Agile methodologies such as eXtreme Programming and SCRUM are hot topics today — and they are also hot targets. When things go wrong on an agile project, it’s far too convenient to blame the methodology, and not the people charged with implementing it correctly. In this talk Erik discussed the most common reasons a team may fail when trying to execute a project using an agile methodology. He also covered how to learn from the mistakes of others, and avoid repeating new mistakes of your own. This talk is based on experiences Clinton Begin and Erik have had on projects at ThoughtWorks.
“The Clean Code Talks” – Inheritance, Polymorphism, & Testing
Is your code full of if statements? Switch statements? Do you have the same switch statement in various places? When you make changes do you find yourself making the same change to the same if/switch in several places? Did you ever forget one?
This talk will discuss approaches to using Object Oriented techniques to remove many of those conditionals. The result is cleaner, tighter, better designed code that’s easier to test, understand and maintain.
Speaker: Misko Hevery
“The clean code talks” – Unit Testing
The Secret Sauce for Improving your Scrum team
High performance depends on the self-organizing capability of teams. Understanding how this works and how to avoid destroying self-organization is a challenge. Until you understand complex adaptive systems and how Toyota works it is difficult to improve team velocity. Jeff will discuss three core topics:
1. Shock therapy as a strategy for booting up teams.
2. The Cosmic Stopping Problem, otherwise known as the choice uncertainty principle.
3. Punctuated equilibrium – how software systems evolve
Take advantage of these concepts and you may find a way to achieve the ultimate potential of a team. This session will be a “Deep Agile” presentation keying off topics presented to engineers at MIT.
Speaker: Jeff Sutherland
Dr. Jeff Sutherland is one of the co-creators of the Scrum software development process. He and Ken Schwaber invented Scrum in 1993. Since then he has worked with many software companies and IT organizations to extend and enhance this process.
Scrum et al.
Ken Schwaber co-developed the Agile process, Scrum. He is a founder of the Agile Alliance and Scrum Alliance, and signatory to the Agile Manifesto. Ken has been a software developer for over thirty years. He is an active advocate and evangelist for Agile processes.
ABSTRACT
Scrum is an amazingly simple process that causes many, many changes when it is implemented. This seminar presents the basic framework of Scrum and some of the implementation issues associated with it. Credits: Speaker:Ken Schwaber
Scrum Tuning
Adwords introduced a Scrum implementation at Google in small steps with remarkable success. As presented at the Agile 2006 conference this exemplifies a great way to start up Scrum teams. The inventor and Co-Creator of Scrum will use this approach in building the Google Scrum implementation to describe some of the subtle aspects of Scrum along with suggested next steps that can help in distributing and scaling Scrum in a “Googly way”. Credits: Speaker:Jeff Sutherland
Agile Excel Template
TDD using easy mock
TDD for Web UI using Selenium IDE
Test Driven Development (TDD) Video Tutorial
-
About
The author of this blog has been involved implementing J2EE solutions for years. This blog is an attempt to share the experience. The author is the founder of Online Travel Agency...
.
-
Blogroll
Categories
-
Books
-