The Latest

Postmodernism in Software Development [article]

Recent history has ushered in the postmodern era in all its fragmented glory. With its arrival comes the displacement of the absolute, the certain, and all that characterizes the modern age. Along with changes in art, politics, and philosophy— there are reverberations in business and technology. The societal shift from Modernism to Postmodernism mirrors and reinforces a shift in software development from traditional waterfall to non-linear Agile methods.

Ryan  Fogarty's picture Ryan Fogarty
Timing Matters in Managing Change[article]

Implementing change can be a colossal challenge. People tend to prefer what's familiar, safe, and predictable to that which is new, unfamiliar, uncertain, confusing, or potentially risky. But the timing of a change effort can influence how readily people accept the change and adjust to it.

Naomi Karten's picture Naomi Karten
When is Open Source not Enough?[article]

Open source CI tools have been immensely popular, but are they the perfect fit for your operation? Answer these seven questions to quickly assess if you should upgrade to an enterprise-class CI environment.

Anders  Wallgren's picture Anders Wallgren
Nationwide - Kevin Fisher - AVP of Product Management - Value of Alignment[article]

Nationwide - Kevin Fisher - AVP of Product Management - Value of Alignment

Bob Payne's picture Bob Payne
Independent Testers? Or Independent Thinkers?[article]

In this article, Lisa Crispin recalls a time when testers alone were solely responsible for software quality, and compares that to more modern thinking where collaboration between developers and testers is king. Software quality is everyone's job, sometimes it takes independence to get there.

Lisa Crispin's picture Lisa Crispin
Nationwide - Mike Kaiser - Customer Proxy and the role of experimentation[article]

Nationwide - Mike Kaiser - Customer Proxy and the role of experimentation

Bob Payne's picture Bob Payne
Rocks into Gold: Part 1[article]

This short book, written by Clarke Ching, is a "biztech" parable for software developers who want to survive—and then thrive—through the credit crunch. We have republished the book in a four-part series. In part one, we meet the main characters who have just found out that their jobs are on the line after discovering their major client's business is failing. Follow the story as our characters fight to keep their jobs by implementing creative business ideas and management skills taken from agile development.

Clarke Ching's picture Clarke Ching
Product Backlog Rules of Thumb[article]

While working with Product Owners over the years I have learned some rules of thumb that help make their Product Backlogs more manageable. Some of these rules of thumb I learned from other people and some were learned through trial and error.

Remember that the statements contained in this article are just rules of thumb intended to help guide your management of a Product Backlog. They are not rules to adhere to no matter what. Always use common sense when applying a rule of thumb to your particular context.

TechWell Contributor's picture TechWell Contributor
Group Coherence for Project Teams - Continuous Improvement[article]

One of the principles in the Agile Manifesto states, "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." This principle guides both aspiring and seasoned Agile teams in the pursuit of continuous improvement and can support whatever Agile adoption path an organization may choose. Kent Beck adds observations about this topic.

TechWell Contributor's picture TechWell Contributor
Speaking Ill of the Dead[article]

The title alone should generate imagery ranging from destructive rumors to the macabre. Who are these dead, and who is speaking ill of them? "The dead" are former team members, the ill speakers are those who blame problems on them, and we are taking a critical look at this complaining with just a touch of irony. We are talking about the culture of blaming current problems and challenges on team members who are no long with the team for whatever reason. Almost anyone who has been involved in the software development life cycle has experienced this behavior, and very possibly taken part in it even with the best intentions in mind.

TechWell Contributor's picture TechWell Contributor
A Critical Look at CMM and Agile Through Gen Y[article]

Much has been written about the commonality or even the lack of it between Agile and CMM. CMM claims to be a flexible model that can be tailored and adapted to many life cycles. The continued discussion is evident enough that it is not sufficient to compare practice to practice and arrive at any reasonable conclusion about their overall compatibility. The one difference that seems to have earned consensus amongst most of the published literature on the subject is "the people aspect" of these models. 

TechWell Contributor's picture TechWell Contributor
What is Best, Scrum or Kanban?[article]

What is best, Kanban or Scrum? Because I can't make up my mind, I decided to write a single article in two parts—one where I wear the "I love Kanban" hat and one where I'm wearing an "I love Scrum" T-shirt.

TechWell Contributor's picture TechWell Contributor
ScrumBut: Failure to Deliver[article]

In this article, Michele Sliger discusses one of the more common "ScrumBut" practices that, while allowing teams to say "We suck less," isn't really in keeping with intended Scrum practices. This ScrumBut practice is the persistent failure of the team to complete the agreed-upon features in the iteration or sprint.

Michele Sliger's picture Michele Sliger
Deception and Self-deception in Software Testing[article]

Untruths about software testing are common. Managers, programmers, and other people on software projects don't always mean to deceive. Quite often, they fool themselves into believing what they want to believe. But sometimes they lie deliberately and even pressure testers to lie. And testers can also practice deceptions and self-deceptions of their own. In this column, Fiona Charles describes four categories of common deceptions and self-deceptions in testing and outlines what testers need to do to address them.

Fiona Charles's picture Fiona Charles
If Your Build Fails and No One is Around to Hear It, Does It Make a Sound?[article]

Continuous Integration build tools are great: they help us ensure our product works after every commit, keep historical data and metrics, build our product for all target environments, and do many more useful things. But there's one key aspect that often gets overlooked: They're fun.

Daniel Wellman's picture Daniel Wellman


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

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