CONCURRENT S E S S I O N S
1 PDU per
Session
Wednesday, June 10, 1:30pm
BETTER SOFTWARE
BW5
PROJECTS & TEAMS
BW6
BUSINESS ANALYSIS &
REQUIREMENTS
Integrating Agile
Requirements
and Traditional
and Acceptance
Projects in the
Tests: Yes, They
Enterprise
Go Together
Steve Caseley, Sensei
Project Solutions
Is your
organization
using agile on
some projects
and classic
waterfall on others? Are you
concerned with integrating your
agile projects into your current
PMO, tool, and reporting
structure? Are you afraid you
might require two totally
separate approaches? Steve
Caseley believes you can
support agile without having to
introduce a new suite of tools.
Project vision, release and sprint
planning, product backlog
management, and automated
production of Scrum artifacts
are all possible with your
existing project management
tools. Steve demonstrates how
Microsoft Project and Project
Online can provide full support
for Scrum/agile projects. Having
a framework based on existing
tools is key, as it fully integrates
your agile projects into
established PMOs, ensuring
consistency across your
organization’s project portfolio
independent of the delivery
approach selected. Learn how
to provide full support and
manage all projects—both
traditional and agile—in your
portfolio in the same tool set.
Ken Pugh,
Net Objectives
The practice of
software
development
requires a clear
understanding of
business needs.
Misunderstanding requirements
causes waste, slipped
schedules, and mistrust.
Developers implement their
perceived interpretation of
requirements; testers test
against their perceptions.
Disagreement can arise about
implementation defects, when
the cause is really a
disagreement about a
requirement. Ken Pugh shows
how early acceptance test
development decreases
requirements
misunderstandings by both
developers and testers. A
testable requirement provides a
single source that serves as the
analysis document, acceptance
criteria, regression test suite,
and progress tracker for each
feature. Explore how the
business, testers, and
developers can create, evaluate,
and use testable requirements.
Join Ken to examine how to
transform requirements into
stories, which are small units of
work that have business value,
sm