≡ Sections
ADVERTISEMENT

Ready, Set, Go...and Ready Again: Planning to Groom the Backlog

by Andy Berner

For an agile project to progress smoothly, the backlog must be groomed and ready for each sprint. That work must be included in your project plan. This article gives you five points to consider when planning that work.

When Estimates Go Wrong

by George Dinwiddie

Custom software development is notoriously difficult to estimate. We start with vague ideas of what we want, expecting to fill in the details later. We’re usually doing something a little different than what we’ve done before, or completely different. How can we act more productively?

Do You Really Need a Requirement Management Tool?

by Michelle Stronach

Have you realized that your organization is not putting enough attention on requirements? Wondering what types of tools are out there and how much they cost? Do you even need a tool? And if so, what kind?

Don’t Go Chasing Waterfalls: 2 Reasons to Avoid Waterfall, and 3 Better Approaches

by Rob Saxon

The waterfall methodology for projects is aptly named, because it is equally painful to try to go back to prior phases of a project once the effort has advanced to the next phase. This article will outline two reasons to avoid waterfall, and three ways to approach software projects that are more useful.

What You Should Know About Kanban (Part 3)

by Don Kim

If Kanban works well on specific software projects, can it be scaled to facilitate Lean throughout an organization? Here we look at how Kanban can be thought of as a general purpose change management approach for your organization.

Phased-Based Governance

by Rob Saxon

Governance happens in projects all the time, and a well thought-out governance process can be a powerful project tool. In this article, we will examine why governance is necessary, where governance is most effective and how we as project and program managers can use governance to powerful effect.

Business Process: A Lesson in Anatomy

by Michael Wood

In an attempt to help those of you struggling with Business Process Improvement and Business Process Analysis, our expert presents these “anatomical components” in terms of a series of rules so that you can use them in your efforts.

Coherence vs. Standardization

by George Dinwiddie

Standardization is the “copy and paste” method of process development. It’s as bad in spreading process through an organization as “copy and paste” is in code. Copying a working instance may be a good starting point, but it’s a bad destination. Creative work needs attentive thinking, even when deciding to not change the status quo.

Testing Tools Evaluation Form

PREMIUM deliverable

This Testing Tools Evaluation Form details a complete description of the expected level of service and performance to be provided by prospective testing tools.

Project Schedule Quality Control

PREMIUM deliverable

Use this quality control checklist to identify all the ingredients of a healthy, flexible and dependable project schedule.

Test Sign-Off Form

deliverable

Has your system been properly tested by phase (unit, integration, user acceptance), and do you have the formal sign-off of approval to proceed?

Quality Management Systems Procedures Testing

PREMIUM deliverable

This procedure describes the process of testing software code or products by the test team. It documents the procedure for the entire testing cycle: generating test plans, scheduling tests, conducting tests and reporting test results. This procedure applies to new development, as well as major and minor releases, including customized solutions delivered to customers.

Software Testing Principles Checklist

checklist

Do you know how to thoroughly and efficiently test the software product you have so painstakingly built? Don't risk delivering a faulty software product due to insufficient or unfocused testing. Use this list to check whether you are testing smart--or just testing!

Package Evaluation Test Report

deliverable

What is involved in conducting an evaluation test for an application package? Here's a guide for reporting the test requirements, procedures and results.

Performance Testing

PREMIUM project plan

Defining and measuring software quality attributes is critical to the success of any distributed application, and performance is no exception. Distributed applications must demonstrate performance in order to assure immediacy. Use this project plan to stay on top of your Performance Testing.

The Project Testing Environment

PREMIUM presentation

The key to any successful testing effort is creating a suitable test environment in which testing can occur.

Project Testing

PREMIUM presentation

How to develop a complete testing plan and schedule.

Testing Tool Selection Form

deliverable

Selecting the right testing tool means you must look at a myriad of factors and how well each candidate tool meets your application's testing requirements. This form will help you evaluate the candidates and select the best testing tool for your app.

Testing Services Review Form

PREMIUM deliverable

This Testing Services Review Form outlines major factors to consider when testing software, middleware or Web-based applications.

The Happy Tester

by Mike Donoghue

Being a strong tester means being critical and assertive. This ability is not easy to control and can lead to finding flaws in all sorts of everyday surroundings. How to communicate these errors and mistakes without being a first-class jerk is also difficult. Can you keep everyone's frown upside down?

ADVERTISEMENTS

"There is no shame in not knowing; the shame lies in not finding out."

- Russian proverb