Behavior-Driven Development: An Evolution in Software Design Behavior Driven Development (BDD) is not a revolution in software design, but rather an evolution in how we software engineers think about program design. In this article the author introduces Behavior-Driven Development, explore the rationale behind it, and introduce Open Source tools—some new, some familiar, that you can use to get you started. |
||
Three Levels of Leadership Agility New, in-depth research shows that people move through distinct stages or levels as they become agile leaders. At each new level, managers gain new capacities that make it more natural for them to lead in an agile manner. This article outlines three levels of leadership agility and shows how managers at each level of agility lead projects, lead teams, and engage in pivotal conversations. It ends with a few pointers about ways to assess and develop your own level of leadership agility. |
||
Challenging Why (Not If) Scrum Works Agile works. Early adopters, working largely by instinct, have seen good success. To go to the next level, instinct alone is not enough. As we face more complex and uncertain environments, as we face the need to scale to the enterprise, we need to apply intelligence and knowledge, guided by experience. Knowledge about why Scrum works. |
||
Agile2007 - Dave Thomas - I finally speak with Smalltalk Dave
Podcast
Dave Thomas aka "Smalltalk Dave" was kind enough to join Bob Payne for this podcast while the two of them were both attending Agile 2007. These podcasts are a great way to get the inside scoop to what many of the world's popular conference speakers really feel about the topics that matter most. |
||
Agile2007 - Josh Kerievsky - Scaling Training, e-Learning and Certification
Podcast
Bob Payne finally got a hold of Josh Kerievsky so the two could record one of our friendly discussion podcasts together. Bob and Josh discuss the benefits of e-Learning courses for software developers, and how his own companies provides these classes along with other certifications. |
||
Agile Survey Results: Widespread Adoption, Emphasis on Productivity and Quality This summer in 2006, the Agile Project Leadership Network (APLN) co-sponsored the 2nd Annual 'State of Agile Development' Survey. Almost 1,700 respondents from 71 countries shared their companies' experiences using of Agile methods and the challenges that they face with future adoption. Teams have begun to quantify the value that their projects have achieved and are steadily expanding the types of Agile practices and tools that they use. IT metrics are well-understood. Business metrics must also play a role, but few were included in the scope of this survey. |
||
Personal Agility for More Potent Agile Adoption In this article, the authors propose that the most effective teams—those that show a tremendous improvement in productivity and value to their organizations—have individual team members who take ownership, act responsibly, and are disciplined in recognizing and responding to change at a personal level. |
||
How to Be Persuasive Successfully persuading others to adopt your point of view is a matter of neither magic nor luck. It's a skill and like any skill, improvement takes know—how, opportunity, and practice. In this column, Naomi Karten offers pointers to help you strengthen your persuasion skills. |
||
Lean Anti-Patterns and What to Do About Them When attempting to adopt best practices we often can't see the forest for the trees. We can see what we are doing wrong, but how will that help us to see what to do right? In this article, we will discuss a few common Lean Anti-Patterns. Anti-Patterns are commonly recurring practices that are counter productive. We call them "Anti-Patterns" because these anti-patterns result from violating Lean principles. Lean principles form the basis for Scrum practices. Looking at how Lean Anti-Patterns violate lean principles gives us insight into how we need to modify our practices to be more effective. |
||
People-Driven Software Development Traditionally, we think about projects is in termsof scope, time, cost, quality, human resources, communication, and risk. Thisway of thinking mainly originated in industries other than software development.It fits software development projects poorly, because these projects are mainlyabout people's abilities. |
Pages
Upcoming Events
Sep 22 |
STARWEST Software Testing Conference in Anaheim & Online |
Oct 13 |
Agile + DevOps USA The Conference for Agile and DevOps Professionals |
Apr 27 |
STAREAST Software Testing Conference in Orlando & Online |