The Latest

How Agile Practices Reduce Requirements Risks[article]

Requirements risks are among the most insidious risks threatening software projects. Whether it is having unclear requirements, lack of customer involvement in requirements development, or defective requirements, these troubles are a major culprit in projects that go awry. As requirements expert and agile coach Ellen Gottesdiener explains, agile practice can go a long way in mitigating those risks.

Ellen ellensqe's picture Ellen ellensqe
Agile 2009 - Conference preview with Johanna Rothman[article]
Podcast

Bob Payne chats with Johanna Rothman about the upcoming Agile 2009 conference.

Bob Payne's picture Bob Payne
Beauty Is in the Eye of the Beholder[article]

As a user experience design specialist, clients often ask Jeff Patton to make their software "look better," so it can be successful. But when clients focus primarily on aesthetics, they're often addressing the wrong thing. In this column, Jeff takes a look at common user interface (UI) mistakes and the key concerns software development teams should address to build successful UIs.

Jeff Patton's picture Jeff Patton
How Scrum Generates Increased Productivity, Part Three: The Team[article]

An agile team is, of course, made up of a group of people. As such, it's unique in that responsibilities are distributed among multiple parties to successfully deliver a product increment. Just as the entire Scrum team (i.e. the ScrumMaster, Product Owner, and team) must depend upon one another to complete projects, so, too, the development team's members must trust each other to self-organize their way to success.

TechWell Contributor's picture TechWell Contributor
Principles for managing a Scrum-based Agile Program[article]

Agile project management philosophy, though not very different from the traditional management practices and framework, needs to be rationalized to suit the demands of the agile methodologies. The project management practice remains the same for requirements, planning, initiating and tracking the progress of the project in line with the business vision. However, the focus is more on adaptability towards changing requirements, team work, collaboration and the ability to plan and deliver small chunks of useable software in short intervals of time

TechWell Contributor's picture TechWell Contributor
Managing Software Debt[article]

Continued Delivery of High Values as Systems Age

Many software developers have to deal with legacy code at some point during their careers. Seemingly simple changes are turned into frustrating endeavors: Code that is hard to read and unnecessarily complex. Test scripts and requirements are lacking, and at the same time are out of sync with the existing system. The build is cryptic, minimally sufficient, and difficult to successfully configure and execute. It is almost impossible to find the proper place to make a requested change without breaking unexpected portions of the application. The people who originally worked on the application are long gone.

TechWell Contributor's picture TechWell Contributor
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]
Podcast

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]
Podcast

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

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!