Process

Articles

Simulation Games: A Way to Improve Communication in the Team

One of the hardest daily tasks developers, QA, ScrumMasters, and product owners encounter is effective communication with others. Sound implausible? According to many articles, research, and personal observations, the main cause of project failure is not technology or hardware, but inefficient communication stemming from lack of effective communication between team members, incomplete business analysis, imprecise requirements, and vaguely formulated business objectives.

Monika Konieczny's picture Monika Konieczny
Four Agile Tips to Eliminate Rework in Application Development

Your applications need to meet business needs, overcome complex processes, and provide instant results to customers. And, ideally, they’ll require minimal rework on your part. The first step to success is requirements definition. Here, Filip Szymanski offers some tips from agile methods that will improve your requirements—even if you haven’t otherwise adopted agile.

Filip Szymanski's picture Filip Szymanski
Adapting to Change in Your Agile Strategies

Len Whitmore writes on using agile practices for the development of software. In the ten years since the Agile Manifesto, the agile development domain evolved, as evidenced by such things as the six levels of planning: strategy, release, iteration, daily, and continuous, with strategy appearing to be the least evolved of the planning levels.

Len  Whitmore's picture Len Whitmore
Experimenting: The Way Forward for Agile Development Teams

If you asked anyone in my team what agile practice is most responsible for our success over the past eight years, I bet they'd answer "retrospectives". At the start of every two-week sprint, we spend time talking about the previous sprint, identifying areas that need improvement, and thiinking of ways to overcome obstacles. But I wonder if it's not so much the retrospectives themselves, as the small experiments (to borrow Linda Rising's term) we try to address our problem areas.

Lisa Crispin's picture Lisa Crispin
Mission Possible: ScrumMaster and Technical Contributor

Teams trying out Scrum might not be able to justify a full-time ScrumMaster to the organization, so the role is filled by a contributor on the team. This can be a challenge and, if done incorrectly, a problem. Learn some potential issues to be aware of and how to make the hybrid role work.

Steve Berczuk's picture Steve Berczuk
Personality Factors That Influence Core Build and Release Management Practices

Leslie Sachs discusses the key people skills essential to appreciating how and which personality factors most impact one's ability to successfully implement core build and release management practices.

Leslie  Sachs's picture Leslie Sachs
The Competition of Agile

It is sensible to want to avoid the head-butting sort of competition—that is, arguing for the sake of arguing. But, differing opinions and styles can be a good thing. Competitive forces have driven markets, innovation, and civilization for millennia. Here, Jurgen Appelo takes a look at some of the various approaches to agile development and what they bring to the table.

Jurgen Appelo's picture Jurgen Appelo
My Experience with Test Driven-Development

Vinay Krishna explains why agile development includes testing and coding concurrently, which is also what test-driven-develppment emphasizes.The transformation from coder to developer to tester is needed in all agile software development projects.

Vinay Krishna's picture Vinay Krishna
Mixing Roles in Scrum

We put a lot of emphasis on being Renaissance workers, able to step comfortably from one job role to the next. But, as Mitch Lacey describes here, not all roles play nicely with each other, and trying to combine them may lead to disaster.

Mitch Lacey's picture Mitch Lacey
Building a Competitive Software Capability: Creative Destruction

In this excerpt from Leadership, Teamwork, and Trust: Building a Competitive Software Capability, Watts Humphrey and James Over explain why these changes must be a high priority for software companies and other organizations for whom knowledge is a valuable asset.

Watts S. Humphrey's picture Watts S. Humphrey James W. Over

Pages

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!