The Latest
It's the People; It's Always the People[presentation] Why do we insist on calling people “resources?” If software projects were a factory, people would be fungible-interchangeable equipment just like desks and computers. |
![]() |
|
Are You a Develoment Professional?[presentation] The past decade brought the rise of the Agile movement, which split into two parts-Scrum, dominating the project management practices of agile; and XP, dominating its technical practices. |
Robert Martin, Object Mentor
|
|
You Can Always Get What You Want[presentation] Agile, waterfall, iterative, staged, gated, phased-none of it really matters if all you create are a few early "wins", mediocre solutions, and quick fixes. |
![]() |
|
Testing in an SOA Environment[presentation] Testing Web applications built with service-oriented architecture (SOA) is not the same as testing any other GUI-based application. |
Sanjeev Padasalgi, Sonata Software Ltd.
|
|
Eliminating Process Bottlenecks: The Theory of Constraints[presentation] Managers often fall into the trap of making sure that everyone is busy. It seems logical that we should keep all of our highly paid “resources” (ouch!) fully utilized. |
![]() |
|
The Power of Concept Designs in Requirements Elicitation[presentation] Ever been in a situation where everybody on the design and development team thinks they agree on the requirements-until you try to design that first screen or page? |
Scott Plewes, Macadamian Technologies
|
|
Redirecting the Doomed Project[presentation] It is nearly impossible to work in software development and not end up on a project which one day ends as a death march. |
![]() |
|
Testing and Quality Beyond the Requirements and Code[presentation] Many organizations institute testing and quality improvement initiatives focused on testers, developers, and software managers. One stakeholder often ignored in these efforts is the user-your customer. |
Lanette Creamer, Adobe Systems
|
|
Is It Good Enough To Ship? Predicting Software Quality[presentation] Software quality often gets lots of lip service and little else-until its absence triggers a disaster and stuff hits the wall. |
Donald Beckett, Quantitative Software Management
|
|
Involve Your Customers for Better Requirements[presentation] Have you ever heard something like “This feature (system) doesn't look anything like what I expected and doesn't do what I want”-even though you were confident that you knew what your customers wanted? |
![]() |
|
Agile Development Conference & Better Software Conference West 2010: Seven Deadly Habits of Ineffective Software Managers[presentation] Looking for an insightful-and humorous-review of the management disasters you may have witnessed during your professional software career? |
![]() |
|
A Death Knell for Traditional Test Labs[presentation] In this jab at the traditional test lab approach to testing software and Web services, Ken Johnston explains the what, why, and how of the practices and processes for testing in production (TiP). |
|
|
Measurement Problems that Plague Us[presentation] Measurement problems in software organizations are many: challenges with effort tracking; difficulties motivating the workforce to comply; resource management in multitasking and matrix organizations; attempts to "standardize" project status |
Beth Layman, Layman & Layman
|
|
Nonfunctional Requirements: The Forgotten Needs[presentation] Nonfunctional requirements are an essential part of a holistic understanding of system requirements; yet many teams struggle with them. |
![]() |
|
The Art of Giving and Receiving--Feedback[presentation] When people work closely together, there's bound to be friction and irritation. Some people find it difficult to discuss these issues directly. So they hint and hope or simply procrastinate and don't do anything. |
![]() |