Planning
Better Software Magazine Articles
 |
Building Highly Productive Teams Using a Commitment-to-Progress Ratio: Work Committed vs. Done This article explains methods to build a team that will embrace "required work" and deliver robust software in a predictable fashion. It proposes a measure that helps calculate the throughput of an agile team by comparing work committed to work actually done. |
|
|
How Technical Support Is Like a Pain in the Neck Payson Hall looks closely at the unique idea of not just providing better service to clients, but changing the client's perception of what defines good or bad service. We've gotten so used to "normal" that we've lost the ability to appreciate it. But this can be changed. |
||
 |
Agile Code for Agile Teams What makes a team agile? Is it in the way it plans projects or how it engineers its products? In this article, Steve Berczuk explains how agile code and technical practices can help a team stay agile across the product lifecycle. |
|
|
Filling The Blank Page Having trouble starting projects, understanding scope and business processes, or with estimation? Mark shares some tips and techniques to avoid common business analysis pain points at the early part of a new project assignment. |
||
|
Mobile Challenges for Project Management: The Project Factors Developing software for mobile apps requires a different mindset from developing for computers. Some concepts transfer directly, but there are many device-related challenges managers must overcome. In part one of this two-part series on mobile challenges, Jonathan Kohl addresses some of the project factors managers should take into account during mobile application development. |
||
 |
Forget What You Think You Know The transition to lean-agile can be challenging for traditional project managers because traditional competencies and practices can conflict with the core principles that explain why lean principles work. To help prepare project managers transitioning to lean-agile, this article exposes five counterintuitive practices that challenge standard project management beliefs. |
|
|
Enterprise Agile and the Business Analyst Agile is making its way into the enterprise as a project methodology for industrial-strength projects. Why the popularity? The answer lies in the requirements paradox: “We want requirements to be stable, but requirements are never stable.” Discover some key agile concepts as they affect business analysts. |
||
|
Sometimes Perception Is the Problem High on a mountain twenty years ago, a wise man shared secrets of problem solving that have served Payson Hall ever since. In this article, Payson passes along a simple definition that offers insights into problems and potential solutions. |
||
|
Hearing ''No'' "No" can be disappointing. Sometimes we have difficulty hearing or dealing with No. Can we learn how to cope with No with less pain and angst? Can we learn how to prevent No at least some of the time? Yes and yes! |
||
|
Broken Windows, Broken Projects A social experiment in the ‘80s found “Vandalism can occur anywhere once communal barriers are lowered by actions that seem to signal that 'no one cares.'" The same can be said for our software projects. |
Pages
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.