|
MORNING
KEYNOTE:
The Impact of Web 2.0 on The Software
Development Community
Ed
Yourdon,
Author
8:10am
- 9:10am
Software development processes and
technologies have evolved and improved over the past couple decades; but
they still tend to follow a traditional, top-down, hierarchical management
style -- with traditional tools and technologies to support that style.
But the recent appearance of Web 2.0 tools -- including blogs, microblogs
(Twitter) wikis, RSS feeds, etc. -- has begun to change not only the broad
spectrum of interactions in business and society, but also the
interactions and work-styles of developers, users, analysts, QA
specialists, and other stakeholders in software development. Ed Yourdon's
presentation will summarize these tools and trends, and will offer
practical guidelines and suggestions for putting them to effective use for
greater productivity, quality, and user satisfaction.
AFTERNOON
KEYNOTE:
The
Role of Software Architecture in System Development and Evolution
Linda
Northrop,
Director of the Product Line Systems Program, The Software Engineering
Institute
1:10pm - 2:10pm
Quality software is software
that is fit for its intended purpose. High quality software meets business
goals and user needs, which means it has the right features and the right
attributes. Building quality software requires using disciplined processes
and a carefully designed software architecture. Software architecture
forms the backbone for any successful software-intensive system. It is the
first design artifact that addresses key quality attributes such as
affordability, reliability, security, modifiability, and performance. It
provides the most fundamental basis for communicating design decisions and
establishing effective work breakdown structures. The software
architecture is the reusable, transferable abstraction that is the basis
for software product lines. Architecture represents an enormous risk in a
software development project; the wrong architecture leads to poor quality
software and very often to project failure. This talk will highlight the
importance of both software architecture and the disciplined use of
effective architecture-centric practices.
CLOSING
KEYNOTE:
Putting
the engineering in software engineering: technology infrastructure in
process improvement
Dr.
Adam Kolawa,
Co-founder and CEO of Parasoft
4:10pm - 5:00pm
Like
other engineers, software developers transform ideas into usable products.
Unlike other engineers, they create a product that is inherently
invisible, not completely testable and often transitional. Moreover, a
software product in an interim development stage is often unusable,
producing free-floating anxiety in developers and users alike. Behavioral
science tells us that invisibility and the effect of “all or nothing”
are psychological factors that negatively impact developer effectiveness.
Mundane tasks such as repeated testing often result in frustration while
the transitional nature of software creates a false notion that the
defects can always be removed in the future. Moreover, there is growing
realization that we humans are incapable of fully applying and maintaining
our own best practices.
Based on aforementioned factors and the
concepts described in the recently published book, the co-authors,
Huizinga and Kolawa, will explain how to establish an automated technology
infrastructure that supports effective software development. This
infrastructure defines people roles, necessary technology, and
interactions between people and technology. This infrastructure provides
product visibility, automates repetitive tasks, tracks project status, and
seamlessly collects project data to provide measures necessary for
decision making. This infrastructure forms a software production line,
thereby putting the engineering into software engineering. Most of all, by
putting the engineering into software engineering this infrastructure
sustains and facilitates the improvement of human-defined processes.
TRACK
ONE: CMMI & PROCESS IMPROVEMENT I
EXECUTION
- the key to success! The Top 10 Steps for Achieving Successful
Institutionalization of Processes and Tools
John
L Voss, Accenture
9:20am -
10:00am
Are you constantly fighting to successfully
institutionalize process improvements? Is your organization undergoing yet
another reorganization? Does your organization need to integrate multiple
models or standards? Are you tired of trying to figure out how to make it
all fit together?
The answers are only a few steps away! Attendees will
learn tips and techniques to overcome organizational obstacles; including
tight budgets, limited time, limited availability of skilled resources,
senior leadership support. I will provide a set of activities you may
perform now that can work successfully even when everything around you may
seem to be in turmoil..
Team
for Success: Process Engineering and Quality Assurance
Sharon
E. Miller,
L3 Communications Command & Control Systems and
Software/ILEX Sector
10:30am - 11:20am
Process engineering and quality assurance are in place;
organizational processes are defined and deployed; institutionalization is
still an issue. Sound familiar? The easy part of the journey to CMMI Level
3 is putting organizational processes in place. The hard part is getting
the entire organization to embrace the processes and integrate them into
their day-to-day activities.
Process engineers are model-centric, generally not very
involved in day-to-day project activities. Quality assurance is
project-centric; very involved in day-to-day project activities. This
presentation discusses how one organization leveraged the strengths and
capitalized on the differences between these disciplines to successfully
drive institutionalization in a natural and seamless way.
Extreme
Auditing: Application of extreme programming in Auditing. A breakthrough
in process experimentation in Nedbank
Reinier Olivier &
Amol Tope, Zensar Technologies Ltd
11:20am - 12:00pm
Organizations
are striving for process maturity to improve their productivity, drive
down cost, ensured predictability, retain the knowledge in the process
assets and reduce dependency on people. At the IT Process audit function
of Nedbank Ltd., South Africa, we have applied concepts of extreme
programming to achieve these goals. The purpose of this paper is to
briefly explain the steps taken at Nedbank to adopt and establish these
concepts in the Process & Product Quality Assurance (PPQA) function.
The paper gives a brief review extreme programming and describes the
various methods used by the organization in adopting these principles and
the results of implementation. The paper also illustrates the benefits,
which the organization has gained.
Work On
Your Engineering Business, Not In It.
Rolf
Reitzig, cognence,
inc
2:10pm - 2:50pm
Best in Class companies are built on a simple principle:
successful businesses are built on scalable systems that enable their
people to deliver higher quality products and services than the
competition. The CMMI builds on this principle, particularly at Maturity
Level 3 where a repeatable, scalable, and franchisable engineering system
has been put in place. Unfortunately, many organizations don’t
understand and don’t employ the strategic benefits CMMI embodies. Too
many view compliance as “checking the box” versus creating a culture
that constantly improves. This presentation will introduce participants to key
concepts that enable one to work ON an engineering business, and not IN
it.
The
Last Phase in Process Change - Deployment
Barbara
A. Tyson, Software
Engineering Group
3:20pm - 4:10pm
Organizations often struggle to effectively deploy new or
changed processes. Many times this is because the deployment is not fully
planned and monitored. The need for attention to this type of planning and
monitoring is reflected in Specific Goal 3 of the Organizational Process
Focus Process Area. This session will walk through an approach to planning
and monitoring process deployment activities. In addition, types of
measures to monitor adoption of new processes will be discussed. The
session will also provide time for attendees to share their experiences
and successes in relation to deploying new processes in their
organizations.
TRACK
TWO: CMMI & PROCESS IMPROVEMENT
II
CMMI
on the Web v1.2
Shane
McGraw&
Deen
Blash,
Software
Engineering Institute
9:20am - 10:00am
With the abundance of information on CMMI, this presentation will
clarify what is available for organizations starting and maintaining CMMI-based
process improvement initiatives. While your implementation will be unique,
there are definite commonalities for every CMMI implementation. This
presentation will also show that efficiently accessing the available
information has enormous tangible benefits for anyone interested in CMMI-based
process improvement.
CMMI®
Maturity Levels, Not Acting Your Age and Erosion of Continuity - Causes
and Cures
Ken
Dymond,
Process Transition International, Inc
10:30am - 11:20am
Sometimes
a CMMI appraisal is like a chemistry test – once it’s over, life goes
on as usual. The appraisal (the test) is the focus, but production
capability is what customers and suppliers want. A Maturity Level > 1
indicates capability but does not guarantee that customers will see the
expected behavior (acting one’s age). Some causes (poor labeling of the
appraised entity) can be adjusted by a kind of truth-in-labeling and by
educating the customer. Others are inherent in model-based and
appraisal-determined process capability and are more difficult. This
presentation describes factors to help ensure continuity of capability.
Using Failure Mode and Effects
Analysis (FMEA) to Assess Risks to the Global Enterprise due to
Process/Application Changes
Vic Nanda, Motorola
11:20 am - 12:00pm
As
part of a multi-million dollar project, Motorola has undertaken an
ambitious project to redesign the current global architecture for a
business-critical application in order to improve operational efficiencies
and reduce cost of poor quality. The challenge for the quality team was to
proactively identify the risks to the global enterprise due to redesign of
the current architecture, and how to mitigate those risks prior to
implementation of the new architecture. The presentation will describe: 1.
How the FMEA Six Sigma method was enhanced to get a quantifiable measure
of risk to the global enterprise 2. How the risks were analyzed to provide
a prioritized list of improvement recommendations, and 3. How the team
demonstrated quantifiable reduction in enterprise risk if the improvement
recommendations were to be implemented This before and after analysis
(items 1 and 3 above) of the original and reduced enterprise risks, along
with a Pareto analysis of the underlying root causes that posed the most
risk to the enterprise, served as a very effective tool for of presenting
results of this risk assessment exercise to senior management for informed
decision making.
Documentation
Diet
Neil
Potter, The Process Group
2:10pm - 2:50pm
This talk addresses the following crucial topics in any
process improvement initiative: (1) How
to focus on the organization’s current needs and problems and create
documents that serve your organization; (2) How to keep processes short,
to the point, and flexible so that they help individuals do their jobs;
(3) 10 ways to keep processes concise; (4) How to know if you are meeting
the intent of CMMI process areas; (5) What it means to have an SEI
Maturity Level N process; and (6) How to know when you are in
trouble.
CMMI-SVC
: Get Ready… Here it Comes
Craig
Hollenbach, Marilyn
Ginsberg-Finner
& James Blinn,
Northrop Grumman Information Technology, and
Eileen Forrester, Software Engineering Institute
3:20pm - 4:10pm
CMMI for Services (CMMI-SVC) is a CMMI constellation that
covers the activities required to manage, establish, and deliver services.
Currently, some service organizations apply CMMI-DEV to their work, but
this requires significant interpretation. CMMI-SVC is relevant to any
organization concerned with the delivery of services, including
enterprises in sectors such as defense, IT, health care, finance, and
transportation. This presentation provides an overview and will use a Case
Study to prepare attendees to consider the application of the CMMI-SVC to
their environment. The presentation will also address the synergy between
ITIL and the application of CMMI-SVC to IT services.
TRACK
THREE:
TRACK
THREE:
AGILE
& GENERAL TOPICS
Agile
101: An Introduction and Overview
Chris
Sims, Technical Management Institute
9:20am - 10:00am
Agile software development has crossed the chasm and become a
mainstream best practice. Microsoft, Google, Yahoo, and IBM all do agile
development, as do scores of fast-moving start-up companies. Businesses
like agile because it delivers more value in less time. Engineers enjoy
the opportunity to craft high quality code that they can be proud of.
This presentation examines agile methods, uncovering how, why, and when
they work. We will avoid the preachy and focus on the practical, sharing
stories and lessons from real projects. You will hear what worked and what
didn't.
Agile
CMMI: Supercharging process performance Using agile Methods
Jeff
Dalton, Broadsword Solutions Corporation
10:30am
- 11:20am
Is your company trying to roll out yet another process that’s too
heavy, burdensome, and just gets in the way? Are they trying to achieve
CMMI, ISO9001, or ITIL just to get the certificate on the wall?
Come listen to Jeff Dalton, an Agile CMMI Lead Appraiser and creator of
“AgileCMMI” a process methodology based on Agile project management
concepts that will help you deploy useful, rightsized, and agile processes
that will not only reduce your workload, but will allow you to achieve
CMMI.
Attendees will learn how to apply the concepts of incremental releases,
iterations, refactoring, test based design, and incremental design and
development to the deployment of useful processes.
Mixing
Oil With Water (CMMI meets eXtreme Programming)
Stephen
Gristock, Citi
- JPMorganChase / Independent Consultant
11:20am - 12:00pm
eXtreme
Programming (XP) is still widely recognized as an industry standard for
agile development. Developed from more “traditional” I.T. values, the
CMMI provides a proven framework for driving process improvement. On the
face of it, CMMI and XP would appear to be (almost) mutually exclusive.
However, this presentation will demonstrate that it is possible to combine
both disciplines into a powerful tool for driving improvement in the
software engineering domain. Based upon a real-world case study, this
session will provide practical insights into deploying a highly
complementary integrated CMMI/XP solution. All delivered with a dash of
humor.
Using
Automated Frameworks to Facilitate Early and Frequent Testing
Steve
Orlich & Denise Chester, Minitab
Inc.
2:10pm - 2:50pm
Late,
changing, or ambiguous requirements: these facts of software development
have had their share of blame from the software industry for failed or
delayed deliveries. However, the “regression testing cycle” can be one
of the most unpredictable and wasteful periods during the software
development cycle. Waiting until certain periods of time to do regression
testing leads to and promotes many poor development habits. We will review
some specific development techniques that can be used to foster continual
testing that can lead to more predictable software outcomes, better
process, and eliminating the “regression testing cycle” all together.
An
introduction to ITIL V3 and its impact on software processes
Richard
Horwitz, BearingPoint
3:20pm - 4:10pm
Although ITIL has been around for years, only with the release of V3 in
2007 has it taken the IT world by storm. Centered around the concept of
Business Focused IT Services, ITIL V3 provides a comprehensive lifecycle
covering everything from the strategic planning of services, to their
design and release, to the day to day management and continual improvement
of services.
In this session you will learn what each of the five ITIL V3 books
covers, the key concepts they address, and the processes they define. You
will also learn specific steps you can take in your own projects to help
them support the ITIL V3 model.
TRACK
FOUR:
MEASUREMENTS,
ESTIMATION & GENERAL TOPICS
Analyzing
Defects Can Tell a LOT About a Company
Diane
Mizukami-Williams,
Northrop Grumman Corporation
9:20am -10:00am
By analyzing a company’s defect data using statistical
analysis techniques, such as control charts, tests for equal variance,
etc., you can tell a LOT about the company with very limited knowledge
about the company. Since most companies, even small companies, collect
defect data during test, it is the most readily available data that can
provide insight into the company’s maturity level and the quality of
their products. This presentation will use real defect data from a
company, analyze it, and come up with a story about the company based on
defect data alone.
How
can we measure the value of IT?
Michael
Harris,
David Consulting
Group
10:30am - 11:20am
The phrase, “Beauty is in the eye of the beholder,”
could equally well apply to IT value as to beauty. IT consumes more
resources than other functions because of the cost to operate the IT
infrastructure and the ubiquity of IT throughout the organization. How do
you know if you are getting value for money from your IT investments? How
can you tell if you need to make as much investment in IT as you are
making now? This presentation reviews the most frequently used financial
and non-financial measures of IT value.
The
Evolution of Software Size : A Search for Value
Arlene
F. Minkiewicz, PRICE Systems,LLC
11:20am - 12:00pm
Software size measurement continues to be a contentious
issue in the software engineering community. This paper reviews software
sizing methodologies employed through the years, focusing on their uses
and misuses. It covers the journey the software estimating community has
traversed in the quest for finding the right way to assign value to
software solutions, highlighting the detours and missteps along the way.
Readers will gain a fresh perspective on software size: what it really
means and what they can and cannot learn from it.
Secure
SDLCs Compared
Kenneth
R. van Wyk, KRvW Associates, LLC
2:10pm - 2:50pm
Several secure software development processes have been
published in the past few years. These include Microsoft's Secure
Development Lifecycle, Cigital's "Touchpoints", and OWASP's own
CLASP project. Which one is right for your organization, or would your
needs be best served by taking the best of each and coming up with
"your own" process? In this talk, we'll compare and contrast
each of these approaches and talk about the practical aspects of putting
them to maximum use, including pitfalls to avoid.
Design
of IT Release Management Process using Blended DMAIC & DFSS
Methodology
Neeraj
Katare & Dr.Prasad Chitimalla,
Tata Consultancy Services Ltd
Inefficient and inconsistent software release processes
have persisted for long and was a major cause for setbacks in the IT
environment. While the current process was disjointed and different
functions within the organization perceived the process differently, it
also lacked clearly defined ownership. The team used a blended approach of
both DMAIC and DFSS first to understand the existing process, establish
process performance baseline, and perform root-cause analysis and later to
design the new release process using the principles of process design.
This demonstrates how one can resolve a real customer problem by bringing
best of both methodologies together.
TRACK
FIVE:
ORGANIZATIONS & PEOPLE and GENERAL TOPICS
Organizational
Change Management (OCM) the missing PA (Process Area)
William
C McKnight, Next Level Consultants
9:20am - 10:00am
The benefit of compliance to the CMMI can not be realized if an
organization is unable to adapt the behavior of its people to comply with
their defined process. This presentation will define the Goals and
Practices of Organizational Change Management, describing the “what”
so organizations can define the “how” that will enable change within
their organization. All the material delivered will be supported by
accepted theories in change management. The goals identified will be
compatible with recognized three-step change processes first introduced by
Kurt Lewin in 1947 This model of change is based on the theory that change
occurs through three phases, commonly referred to as unfreeze, change, and
refreeze.
From
Grass Roots to Executive Enthusiasm - The Inside Job of Selling CMMI
Rob Donnellan,
Q/P Management Group
10:30am - 11:20am
Without ongoing support from key stakeholders, and especially senior
management, process improvement initiatives are unlikely to succeed.
However, acquiring internal commitment to initiatives is neglected
surprisingly often. The result: cancellations, delays, resources
reductions, and organizations reduced to just superficial activities.
This presentation will discuss in general the how-to for internal
selling of improvement initiatives, and specifically the issues related to
selling the CMMI®. Topics will include: The bad things that happen when
you don’t sell internally; Internal selling steps; How to tell if it’s
working; and Specific issues related to selling CMMI.
Improvement
in Four Dimensions
John
H. Maher, Jr.,
Organization & Process Improvement, Inc.
11:20am - 12:00pm
Improving sustainably … in an organization… with a
culture…where people must change habits…to accomplish management goals…in
a specified time…isn’t a walk in the park. Four disciplines—what to
improve, how to improve, how to adapt to an organizational context, and
how to effect real change—comprise a critical set of knowledge and
skills for guiding an improvement effort. In this session we’ll look at
a core set of models in each dimension that anyone implementing
improvement must know how to apply in today’s complex environments.
Test
Driven Architecture
Joseph
N Frisina, BAE Systems
2:10pm - 2:50pm
We can usually agree that good software architecture is essential to
the development of a good software product. But what makes good software
architecture? How do we tell if we have a good architecture? Why
Generating a good Software Architecture remains wrapped in mystery because
we have many different voices each crying-out there particular approach.
We assert that having a good architecture is important but give little
guidance on how to achieve a good architecture. What this article provides
is a method to achieve good software architecture based upon a reversal of
the Software Engineering Institute’s Architectural Trade-off Analysis
Method (ATAM). With the approach provided you can guarantee the ‘goodness’
of your architecture for the intended purpose.
Importance
of Traceability to Design for White Box Testing
Alice
C Brown, Haemonetics, Inc.
3:20pm - 4:10pm
Too often products are released into the field with
inadequate testing. When the failures occur, the root cause analysis shows
that there was not enough attention paid at the interfaces, at the
detailed level of design. Why? One reason is because there are so few
standards regarding the granularity necessary in performing a trace.
Another is that too few companies require a trace from software
requirements to design to test cases and test procedures. This paper will
deal with white box testing and how a thorough trace including ‘completeness’
as an evaluation criterion will produce at much less cost in money and
company reputation, a quality product. References will be made to the CMMI,
automated testing tools and how essential continual refinement of the
review process is. Problems encountered and warnings concerning ‘informed
reviewers’ are also included. The attendees will be given a list of
dangerous ambiguities and important ‘whys’ to substantiate the
additional cost of design traceability to take home to their management.
______________________________
SM SEI, SCAMPI, SCAMPI Lead Assessor, and SCAMPI Lead
Appraiser are service marks of Carnegie Mellon University.
®CMMI and CMM are registered in the US Patent and Trademark
office by Carnegie Mellon University.
®ITIL is a Registered Trade Mark and a Registered Community Trade Mark of the Office of Government Commerce and is Registered in the U.S. Patent and Trademark Office.
|
