|
|
|
|
|
|
|
|
|
Linda Rising, Independent Consultant |
 |
Those who attend conferences or read books and articles discover new ideas they
want to bring into their organizations—but they often struggle when trying
to implement those changes. Unfortunately, those introducing change are not always
welcomed with open arms. Linda Rising offers proven change management strategies
to help you become a more successful agent of change in your organization. Learn
how to plant effective seeds of change and identify what forces in your organization drive
or block change. In addition to using these approaches to change your organization,
you can use them to become a more effective person. Come and discuss your organizational
and personal change challenges. Linda shows how the lessons from her book, Fearless
Change: Patterns for Introducing New Ideas, can help you succeed. Learn how to overcome
adversity to change and to celebrate your improvement successes along with your
organization’s new found practices.
|
|
Linda
Rising has a Ph.D. from Arizona State University in the field of object-based
design metrics and a background that includes university teaching and industry work
in telecommunications, avionics, and strategic weapons systems. An internationally
known presenter on topics related to patterns, retrospectives, and the change process,
Linda is the author of Design Patterns in Communications, The Pattern Almanac
2000, A Patterns Handbook, and co-author with Mary Lynn Manns of Fearless
Change: Patterns for Introducing New Ideas. Find more information about Linda at
www.lindarising.org. |
|
|
|
|
|
|
|
|
|
This “on-your-feet” tutorial
guides project managers, agile coaches, and Scrum Masters in how to apply facilitation
techniques and tools to support collaborative decision making. These practices are
critical for agile planning, daily interaction, and reviews of agile software development
projects and teams. Jean Tabaka shows why agile teams require a collaborative style
of decision making rather than classic command-and-control approaches. Practice
planning for agile meetings and kicking off those meetings to ensure that the attendees
are truly engaged and results-oriented. Find out about tools to help teams gather
the important insights and wisdom necessary to attain the sustainable agreements
in their agile projects. Learn ways to deal with conflict that occurs when many
opinions and recommendations arise, and help teams inspect and adapt their agile
processes collaboratively. Along the way, you will discover what must change within
your organization to successfully apply collaboration, especially with large and
distributed agile teams.
|
|
Jean Tabaka is an Agile
Mentor and Coach with Rally Software Development. In addition to being a Certified
Scrum Trainer and Practitioner, she is also a Certified Professional Facilitator.
Her unique blend of passions and skills has been applied in a variety of organizations—large
and small, co-located and distributed—eager to adopt the best of agile and
bring out the best in their teams. Author of the Agile Software Development
Series book Collaboration Explained, Jean holds a Masters in Computer Science from
Johns Hopkins University. When not sharing her agile passion with clients, she resides
in beautiful Boulder, Colorado.
|
|
 |
|
|
|
|
|
|
|
|
Michael Mah, QSM Associates, Inc. |
|
Frequently, schedules and deadlines all too often are dictated
to software development teams. When this happens, what is a manager to do? Michael
Mah addresses the key issues in deadline-driven projects—estimation and risk
management. Employing industry data from more than 7,000 completed projects worldwide,
Michael describes how different software projects—agile development, waterfall
development, and package implementations—behave in unique and interesting
ways when a deadline is imposed. Using case studies from leading companies, Michael
illustrates how to estimate and commit to a reasonable project scope in the face
of aggressive deadlines. Find out how to “triage” the amount of functionality
you can deliver within an imposed deadline and deal methodically with the inevitable
project trade-offs. Develop a core set of estimation metrics that will help you
avoid common scheduling traps.
|
Laptop Required |
|
|
To take full advantage of this tutorial, participants should bring a laptop computer
for data capture and estimation calculations.
|
|
|
Michael
Mah is director of the Benchmarking Practice, an author with the Cutter
Consortium, and managing partner of QSM Associates, Inc., specializing in software
measurement and project estimation. Michael has written extensively and consulted
with the world’s leading software organizations, while collecting data on thousands
of projects worldwide. Michael’s book-in-progress, Optimal Friction,
examines the dynamics of teams under time pressure and its role in contributing
to success and failure. He lives in the mountains of western Massachusetts with
his two young children. Michael can be reached at www.qsma.com. |
|
|
|
|
|
|
|
|
|
|
Timothy Korson, Korson Consulting |
|
“Pure” agile development uses story cards to scope
and organize customer needs. Each story is described in a sentence or two with details
filled in through conversations. Because there are no written requirements that
contain enough information for independent test teams to create comprehensive test
suites, testers find themselves in a difficult position. In some agile philosophies,
testers must create test cases directly from discussions with clients. In effect,
the test cases become the only detailed requirements. Eliciting test requirements
directly from stakeholders requires that testers learn a new set of skills and practices.
In addition to explaining how to effectively create system test cases from stories
and stakeholders, Tim Korson examines unit, component, increment, and regression
test development as parts of a comprehensive testing process within an agile development
environment. Tim presents test automation strategies and tools that agile testers
are successfully using today.
|
|
Tim
Korson has a decade of experience working on a large variety of systems
developed using modern software engineering techniques. This experience includes
distributed, real-time, and embedded systems as well as business information systems
in an n-tier, client-server environment. Tim’s typical involvement on a project
is as a senior management consultant with additional technical responsibilities
to ensure high quality, robust test and quality assurance processes and practices.
He has authored numerous articles and co-authored the book Object Technology
Centers of Excellence. |
|
|
|
|
|
|
|
|
|
|
Rebecca Wirfs-Brock, Wirfs-Brock Associates |
|
Objects are more than simple bundles of logic and data—they
are service-providers, information-holders, coordinators, controllers, and interfacers
to other systems. Rebecca Wirfs-Brock discusses how objects play specific roles
and occupy well-known positions in an application’s architecture. Each object
must know and do its part! Role stereotypes—think of them as purposeful oversimplifications—are
a fundamental way of seeing objects’ responsibilities. Learn and practice
practical responsibility-driven design techniques to enhance your design process
and design thinking. Experience the latest in Class Responsibility Collaborator
(CRC) modeling, object identification and naming, object role stereotypes, control
style design, collaboration trust regions, and contracts. Find out how responsibility-driven
design thinking can enhance your design and development practices.
Delegates should be familiar with object-oriented
technology and object concepts. Some experience with object design and programming
languages is a plus.
|
|
Rebecca
Wirfs-Brock, design columnist for IEEE Software, is a well-known object
practitioner who invented the way of thinking about objects known as responsibility-driven
design. Through her writing, teaching, consulting, and speaking, Rebecca popularizes
the use of informal techniques and practical thinking tools for designers, architects,
and analysts. She teaches courses on responsibility-driven design, practical UML,
developing and communicating software architecture, and agile design skills. Rebecca
regularly mentors teams on use case writing, design, architecture, and managing
incremental, iterative object-technology projects. Rebecca is the author of
Object Design: Roles, Responsibilities, and Collaboration. |
|
|
|
|
|
|
|
|
|
|
Richard Bender, Bender RBT |
|
In this process-oriented class—geared
to business analysts, designers, programmers, testers, technical writers, and users—Richard
Bender teaches a powerful and practical method for ensuring that requirements specifications
are clear, concise, and unambiguous. Learn how to verify that requirements are written
at the correct level of detail needed by designers, developers, and testers. Because
this level of detail must be discovered one way or another, this process does not
add any additional overhead to the effort and costs of developing requirements specifications.
In fact, by eliminating ambiguous requirements early in development, you can save
time, reduce confusion, and avoid unnecessary re-work. In this hands-on workshop,
learn the ambiguity review process and how to quickly identify ambiguities in specifications
in any format. Eliminate unnecessary complexity from your requirements documents
and help your team develop and test applications more quickly and more effectively.
|
|
Richard Bender has more than thirty-five years of
experience in software with a primary focus on quality assurance and testing. He
has consulted internationally for large and small corporations, government agencies,
and the military on applications that run the gamut from finance, billing, and manufacturing
to medical, transportation, and communications—to prison management and weather
forecasting. Richard teaches a series of courses on the techniques for practical,
rigorous requirements-based testing, code-based testing, and writing testable requirements. |
|
 |
