|
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.
|
|
|
Writing Good Test Cases We all know writing test cases is an integral part of the testing activity. In order to write good test cases, we must first understand what a test case is and why we need to write test cases. Can’t we live without writing test cases?
|
|
|
Accelerating Agile Development through Software Reuse One of the main attractions of agile methods over traditional heavyweight approaches to software engineering is their ability to accelerate the software development process. By minimizing superfluous activities and artifacts such as models and documentation and focusing developers' efforts on coding, agile methods increase productivity and reduce overall development time.
|
|
|
Suffering for Success One of the most valuable services a QA group provides is preventing failure. Ironically if the group succeeds at this, QA might find themselves unpopular or out of a job. Linda Hayes reveals how typical methods of measuring success can actually cause failure. Especially if success is achieved at the loser's expense.
|
|
|
Agile Codeline Management Software developers often view version management tools and techniques as a necessary evil. This is particularly true of developers practicing agile techniques. However, version management, can be an aid to agility rather than something that gets in the way.
|
|
|
Software Development Lifecycle: Defect and Test Case Measurement This article focuses on how to manage the defect and test case measurement during the software development lifecycle. This should be a practical resource for software developers and project managers.
|
|