|
|
|
|
|
|
|
|
Linda Westfall, The Westfall Team |
|
Linda Westfall offers a practical process
for establishing and tailoring a software metrics program that focuses on business
goals and information needs. Learn a practical, start-to-finish method of selecting,
designing, and implementing software metrics. Linda outlines a “cookbook method”
you can use to simplify the journey from conceptual software measurement and metrics
to valuable information summarized and delivered to management. Utilize the Goal/Question/Metric
paradigm to select metrics that align with the organizational, project, and process
goals. Walk through the steps for designing important metrics—standardizing
entity and attribute definitions, choosing measurement functions, establishing measurement
methods, defining decision criteria, designing reporting mechanisms, and determining
additional qualifiers. Find out who should collect the data, what data to collect,
and how to collect it. Learn to consider the human issues of implementing a measurement
system and the metric do’s and don’ts that Linda has discovered over
many years of helping people with their metrics programs.
|
|
Linda Westfall is the president of The Westfall
Team, which provides software engineering, quality and project management consulting,
and training services. Prior to starting her own company, Linda was
senior manager of quality metrics and analysis at DSC Communications, where her
team designed and implemented a corporate-wide metrics program. An ASQ Certified
Software Quality Engineer, Linda has more than thirty years of experience in real-time
software engineering, quality, and metrics. A past chair of the ASQ Software Division,
Linda Westfall has served as the Software Division’s Program Chair and Certification
Chair and on the ASQ National Certification Board. |
|
 |
|
|
|
|
|
|
|
|
Ken Pugh, IT communication |
|
All projects, whether agile or traditional,
need requirements. Ken Pugh explores the differences between agile and traditional
requirements by interactively creating a set of agile-style requirements. These
requirements are developed through progressive elaboration—rather than the
big-bang, big-document approach. Ken first examines with you how stakeholders and
requirements gatherers interact and communicate in an agile environment. Students
will create a charter for a project that defines the overall scope and participate
in a story-gathering workshop to create an initial set of stories. Learn when and
how to revise stories by chunking and de-chunking to ensure that the requirements
fulfill the characteristics of good stories. Explore user roles, personas, and narratives
to determine additional stories. Practice prioritizing the requirements and estimating
their business value to help in that prioritization. At the end of the session, students
will begin constructing use cases and acceptance tests to add details to the requirements.
|
|
A fellow consultant with Net Objectives, Ken Pugh (ken.pugh@netobjectives.com) consults, trains, mentors, and testifies on technology topics ranging from object-oriented design to Linux/Unix to the system development process. He has written several programming books, including the Jolt Award winner Prefactoring and has served clients from London to Sydney. When not computing, Ken enjoys snowboarding, windsurfing, biking, and hiking the Appalachian Trail. |
|
 |
|
|
|
|
|
|
|
|
|
|
Mike Cohn, Mountain Goat Software |
| | |
