SlideShare ist ein Scribd-Unternehmen logo
1 von 11
Downloaden Sie, um offline zu lesen
Mitigating risk in the software delivery
lifecycle
August 2009




                                           Lowering business costs: Mitigating
                                           risk in the software delivery lifecycle




                                           Roberto Argento
                                           IBM Rational Business Development Executive

                                           Valerie Hamilton
                                           IBM Rational Solution Marketing Manager and Certified
                                           Senior IT Specialist
Mitigating risk in the software delivery
lifecycle
Page 2




                                              Introduction
                    Contents                  In today’s challenging economy, businesses are under increased pressures to
                                              reduce overall costs while mitigating and controlling risks. The reality is that
    2   Introduction                          many businesses continue to struggle to successfully deliver quality software
    3   Defining software delivery risks      on time and on budget that meets their market needs. One study states that, on
    3   Balancing risks with value            average, 32% of projects do not align with company goals and 39% of projects
    5   The cost of failure                   are over budget.1 Such surprising statistics only touch the surface of the
    6   Building the right thing:             software delivery problems faced by businesses today.
        Requirements management
    8   Visibility into project and process   Other studies confirm that success rates are not improving; software delivery
        outcomes: Performance                 challenges continue to adversely affect business costs. According to the
        measurement and management            Standish Group, businesses continue to struggle with project success rates and
    10 Conclusion                             failures. Their latest published Chaos Report 2 states that “this year’s results
                                              show a marked decrease in project success rates, with 32% of all projects
                                              succeeding which are delivered on time, on budget, with required features and
                                              functions”. Additionally, “44% were challenged which are late, over budget,
                                              and/or with less than the required features and functions and 24% failed which
                                              are cancelled prior to completion or delivered and never used.”3 The numbers
                                              are staggering.


                                              Why is it so difficult to deliver quality software on time and on budget that
                                              aligns to the business goals? Imagine if “wasted” resources and dollars lost on
                                              software delivery failures could be used to innovate — to create new products
                                              or to pursue new market opportunities. Think of the positive impact to the
                                              business’s bottom-line. There are plenty of businesses that, by mitigating
                                              risks and having a systematic (but not bureaucratic) approach to the software
                                              delivery process, have achieved improvements in their success rates leading
                                              to a decrease in their development costs and a better and greater impact to
                                              their business outcome. In this paper, you will learn how requirements and
                                              performance management can help to reduce risks and lower business costs by:


                                              •	   Achieving consensus on project requirements and delivering quality products
                                                   that meet stakeholder’s business needs
                                              •	   Understanding the impact of changes to your deliverables and having the
                                                   ability to accurately track and communicate these changes
                                              •	   Providing the ability to analyze, monitor, and trend project status across the
                                                   entire software lifecycle for objective and informed decision making
                                              •	   Assessing and measuring process and project performance to drive continual
                                                   process improvements
Mitigating risk in the software delivery
lifecycle
Page 3




                                              Defining software delivery risks
                   Highlights                 In everyday life a risk is an exposure to loss or injury: A factor, thing, element,
                                              or course involving some degree of danger. Similarly, in software development
                                              a risk is something that can compromise the success of a project. Examples of
                                              potential sources of risk in software delivery are listed below:


                                              •	   Missing, incomplete or changing requirements and specifications
                                              •	   Manual or undefined development processes and practices
                                              •	   Incomplete testing and validation
                                              •	   Lack of stakeolder input
                                              •	   Disconnected distributed teams
                                              •	   Project interdependencies and lack of team collaboration
                                              •	   Changes to regulatory compliance
                                              •	   Insufficient time or schedule expectations
                                              •	   Unclear business goals and objectives


    Making informed decisions by              Making informed decisions by consciously assessing what can go wrong, as
    consciously assessing what can go         well as the likelihood and severity of the impact, is at the heart of defining
    wrong, as well as the likelihood and      software delivery risks. Risks are exposed and can be addressed through the
    severity of the impact, is at the heart   identification, analysis, planning, tracking, controlling, and communication of
    of defining software delivery risks.      the software delivery lifecycle.



                                              Balancing risks with value
                                              Risk is a potential manifestation of the likelihood of unexpected things
                                              happening to the project, and risk stands in the way of value creation. Every
                                              project carries an amount of risk. If project risks are not identified and
                                              addressed, there is a very real chance that they will arise at some point in
                                              the project lifespan. The longer a risk goes unnoticed, the more costly it
                                              is to correct. Risk is directly proportional to uncertainty in estimates, and
                                              stakeholders typically want to know sooner rather than later what value the
                                              project can deliver in the stipulated time. In many cases, you reduce risk when
                                              you create value by implementing and testing the most critical capabilities.


                                              Risk-driven development focuses on identifying high risk areas and addressing
                                              those items early in the project lifespan. The goal is to flush these issues out
                                              early before you spend a considerable amount of time on project development
                                              and any re-work is required.
Mitigating risk in the software delivery
lifecycle
Page 4




                                           Value-driven development focuses on identifying those features most
                   Highlights              important to the customer and business, and completing those items early
                                           so the stakeholders can see progress as well as provide feedback on those
                                           features early and on-going.


                                           Risk-driven development recommends focusing on those high risks areas
                                           that are critical to the success of the project, while value-driven development
                                           focuses on those functional requirements perceived to be of high value to
                                           the stakeholders.


    The risk response requires careful     Risk response should be in proportion to the significance of the risk.
    balancing of competing priorities to   However, there are situations where risks and business value are at odds
    maximize stakeholder value.            with each other. Thus, the risk response requires careful balancing of these
                                           competing priorities to maximize stakeholder value. A risk-driven iterative
                                           approach involves iterations that strike a balance between high-risk issues
                                           crucial to the project and features that bring value (see Figure 1).




                                           Figure 1: A risk-driven iterative approach balances risks with value
Mitigating risk in the software delivery
lifecycle
Page 5




                                            In reviewing the project lifecycle phases (Inception, Elaboration, Construction and
                     Highlights             Transition) shown in Figure 1, risks are normally higher in the Inception phase,
                                            and they continue to decline over subsequent project lifecycle phases as risks
                                            are identified and addressed. In the Inception phase the initial risk assessment
                                            is performed and core project requirements and key features are defined. In the
                                            Elaboration phase, the primary objective is to mitigate the key risk items identi-
                                            fied by analysis. The Elaboration phase is where the project starts to take shape:
                                            the problem domain analysis is made and the architecture of the project gets its
                                            basic form. This is the phase where there is a balance between risk and features
                                            that are perceived to be of high value to the stakeholders. Creating value by
                                            reducing uncertainty is the best way to reduce costs and improve project success.



                                            The cost of failure
                                            Software delivery is a team-based activity. In order to avoid the high cost of
                                            failure teams must work together to mitigate and manage risks for successful
                                            outcomes to the business. To avoid the high costs of failure and reduce risks,
                                            there must be repeatable, predictable processes and best practices in place
                                            throughout the software delivery lifecycle that improve productivity and
                                            quality.
    Stakeholders typically have an
    abstract idea of what they want as an   Typical software delivery activities include requirements elicitation,
    end result, but not what the software   planning, design, implementation, testing, documentation, deployment, and
    should do. Project requirements need    maintenance. With so many activities of the software delivery lifecycle, it is no
    to be accessible so that all team       wonder that failures frequently occur.
    members understand their part of the
    whole project.                          “Requirements elicitation” refers to those activities focused on understanding
                                            your stakeholders’ business goals and objectives, which serve as the starting
                                            point for gathering project requirements. Only when you understand the
                                            business goals and objectives can you begin defining a solution that will solve
                                            stakeholders’ business needs.


                                            The planning phase within the software delivery lifecycle involves the
                                            important task of defining the requirements or requirements analysis.
                                            Stakeholders typically have an abstract idea of what they want as an end result,
                                            but not what the software should do. Project requirements need to be accessible
                                            so that all team members understand their part of the whole project and are
                                            informed as changes occur.
Mitigating risk in the software delivery
lifecycle
Page 6




                                              Missing requirements is one of the biggest contributors to schedule delays and
                   Highlights                 budget overruns; there’s nothing worse than being half way done with a project
                                              and then realizing a major stakeholder need has not even been addressed.
                                              Incomplete, ambiguous, or even contradictory requirements need to be
                                              analyzed and extracted prior to defining the scope of a project.


    Making changes to a deployed system       Requirements analysis and management is a high-leverage activity because
    is much more costly than getting it       making changes to a deployed system is much more costly than getting it right
    right the first time. The immense cost    the first time. The immense cost associated with reworking existing code and
    associated with reworking existing        tests when requirement errors are identified is one of the key areas of risk in the
    code is one of the key areas of risk in   software delivery lifecycle.
    the software delivery lifecycle.
                                              Organizations must have the ability to review, assess, and improve current proc-
                                              esses within each phase of the software delivery lifecycle. Having accurate insight
                                              into enterprise data, processes, and practices is a key component of success. How-
    Measuring project and process out-        ever, many organizations suffer from a lack of visibility into the software delivery
    comes allows for continual process        lifecycle. Additionally, they struggle with data gaps and manually created metrics,
    improvements across the software          which creates data blind spots that put an organization’s success at risk. Measuring
    delivery lifecycle, which reduces         project and process outcomes allows for continual process improvements across
    project failures and lowers business      the software delivery lifecycle, which reduces project failures and lowers business
    costs.                                    costs.



                                              Building the right thing: Requirements management
                                              Requirements management is the process of eliciting, defining, elaborating,
                                              documenting, analyzing, prioritizing, and agreeing on requirements and then
                                              controlling changes over the course of a project to ensure that deliverables
                                              remain aligned to the stakeholders’ goals. Requirements management thus
                                              helps ensure that risks are minimized, stakeholder problems are solved, and
                                              business costs are lowered.


                                              What is so hard about requirements management? Words can be ambiguous.
                                              It is difficult to clearly communicate a vision to all team members. It is
                                              complicated to show relationships or dependencies between requirements.
                                              Requirements come in a variety of shapes and sizes. Some may be more
                                              complex, more risky, more important, or less stable than others, and the
                                              sheer number of requirements can be grueling to manage. But most of all,
                                              requirements frequently change.
Mitigating risk in the software delivery
lifecycle
Page 7




                                           Understanding the impact of changes to other requirements and to your project,
                  Highlights               then tracking and communicating those changes to all team members, is one of
                                           the greatest challenges in the requirements management discipline.


                                           It is clear that doing things right can take us down a path of risk mitigation and
                                           value creation. But how do we know when we are doing the right things?


                                           When evaluating fourteen software development and delivery projects in six coun-
                                           tries of Latin America (Mexico, Brazil, Chile, Argentina, Peru, and Colombia), in
                                           different sectors of the economy (finance, insurance, telecom, ISVs, government
                                           agencies, and energy) and covering several technology platforms (mainframe, Java
                                           development, creation of new products, and ERP maintenance), we discovered a
                                           common problem: a pervasive lack of effective requirements management.


                                           Each of the projects presented a variety of requirements issues, including the
                                           inability to properly test or validate functionality, rework and churn due to
                                           constant change of features and functionality, and high development costs. The
                                           fact was that all projects invested very little time in planning and managing their
                                           requirements.


                                           The conclusion of this project evaluation is that most organizations are very good
    Most organizations are very good at    at proposing new ideas and solutions. But they are commonly ineffective in plan-
    proposing new ideas and solutions.     ning and managing requirements and executing software delivery with reduced
    But they are commonly ineffective in   risks and costs.
    planning and managing requirements.
                                           CIO Magazine reported that “as many as 71% of software projects that fail do so
                                           because of poor requirements management, making it the single biggest reason for
                                           project failure.”4 Domain experts such as Rikki Kirzner cite the need for require-
                                           ments management for project success. He was quoted in a recent article:


                                             The successful outcome of any project starts with defining, creating, and distrib-
                                             uting project requirements in a form where all stakeholders can easily access,
                                             collaborate, and contribute to creating requirements. While this seems simple
                                             enough to explain, time and again, good intentions are undermined by the
                                             capabilities of the tools you are using and the environment in which you are
                                             working. This situation only exacerbates the problems encountered when all the
                                             stakeholders don’t understand the original business intent, goals, or cannot con-
                                             nect those goals with what the team is doing. Geographic dispersion, communi-
                                             cation difficulties and conflicting priorities can also cause problems.5
Mitigating risk in the software delivery
lifecycle
Page 8




                                           One of the core principles of requirements management is promoting team
                  Highlights               collaboration. It is imperative to make the requirements accessible to every-
                                           one on the team, thus facilitating team collaboration and providing visibility
                                           to the impact of change.


                                           IBM has found that the investment in a requirements management solution,
                                           such as IBM Rational Requirements Composer, IBM Rational RequisitePro,
                                           or IBM Rational Doors facilitates team collaboration and helps implement
                                           requirements management best practices. This in turn reduces costs and
                                           helps mitigate risks. Rational Requirements Composer is a collaborative
                                           requirements definition and management solution, perfect for teams that
                                           want to focus on definition and need “just enough” requirements manage-
                                           ment. It provides textual and visual techniques to elicit, elaborate, and vali-
                                           date requirements collaboratively with your stakeholders, and it helps deliver
                                           quality solutions that meet their business and product requirements. Both
                                           Rational RequisitePro and Rational Doors provide traceability and impact
                                           analysis that keeps analysts, architects, developers, and testers aligned to
                                           business needs and requirements throughout the software delivery lifecycle.



                                           Visibility into project and process outcomes: Performance measurement and
                                           management
                                           Performance measurement and management helps software delivery teams make
                                           the right decisions by providing deeper insight into an organization. It enables
                                           organizations to measure, monitor, and analyze project and process performance
                                           against business objectives for trending, to identify issues, and to drive continuous
                                           process improvement.


                                           When data is gathered manually, when it comes from different sources that may
                                           not align, or where there is an inability to gather information from the various
                                           teams (thus creating data silos), it is nearly impossible to make the right deci-
                                           sions for an organization. It becomes hard to react to organizational and market
                                           changes, and to measure the effectiveness of processes and practices to improve
                                           them. And of course, this ineffectiveness can directly impact costs and business
                                           risks.
Mitigating risk in the software delivery
lifecycle
Page 9




                                           You cannot improve what you cannot measure. Raising the visibility into an
                  Highlights               organization by having real-time information in a single view across the various
                                           projects, products, and geographical boundaries helps project teams to review,
    You cannot improve what you cannot     assess, and improve current processes within each phase of the software delivery
    measure. Real-time information         lifecycle.
    in a single view across various
    projects, products, and geographical   Having access to the right data at the right time helps organizations make objec-
    boundaries helps project teams to      tive and informed decisions. They are able to measure organizational effectiveness
    review, assess, and improve current    to improve processes and practices, which not only increases efficiency and speed,
    processes.                             but allows for quick detection of problems and continual status monitoring for
                                           reduced costs and risks.


                                           IBM Rational Insight, a performance measure and management solution, allows
    Measuring organizational               organizations to measure, monitor, analyze, and trend project and process per-
    effectiveness improves processes       formance as well as continually improve organizational outcomes through process
    and practices, which not only          improvements. It eliminates inefficient time wasted on manual data collection
    increases efficiency and speed, but    through automatic collection of data presented in a single view. Rational Insight
    allows quick detection of problems.    also helps deliver the IBM Measured Capability Improvement Framework (known
                                           as MCIF) for process improvement and best practice guidance. This aligns guid-
                                           ance with performance measurement for faster improvements to an organization,
                                           thus lowering costs while raising team capabilities.
Mitigating risk in the software delivery
lifecycle
Page 10




                                           Conclusion
                     Highlights            Lowering business costs by mitigating risks in the software delivery lifecycle is not
                                           simply an aspiration among businesses today. During these challenging economic
                                           times, it is imperative to improve the success rate of projects with reduced costs.
                                           Improving the success rate of projects requires that teams focus on business
                                           outcomes, become as productive as possible, and mitigate risks with proven tools
                                           and techniques. This requires the right mix of information, collaboration, and
                                           automation — all at the right time.


                                           Successful leaders will leverage innovation to help them seize business opportuni-
    Successful leaders will leverage       ties, manage to objectives, and execute with reduced cost and risk. To drive busi-
    innovation to help them seize          ness transformation, companies need greater agility and responsiveness from their
    business opportunities, manage to      teams. They demand greater differentiation in their products and services in order
    objectives, and execute with reduced   to surpass the competition and increase profits.
    cost and risk.
                                           Requirements management helps achieve consensus with your stakeholders. It
                                           focuses on the ability to deliver quality solutions that align project deliverables to
                                           stakeholder business needs.


                                           Performance measurement and management helps to monitor, analyze and trend
                                           process, resources, and project outcomes to drive execution of projects and proc-
                                           esses with consistent and predictable results.


                                           Doing the right thing means to be able to:
                                           •	 Reduce risks across the software delivery lifecycle through team collaboration
                                               to clarify actual business issues, increase individual and team productivity,
                                               compress development cycles, and rapidly deliver high-quality software
                                           •	 Make better decisions based on real-time, accurate information and consen-
                                               sus across stakeholders
                                           •	 Drive faster project delivery by providing requirements collaboration, history
                                               and context that team members need to reduce rework, and allow for efficient
                                               reuse of requirements artifacts for future projects
                                           •	 Iterate quickly by analyzing and managing change for continual alignment
                                               with business priorities.
Endnotes                                                                                      © Copyright IBM Corporation 2009

                                                                                              IBM Corporation

1.   IDC Whitepaper: How Project and Portfolio Management Solutions Are Delivering Value to   Software Group

     Organizations, September 2008                                                            Route 100

2.   Standish Group Chaos Report, CHAOS Summary 2009                                          Somers, NY 10589

3.   “The Standish Group” - http://www.standishgroup.com/newsroom/chaos_2009.php              U.S.A.

4.   Christopher Lindquist, “Fixing the Requirements Mess,” in CIO Magazine, Nov. 15, 2005

5.   Rikki Kirzner, “Requirements Management: A Core Part of the Development Lifecycle,”      Produced in the United States of America

     DevX.com, Aug 8, 2008, at http://www.devx.com/ibm/Article/38819/4047                     August 2009

                                                                                              All Rights Reserved



                                                                                              IBM, the IBM logo, ibm.com, Rational, IBM Rational

                                                                                              Requirements Composer, IBM Rational RequisitePro,

                                                                                              IBM Rational Insight and IBM Measured Capability

                                                                                              Improvement Framework are trademarks or registered

                                                                                              trademarks of International Business Machines

                                                                                              Corporation in the United States, other countries, or

                                                                                              both. Other company, product, or service names may

                                                                                              be trademarks of IBM or other companies.



                                                                                              A current list of IBM trademarks is available on the

                                                                                              Web at “Copyright and trademark information” at

                                                                                              www.ibm.com/legal/copytrade.shtml



                                                                                              The information contained in this document is

                                                                                              provided for informational purposes only. While

                                                                                              efforts were made to verify the completeness

                                                                                              and accuracy of the information contained in this

                                                                                              documentation, it is provided “as is” without warranty

                                                                                              of any kind, express or implied.




                                                                                              RAW14172-USEN-00

Weitere ähnliche Inhalte

Was ist angesagt?

Project Management Discipline - Brown Bag CXB V03 Jun 2009 SAN
Project Management Discipline - Brown Bag CXB V03 Jun 2009 SANProject Management Discipline - Brown Bag CXB V03 Jun 2009 SAN
Project Management Discipline - Brown Bag CXB V03 Jun 2009 SANcj_barbosa
 
Risk Management of PPP
Risk Management of PPPRisk Management of PPP
Risk Management of PPPRupertBooth
 
Project Iniation And Setup
Project Iniation And SetupProject Iniation And Setup
Project Iniation And SetupSpinnaker_Group
 
Managing Dependencies
Managing DependenciesManaging Dependencies
Managing DependenciesJohn Phillips
 
Planning For Disaster And Everyday Threats Wp111438
Planning For Disaster And Everyday Threats Wp111438Planning For Disaster And Everyday Threats Wp111438
Planning For Disaster And Everyday Threats Wp111438Erik Ginalick
 
Macrosolutions Consulting Service: Structuring the Risks Management Processes
Macrosolutions Consulting Service: Structuring the Risks Management ProcessesMacrosolutions Consulting Service: Structuring the Risks Management Processes
Macrosolutions Consulting Service: Structuring the Risks Management ProcessesMacrosolutions SA
 
PM Chapter on Agile IT Project Management Methods
PM Chapter on Agile IT Project Management MethodsPM Chapter on Agile IT Project Management Methods
PM Chapter on Agile IT Project Management MethodsGlen Alleman
 
Agile - Agile Software Project Management Methodologies
Agile - Agile Software Project Management MethodologiesAgile - Agile Software Project Management Methodologies
Agile - Agile Software Project Management MethodologiesRam Srivastava
 
Agile in an ANSI-748-C environment
Agile in an ANSI-748-C environmentAgile in an ANSI-748-C environment
Agile in an ANSI-748-C environmentGlen Alleman
 
Success mgt client april 12 (2)
Success mgt client april 12 (2)Success mgt client april 12 (2)
Success mgt client april 12 (2)Roy Dunster
 
Technology enabled business change projects
Technology enabled business change projectsTechnology enabled business change projects
Technology enabled business change projectsJohn Phillips
 
Bahrs.peter
Bahrs.peterBahrs.peter
Bahrs.peterNASAPMC
 
A risk management framework for distributed scrum using PRINCE2 methodology
A risk management framework for distributed scrum using PRINCE2 methodologyA risk management framework for distributed scrum using PRINCE2 methodology
A risk management framework for distributed scrum using PRINCE2 methodologyjournalBEEI
 
Carol scottcowartmcphillipspm challengefinal
Carol scottcowartmcphillipspm challengefinalCarol scottcowartmcphillipspm challengefinal
Carol scottcowartmcphillipspm challengefinalNASAPMC
 
AACE Presentation Final 2007
AACE Presentation Final 2007AACE Presentation Final 2007
AACE Presentation Final 2007janknopfler
 

Was ist angesagt? (20)

Project Management Discipline - Brown Bag CXB V03 Jun 2009 SAN
Project Management Discipline - Brown Bag CXB V03 Jun 2009 SANProject Management Discipline - Brown Bag CXB V03 Jun 2009 SAN
Project Management Discipline - Brown Bag CXB V03 Jun 2009 SAN
 
Risk Management of PPP
Risk Management of PPPRisk Management of PPP
Risk Management of PPP
 
Agile development
Agile developmentAgile development
Agile development
 
Project Iniation And Setup
Project Iniation And SetupProject Iniation And Setup
Project Iniation And Setup
 
Why Agile?
Why Agile?Why Agile?
Why Agile?
 
Managing Dependencies
Managing DependenciesManaging Dependencies
Managing Dependencies
 
MCP1
MCP1MCP1
MCP1
 
Planning For Disaster And Everyday Threats Wp111438
Planning For Disaster And Everyday Threats Wp111438Planning For Disaster And Everyday Threats Wp111438
Planning For Disaster And Everyday Threats Wp111438
 
Macrosolutions Consulting Service: Structuring the Risks Management Processes
Macrosolutions Consulting Service: Structuring the Risks Management ProcessesMacrosolutions Consulting Service: Structuring the Risks Management Processes
Macrosolutions Consulting Service: Structuring the Risks Management Processes
 
PM Chapter on Agile IT Project Management Methods
PM Chapter on Agile IT Project Management MethodsPM Chapter on Agile IT Project Management Methods
PM Chapter on Agile IT Project Management Methods
 
Cio software testing_survey
Cio software testing_surveyCio software testing_survey
Cio software testing_survey
 
Agile - Agile Software Project Management Methodologies
Agile - Agile Software Project Management MethodologiesAgile - Agile Software Project Management Methodologies
Agile - Agile Software Project Management Methodologies
 
Agile in an ANSI-748-C environment
Agile in an ANSI-748-C environmentAgile in an ANSI-748-C environment
Agile in an ANSI-748-C environment
 
Success mgt client april 12 (2)
Success mgt client april 12 (2)Success mgt client april 12 (2)
Success mgt client april 12 (2)
 
Technology enabled business change projects
Technology enabled business change projectsTechnology enabled business change projects
Technology enabled business change projects
 
Risk Management
Risk ManagementRisk Management
Risk Management
 
Bahrs.peter
Bahrs.peterBahrs.peter
Bahrs.peter
 
A risk management framework for distributed scrum using PRINCE2 methodology
A risk management framework for distributed scrum using PRINCE2 methodologyA risk management framework for distributed scrum using PRINCE2 methodology
A risk management framework for distributed scrum using PRINCE2 methodology
 
Carol scottcowartmcphillipspm challengefinal
Carol scottcowartmcphillipspm challengefinalCarol scottcowartmcphillipspm challengefinal
Carol scottcowartmcphillipspm challengefinal
 
AACE Presentation Final 2007
AACE Presentation Final 2007AACE Presentation Final 2007
AACE Presentation Final 2007
 

Andere mochten auch

Facebook Month-To-Month – April 2014
Facebook Month-To-Month – April 2014Facebook Month-To-Month – April 2014
Facebook Month-To-Month – April 2014NapoleonCat.com
 
Ingenieria del software 7ma. ed. ian sommerville
Ingenieria del software 7ma. ed.   ian sommervilleIngenieria del software 7ma. ed.   ian sommerville
Ingenieria del software 7ma. ed. ian sommervilleFrancisco Mora
 
Social Brand Footprint - sierpień 2013
Social Brand Footprint - sierpień 2013Social Brand Footprint - sierpień 2013
Social Brand Footprint - sierpień 2013NapoleonCat.com
 
бібліотека +читач
бібліотека +читачбібліотека +читач
бібліотека +читачМарина Жук
 
Supercharging IBM Websphere with IBM Rational software
Supercharging IBM Websphere with IBM Rational softwareSupercharging IBM Websphere with IBM Rational software
Supercharging IBM Websphere with IBM Rational softwareIBM Rational software
 
Cover g it si-bos
Cover g it si-bosCover g it si-bos
Cover g it si-bossulfikar354
 
Lab 1: Importing a Microsoft Word file as a module
Lab 1: Importing a Microsoft Word file as a moduleLab 1: Importing a Microsoft Word file as a module
Lab 1: Importing a Microsoft Word file as a moduleIBM Rational software
 
Servicios publicos accesibles para todos-JC Valero
Servicios publicos accesibles para todos-JC ValeroServicios publicos accesibles para todos-JC Valero
Servicios publicos accesibles para todos-JC ValeroJCCM1925
 
Our World: The Razors Edge
Our World: The Razors EdgeOur World: The Razors Edge
Our World: The Razors EdgeKevin Thomason
 
真6 -祖父的小提琴
真6 -祖父的小提琴真6 -祖父的小提琴
真6 -祖父的小提琴childrenmeeting
 
How to Build Your Brand with UC
How to Build Your Brand with UCHow to Build Your Brand with UC
How to Build Your Brand with UCDigium
 
Napoleon - raport aktywności branż na facebooku - marzec 2012
Napoleon - raport aktywności branż na facebooku - marzec 2012Napoleon - raport aktywności branż na facebooku - marzec 2012
Napoleon - raport aktywności branż na facebooku - marzec 2012NapoleonCat.com
 
ΑΝΝΑ ΦΡΑΝΚ. ΚΕΙΜΕΝΑ ΝΕΟΕΛΛΗΝΙΚΗΣ ΛΟΓΟΤΕΧΝΙΑΣ. ΥΠΕΥΘΥΝΗ ΚΑΘΗΓΗΤΡΙΑ: ΖΑΡΚΟΓΙΑΝΝ...
ΑΝΝΑ ΦΡΑΝΚ. ΚΕΙΜΕΝΑ ΝΕΟΕΛΛΗΝΙΚΗΣ ΛΟΓΟΤΕΧΝΙΑΣ. ΥΠΕΥΘΥΝΗ ΚΑΘΗΓΗΤΡΙΑ: ΖΑΡΚΟΓΙΑΝΝ...ΑΝΝΑ ΦΡΑΝΚ. ΚΕΙΜΕΝΑ ΝΕΟΕΛΛΗΝΙΚΗΣ ΛΟΓΟΤΕΧΝΙΑΣ. ΥΠΕΥΘΥΝΗ ΚΑΘΗΓΗΤΡΙΑ: ΖΑΡΚΟΓΙΑΝΝ...
ΑΝΝΑ ΦΡΑΝΚ. ΚΕΙΜΕΝΑ ΝΕΟΕΛΛΗΝΙΚΗΣ ΛΟΓΟΤΕΧΝΙΑΣ. ΥΠΕΥΘΥΝΗ ΚΑΘΗΓΗΤΡΙΑ: ΖΑΡΚΟΓΙΑΝΝ...Εύα Ζαρκογιάννη
 
Facebook age breakdown by country 2014-03
Facebook age breakdown by country 2014-03Facebook age breakdown by country 2014-03
Facebook age breakdown by country 2014-03NapoleonCat.com
 
Preservation and Research Data at Binghamton University Libraries by Edward C...
Preservation and Research Data at Binghamton University Libraries by Edward C...Preservation and Research Data at Binghamton University Libraries by Edward C...
Preservation and Research Data at Binghamton University Libraries by Edward C...Charles Lyons
 

Andere mochten auch (20)

Facebook Month-To-Month – April 2014
Facebook Month-To-Month – April 2014Facebook Month-To-Month – April 2014
Facebook Month-To-Month – April 2014
 
Scifood lecture
Scifood lectureScifood lecture
Scifood lecture
 
Ingenieria del software 7ma. ed. ian sommerville
Ingenieria del software 7ma. ed.   ian sommervilleIngenieria del software 7ma. ed.   ian sommerville
Ingenieria del software 7ma. ed. ian sommerville
 
Proposal HunianOnline
Proposal HunianOnlineProposal HunianOnline
Proposal HunianOnline
 
Social Brand Footprint - sierpień 2013
Social Brand Footprint - sierpień 2013Social Brand Footprint - sierpień 2013
Social Brand Footprint - sierpień 2013
 
Dez1
Dez1Dez1
Dez1
 
бібліотека +читач
бібліотека +читачбібліотека +читач
бібліотека +читач
 
Supercharging IBM Websphere with IBM Rational software
Supercharging IBM Websphere with IBM Rational softwareSupercharging IBM Websphere with IBM Rational software
Supercharging IBM Websphere with IBM Rational software
 
Ny under oslo presentasjon
Ny under oslo presentasjonNy under oslo presentasjon
Ny under oslo presentasjon
 
Cover g it si-bos
Cover g it si-bosCover g it si-bos
Cover g it si-bos
 
Juayderito
JuayderitoJuayderito
Juayderito
 
Lab 1: Importing a Microsoft Word file as a module
Lab 1: Importing a Microsoft Word file as a moduleLab 1: Importing a Microsoft Word file as a module
Lab 1: Importing a Microsoft Word file as a module
 
Servicios publicos accesibles para todos-JC Valero
Servicios publicos accesibles para todos-JC ValeroServicios publicos accesibles para todos-JC Valero
Servicios publicos accesibles para todos-JC Valero
 
Our World: The Razors Edge
Our World: The Razors EdgeOur World: The Razors Edge
Our World: The Razors Edge
 
真6 -祖父的小提琴
真6 -祖父的小提琴真6 -祖父的小提琴
真6 -祖父的小提琴
 
How to Build Your Brand with UC
How to Build Your Brand with UCHow to Build Your Brand with UC
How to Build Your Brand with UC
 
Napoleon - raport aktywności branż na facebooku - marzec 2012
Napoleon - raport aktywności branż na facebooku - marzec 2012Napoleon - raport aktywności branż na facebooku - marzec 2012
Napoleon - raport aktywności branż na facebooku - marzec 2012
 
ΑΝΝΑ ΦΡΑΝΚ. ΚΕΙΜΕΝΑ ΝΕΟΕΛΛΗΝΙΚΗΣ ΛΟΓΟΤΕΧΝΙΑΣ. ΥΠΕΥΘΥΝΗ ΚΑΘΗΓΗΤΡΙΑ: ΖΑΡΚΟΓΙΑΝΝ...
ΑΝΝΑ ΦΡΑΝΚ. ΚΕΙΜΕΝΑ ΝΕΟΕΛΛΗΝΙΚΗΣ ΛΟΓΟΤΕΧΝΙΑΣ. ΥΠΕΥΘΥΝΗ ΚΑΘΗΓΗΤΡΙΑ: ΖΑΡΚΟΓΙΑΝΝ...ΑΝΝΑ ΦΡΑΝΚ. ΚΕΙΜΕΝΑ ΝΕΟΕΛΛΗΝΙΚΗΣ ΛΟΓΟΤΕΧΝΙΑΣ. ΥΠΕΥΘΥΝΗ ΚΑΘΗΓΗΤΡΙΑ: ΖΑΡΚΟΓΙΑΝΝ...
ΑΝΝΑ ΦΡΑΝΚ. ΚΕΙΜΕΝΑ ΝΕΟΕΛΛΗΝΙΚΗΣ ΛΟΓΟΤΕΧΝΙΑΣ. ΥΠΕΥΘΥΝΗ ΚΑΘΗΓΗΤΡΙΑ: ΖΑΡΚΟΓΙΑΝΝ...
 
Facebook age breakdown by country 2014-03
Facebook age breakdown by country 2014-03Facebook age breakdown by country 2014-03
Facebook age breakdown by country 2014-03
 
Preservation and Research Data at Binghamton University Libraries by Edward C...
Preservation and Research Data at Binghamton University Libraries by Edward C...Preservation and Research Data at Binghamton University Libraries by Edward C...
Preservation and Research Data at Binghamton University Libraries by Edward C...
 

Ähnlich wie Lowering business costs: Mitigating risk in the software delivery lifecycle

Ibm smarter quality_management
Ibm smarter quality_managementIbm smarter quality_management
Ibm smarter quality_managementCristiano Caetano
 
Rational collaborative-lifecycle-management-2012
Rational collaborative-lifecycle-management-2012Rational collaborative-lifecycle-management-2012
Rational collaborative-lifecycle-management-2012Strongback Consulting
 
Breaking the Project Failure Cycle
Breaking the Project Failure CycleBreaking the Project Failure Cycle
Breaking the Project Failure CycleGlen Alleman
 
CTLR 2010 Issue 7 Waterfall Contract
CTLR 2010 Issue 7 Waterfall ContractCTLR 2010 Issue 7 Waterfall Contract
CTLR 2010 Issue 7 Waterfall Contractsusanatkinson
 
Custom Software Solutions Provider USA: Top 10 Challenges to Mitigate
Custom Software Solutions Provider USA: Top 10 Challenges to MitigateCustom Software Solutions Provider USA: Top 10 Challenges to Mitigate
Custom Software Solutions Provider USA: Top 10 Challenges to MitigateWeblineIndia
 
SE18_SE_Lec 12_ Project Management 1
SE18_SE_Lec 12_ Project Management 1SE18_SE_Lec 12_ Project Management 1
SE18_SE_Lec 12_ Project Management 1Amr E. Mohamed
 
Project management
Project managementProject management
Project managementNihal Ranjan
 
Performance Management With Rational Insight - Karthi D
Performance Management With Rational Insight - Karthi DPerformance Management With Rational Insight - Karthi D
Performance Management With Rational Insight - Karthi DRoopa Nadkarni
 
Software engineering project management
Software engineering project managementSoftware engineering project management
Software engineering project managementjhudyne
 
Improving software economics - Top 10 principles of achieving agility at scale
Improving software economics - Top 10 principles of achieving agility at scaleImproving software economics - Top 10 principles of achieving agility at scale
Improving software economics - Top 10 principles of achieving agility at scaleIBM Rational software
 
Future of Software Analysis & Measurement_CAST
Future of Software Analysis & Measurement_CASTFuture of Software Analysis & Measurement_CAST
Future of Software Analysis & Measurement_CASTCAST
 
Project Portfolio Management
Project Portfolio ManagementProject Portfolio Management
Project Portfolio ManagementDigite Inc
 
Rational
RationalRational
RationalIBM
 
Software Quality Management ( 2510Ict )
Software Quality Management ( 2510Ict )Software Quality Management ( 2510Ict )
Software Quality Management ( 2510Ict )Crystal Williams
 
Introduction to Agile
Introduction to AgileIntroduction to Agile
Introduction to AgileRichard Cheng
 
Software Risk Management for IT Execs CAST
Software Risk Management for IT Execs CASTSoftware Risk Management for IT Execs CAST
Software Risk Management for IT Execs CASTCAST
 
SE_Lec 11_ Project Management
SE_Lec 11_ Project ManagementSE_Lec 11_ Project Management
SE_Lec 11_ Project ManagementAmr E. Mohamed
 

Ähnlich wie Lowering business costs: Mitigating risk in the software delivery lifecycle (20)

Enterprise software delivery
Enterprise software deliveryEnterprise software delivery
Enterprise software delivery
 
Ibm smarter quality_management
Ibm smarter quality_managementIbm smarter quality_management
Ibm smarter quality_management
 
Rational collaborative-lifecycle-management-2012
Rational collaborative-lifecycle-management-2012Rational collaborative-lifecycle-management-2012
Rational collaborative-lifecycle-management-2012
 
Breaking the Project Failure Cycle
Breaking the Project Failure CycleBreaking the Project Failure Cycle
Breaking the Project Failure Cycle
 
CTLR 2010 Issue 7 Waterfall Contract
CTLR 2010 Issue 7 Waterfall ContractCTLR 2010 Issue 7 Waterfall Contract
CTLR 2010 Issue 7 Waterfall Contract
 
Agile methodology
Agile methodologyAgile methodology
Agile methodology
 
Custom Software Solutions Provider USA: Top 10 Challenges to Mitigate
Custom Software Solutions Provider USA: Top 10 Challenges to MitigateCustom Software Solutions Provider USA: Top 10 Challenges to Mitigate
Custom Software Solutions Provider USA: Top 10 Challenges to Mitigate
 
SE18_SE_Lec 12_ Project Management 1
SE18_SE_Lec 12_ Project Management 1SE18_SE_Lec 12_ Project Management 1
SE18_SE_Lec 12_ Project Management 1
 
Project management
Project managementProject management
Project management
 
Performance Management With Rational Insight - Karthi D
Performance Management With Rational Insight - Karthi DPerformance Management With Rational Insight - Karthi D
Performance Management With Rational Insight - Karthi D
 
Ch22
Ch22Ch22
Ch22
 
Software engineering project management
Software engineering project managementSoftware engineering project management
Software engineering project management
 
Improving software economics - Top 10 principles of achieving agility at scale
Improving software economics - Top 10 principles of achieving agility at scaleImproving software economics - Top 10 principles of achieving agility at scale
Improving software economics - Top 10 principles of achieving agility at scale
 
Future of Software Analysis & Measurement_CAST
Future of Software Analysis & Measurement_CASTFuture of Software Analysis & Measurement_CAST
Future of Software Analysis & Measurement_CAST
 
Project Portfolio Management
Project Portfolio ManagementProject Portfolio Management
Project Portfolio Management
 
Rational
RationalRational
Rational
 
Software Quality Management ( 2510Ict )
Software Quality Management ( 2510Ict )Software Quality Management ( 2510Ict )
Software Quality Management ( 2510Ict )
 
Introduction to Agile
Introduction to AgileIntroduction to Agile
Introduction to Agile
 
Software Risk Management for IT Execs CAST
Software Risk Management for IT Execs CASTSoftware Risk Management for IT Execs CAST
Software Risk Management for IT Execs CAST
 
SE_Lec 11_ Project Management
SE_Lec 11_ Project ManagementSE_Lec 11_ Project Management
SE_Lec 11_ Project Management
 

Mehr von IBM Rational software

DMT-2467 Like the Features in Rational DOORS 9? Come Check Them Out in DOORS...
DMT-2467	Like the Features in Rational DOORS 9? Come Check Them Out in DOORS...DMT-2467	Like the Features in Rational DOORS 9? Come Check Them Out in DOORS...
DMT-2467 Like the Features in Rational DOORS 9? Come Check Them Out in DOORS...IBM Rational software
 
Dmt 5899 workshop - Learn to Collaborate, Trace, Review and Reuse Your Requir...
Dmt 5899 workshop - Learn to Collaborate, Trace, Review and Reuse Your Requir...Dmt 5899 workshop - Learn to Collaborate, Trace, Review and Reuse Your Requir...
Dmt 5899 workshop - Learn to Collaborate, Trace, Review and Reuse Your Requir...IBM Rational software
 
Steer at the Team Level with Rational Team Concert
Steer at the Team Level with Rational Team ConcertSteer at the Team Level with Rational Team Concert
Steer at the Team Level with Rational Team ConcertIBM Rational software
 
UrbanCode Deploy course and product overview slides
UrbanCode Deploy course and product overview slidesUrbanCode Deploy course and product overview slides
UrbanCode Deploy course and product overview slidesIBM Rational software
 
IBM InterConnect Speaker Proposal Tips
IBM InterConnect Speaker Proposal TipsIBM InterConnect Speaker Proposal Tips
IBM InterConnect Speaker Proposal TipsIBM Rational software
 
Factors to consider when starting a brand-new requirements management project...
Factors to consider when starting a brand-new requirements management project...Factors to consider when starting a brand-new requirements management project...
Factors to consider when starting a brand-new requirements management project...IBM Rational software
 
IBM DevOps Announcements - June 2014
IBM DevOps Announcements - June 2014IBM DevOps Announcements - June 2014
IBM DevOps Announcements - June 2014IBM Rational software
 
IBM Rational Developer for System z Quick Start Sales Presentation
IBM Rational Developer for System z Quick Start Sales PresentationIBM Rational Developer for System z Quick Start Sales Presentation
IBM Rational Developer for System z Quick Start Sales PresentationIBM Rational software
 
Rational consulting café to go menu
Rational consulting café to go menuRational consulting café to go menu
Rational consulting café to go menuIBM Rational software
 

Mehr von IBM Rational software (20)

DMT-2467 Like the Features in Rational DOORS 9? Come Check Them Out in DOORS...
DMT-2467	Like the Features in Rational DOORS 9? Come Check Them Out in DOORS...DMT-2467	Like the Features in Rational DOORS 9? Come Check Them Out in DOORS...
DMT-2467 Like the Features in Rational DOORS 9? Come Check Them Out in DOORS...
 
Dmt 5899 workshop - Learn to Collaborate, Trace, Review and Reuse Your Requir...
Dmt 5899 workshop - Learn to Collaborate, Trace, Review and Reuse Your Requir...Dmt 5899 workshop - Learn to Collaborate, Trace, Review and Reuse Your Requir...
Dmt 5899 workshop - Learn to Collaborate, Trace, Review and Reuse Your Requir...
 
Deployment module slides
Deployment module slidesDeployment module slides
Deployment module slides
 
Security
SecuritySecurity
Security
 
Steer at the Team Level with Rational Team Concert
Steer at the Team Level with Rational Team ConcertSteer at the Team Level with Rational Team Concert
Steer at the Team Level with Rational Team Concert
 
Applications lab
Applications lab Applications lab
Applications lab
 
Application slides
Application slidesApplication slides
Application slides
 
Components lab
Components labComponents lab
Components lab
 
UCD components
UCD components UCD components
UCD components
 
Resource lab
Resource labResource lab
Resource lab
 
Resources slides
Resources slidesResources slides
Resources slides
 
UrbanCode Deploy course and product overview slides
UrbanCode Deploy course and product overview slidesUrbanCode Deploy course and product overview slides
UrbanCode Deploy course and product overview slides
 
IBM InterConnect Speaker Proposal Tips
IBM InterConnect Speaker Proposal TipsIBM InterConnect Speaker Proposal Tips
IBM InterConnect Speaker Proposal Tips
 
Factors to consider when starting a brand-new requirements management project...
Factors to consider when starting a brand-new requirements management project...Factors to consider when starting a brand-new requirements management project...
Factors to consider when starting a brand-new requirements management project...
 
IBM DevOps Announcements - June 2014
IBM DevOps Announcements - June 2014IBM DevOps Announcements - June 2014
IBM DevOps Announcements - June 2014
 
IBM Rational Developer for System z Quick Start Sales Presentation
IBM Rational Developer for System z Quick Start Sales PresentationIBM Rational Developer for System z Quick Start Sales Presentation
IBM Rational Developer for System z Quick Start Sales Presentation
 
Rational consulting café to go menu
Rational consulting café to go menuRational consulting café to go menu
Rational consulting café to go menu
 
Lab3 RTC Source Control
Lab3 RTC Source ControlLab3 RTC Source Control
Lab3 RTC Source Control
 
Lab2 RTC Work Items
Lab2 RTC Work ItemsLab2 RTC Work Items
Lab2 RTC Work Items
 
Lab4 RTC Builds
Lab4 RTC BuildsLab4 RTC Builds
Lab4 RTC Builds
 

Kürzlich hochgeladen

NASA CoCEI Scaling Strategy - November 2023
NASA CoCEI Scaling Strategy - November 2023NASA CoCEI Scaling Strategy - November 2023
NASA CoCEI Scaling Strategy - November 2023Steve Rader
 
AMAZON SELLER VIRTUAL ASSISTANT PRODUCT RESEARCH .pdf
AMAZON SELLER VIRTUAL ASSISTANT PRODUCT RESEARCH .pdfAMAZON SELLER VIRTUAL ASSISTANT PRODUCT RESEARCH .pdf
AMAZON SELLER VIRTUAL ASSISTANT PRODUCT RESEARCH .pdfJohnCarloValencia4
 
BCE24 | Virtual Brand Ambassadors: Making Brands Personal - John Meulemans
BCE24 | Virtual Brand Ambassadors: Making Brands Personal - John MeulemansBCE24 | Virtual Brand Ambassadors: Making Brands Personal - John Meulemans
BCE24 | Virtual Brand Ambassadors: Making Brands Personal - John MeulemansBBPMedia1
 
Chapter_Five_The_Rural_Development_Policies_and_Strategy_of_Ethiopia.pptx
Chapter_Five_The_Rural_Development_Policies_and_Strategy_of_Ethiopia.pptxChapter_Five_The_Rural_Development_Policies_and_Strategy_of_Ethiopia.pptx
Chapter_Five_The_Rural_Development_Policies_and_Strategy_of_Ethiopia.pptxesiyasmengesha
 
Team B Mind Map for Organizational Chg..
Team B Mind Map for Organizational Chg..Team B Mind Map for Organizational Chg..
Team B Mind Map for Organizational Chg..dlewis191
 
PDT 88 - 4 million seed - Seed - Protecto.pdf
PDT 88 - 4 million seed - Seed - Protecto.pdfPDT 88 - 4 million seed - Seed - Protecto.pdf
PDT 88 - 4 million seed - Seed - Protecto.pdfHajeJanKamps
 
Entrepreneurship & organisations: influences and organizations
Entrepreneurship & organisations: influences and organizationsEntrepreneurship & organisations: influences and organizations
Entrepreneurship & organisations: influences and organizationsP&CO
 
HELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptx
HELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptxHELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptx
HELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptxHelene Heckrotte
 
Fabric RFID Wristbands in Ireland for Events and Festivals
Fabric RFID Wristbands in Ireland for Events and FestivalsFabric RFID Wristbands in Ireland for Events and Festivals
Fabric RFID Wristbands in Ireland for Events and FestivalsWristbands Ireland
 
To Create Your Own Wig Online To Create Your Own Wig Online
To Create Your Own Wig Online  To Create Your Own Wig OnlineTo Create Your Own Wig Online  To Create Your Own Wig Online
To Create Your Own Wig Online To Create Your Own Wig Onlinelng ths
 
Scrum Events & How to run them effectively
Scrum Events & How to run them effectivelyScrum Events & How to run them effectively
Scrum Events & How to run them effectivelyMarianna Nakou
 
MoneyBridge Pitch Deck - Investor Presentation
MoneyBridge Pitch Deck - Investor PresentationMoneyBridge Pitch Deck - Investor Presentation
MoneyBridge Pitch Deck - Investor Presentationbaron83
 
Harvard Business Review.pptx | Navigating Labor Unrest (March-April 2024)
Harvard Business Review.pptx | Navigating Labor Unrest (March-April 2024)Harvard Business Review.pptx | Navigating Labor Unrest (March-April 2024)
Harvard Business Review.pptx | Navigating Labor Unrest (March-April 2024)tazeenaila12
 
Borderless Access - Global Panel book-unlock 2024
Borderless Access - Global Panel book-unlock 2024Borderless Access - Global Panel book-unlock 2024
Borderless Access - Global Panel book-unlock 2024Borderless Access
 
UNLEASHING THE POWER OF PROGRAMMATIC ADVERTISING
UNLEASHING THE POWER OF PROGRAMMATIC ADVERTISINGUNLEASHING THE POWER OF PROGRAMMATIC ADVERTISING
UNLEASHING THE POWER OF PROGRAMMATIC ADVERTISINGlokeshwarmaha
 
Developing Coaching Skills: Mine, Yours, Ours
Developing Coaching Skills: Mine, Yours, OursDeveloping Coaching Skills: Mine, Yours, Ours
Developing Coaching Skills: Mine, Yours, OursKaiNexus
 
The Vietnam Believer Newsletter_MARCH 25, 2024_EN_Vol. 003
The Vietnam Believer Newsletter_MARCH 25, 2024_EN_Vol. 003The Vietnam Believer Newsletter_MARCH 25, 2024_EN_Vol. 003
The Vietnam Believer Newsletter_MARCH 25, 2024_EN_Vol. 003believeminhh
 
Boat Trailers Market PPT: Growth, Outlook, Demand, Keyplayer Analysis and Opp...
Boat Trailers Market PPT: Growth, Outlook, Demand, Keyplayer Analysis and Opp...Boat Trailers Market PPT: Growth, Outlook, Demand, Keyplayer Analysis and Opp...
Boat Trailers Market PPT: Growth, Outlook, Demand, Keyplayer Analysis and Opp...IMARC Group
 
Project Brief & Information Architecture Report
Project Brief & Information Architecture ReportProject Brief & Information Architecture Report
Project Brief & Information Architecture Reportamberjiles31
 

Kürzlich hochgeladen (20)

NASA CoCEI Scaling Strategy - November 2023
NASA CoCEI Scaling Strategy - November 2023NASA CoCEI Scaling Strategy - November 2023
NASA CoCEI Scaling Strategy - November 2023
 
AMAZON SELLER VIRTUAL ASSISTANT PRODUCT RESEARCH .pdf
AMAZON SELLER VIRTUAL ASSISTANT PRODUCT RESEARCH .pdfAMAZON SELLER VIRTUAL ASSISTANT PRODUCT RESEARCH .pdf
AMAZON SELLER VIRTUAL ASSISTANT PRODUCT RESEARCH .pdf
 
BCE24 | Virtual Brand Ambassadors: Making Brands Personal - John Meulemans
BCE24 | Virtual Brand Ambassadors: Making Brands Personal - John MeulemansBCE24 | Virtual Brand Ambassadors: Making Brands Personal - John Meulemans
BCE24 | Virtual Brand Ambassadors: Making Brands Personal - John Meulemans
 
Chapter_Five_The_Rural_Development_Policies_and_Strategy_of_Ethiopia.pptx
Chapter_Five_The_Rural_Development_Policies_and_Strategy_of_Ethiopia.pptxChapter_Five_The_Rural_Development_Policies_and_Strategy_of_Ethiopia.pptx
Chapter_Five_The_Rural_Development_Policies_and_Strategy_of_Ethiopia.pptx
 
Team B Mind Map for Organizational Chg..
Team B Mind Map for Organizational Chg..Team B Mind Map for Organizational Chg..
Team B Mind Map for Organizational Chg..
 
PDT 88 - 4 million seed - Seed - Protecto.pdf
PDT 88 - 4 million seed - Seed - Protecto.pdfPDT 88 - 4 million seed - Seed - Protecto.pdf
PDT 88 - 4 million seed - Seed - Protecto.pdf
 
Entrepreneurship & organisations: influences and organizations
Entrepreneurship & organisations: influences and organizationsEntrepreneurship & organisations: influences and organizations
Entrepreneurship & organisations: influences and organizations
 
HELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptx
HELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptxHELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptx
HELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptx
 
Fabric RFID Wristbands in Ireland for Events and Festivals
Fabric RFID Wristbands in Ireland for Events and FestivalsFabric RFID Wristbands in Ireland for Events and Festivals
Fabric RFID Wristbands in Ireland for Events and Festivals
 
To Create Your Own Wig Online To Create Your Own Wig Online
To Create Your Own Wig Online  To Create Your Own Wig OnlineTo Create Your Own Wig Online  To Create Your Own Wig Online
To Create Your Own Wig Online To Create Your Own Wig Online
 
Scrum Events & How to run them effectively
Scrum Events & How to run them effectivelyScrum Events & How to run them effectively
Scrum Events & How to run them effectively
 
MoneyBridge Pitch Deck - Investor Presentation
MoneyBridge Pitch Deck - Investor PresentationMoneyBridge Pitch Deck - Investor Presentation
MoneyBridge Pitch Deck - Investor Presentation
 
Harvard Business Review.pptx | Navigating Labor Unrest (March-April 2024)
Harvard Business Review.pptx | Navigating Labor Unrest (March-April 2024)Harvard Business Review.pptx | Navigating Labor Unrest (March-April 2024)
Harvard Business Review.pptx | Navigating Labor Unrest (March-April 2024)
 
Borderless Access - Global Panel book-unlock 2024
Borderless Access - Global Panel book-unlock 2024Borderless Access - Global Panel book-unlock 2024
Borderless Access - Global Panel book-unlock 2024
 
UNLEASHING THE POWER OF PROGRAMMATIC ADVERTISING
UNLEASHING THE POWER OF PROGRAMMATIC ADVERTISINGUNLEASHING THE POWER OF PROGRAMMATIC ADVERTISING
UNLEASHING THE POWER OF PROGRAMMATIC ADVERTISING
 
Developing Coaching Skills: Mine, Yours, Ours
Developing Coaching Skills: Mine, Yours, OursDeveloping Coaching Skills: Mine, Yours, Ours
Developing Coaching Skills: Mine, Yours, Ours
 
Investment Opportunity for Thailand's Automotive & EV Industries
Investment Opportunity for Thailand's Automotive & EV IndustriesInvestment Opportunity for Thailand's Automotive & EV Industries
Investment Opportunity for Thailand's Automotive & EV Industries
 
The Vietnam Believer Newsletter_MARCH 25, 2024_EN_Vol. 003
The Vietnam Believer Newsletter_MARCH 25, 2024_EN_Vol. 003The Vietnam Believer Newsletter_MARCH 25, 2024_EN_Vol. 003
The Vietnam Believer Newsletter_MARCH 25, 2024_EN_Vol. 003
 
Boat Trailers Market PPT: Growth, Outlook, Demand, Keyplayer Analysis and Opp...
Boat Trailers Market PPT: Growth, Outlook, Demand, Keyplayer Analysis and Opp...Boat Trailers Market PPT: Growth, Outlook, Demand, Keyplayer Analysis and Opp...
Boat Trailers Market PPT: Growth, Outlook, Demand, Keyplayer Analysis and Opp...
 
Project Brief & Information Architecture Report
Project Brief & Information Architecture ReportProject Brief & Information Architecture Report
Project Brief & Information Architecture Report
 

Lowering business costs: Mitigating risk in the software delivery lifecycle

  • 1. Mitigating risk in the software delivery lifecycle August 2009 Lowering business costs: Mitigating risk in the software delivery lifecycle Roberto Argento IBM Rational Business Development Executive Valerie Hamilton IBM Rational Solution Marketing Manager and Certified Senior IT Specialist
  • 2. Mitigating risk in the software delivery lifecycle Page 2 Introduction Contents In today’s challenging economy, businesses are under increased pressures to reduce overall costs while mitigating and controlling risks. The reality is that 2 Introduction many businesses continue to struggle to successfully deliver quality software 3 Defining software delivery risks on time and on budget that meets their market needs. One study states that, on 3 Balancing risks with value average, 32% of projects do not align with company goals and 39% of projects 5 The cost of failure are over budget.1 Such surprising statistics only touch the surface of the 6 Building the right thing: software delivery problems faced by businesses today. Requirements management 8 Visibility into project and process Other studies confirm that success rates are not improving; software delivery outcomes: Performance challenges continue to adversely affect business costs. According to the measurement and management Standish Group, businesses continue to struggle with project success rates and 10 Conclusion failures. Their latest published Chaos Report 2 states that “this year’s results show a marked decrease in project success rates, with 32% of all projects succeeding which are delivered on time, on budget, with required features and functions”. Additionally, “44% were challenged which are late, over budget, and/or with less than the required features and functions and 24% failed which are cancelled prior to completion or delivered and never used.”3 The numbers are staggering. Why is it so difficult to deliver quality software on time and on budget that aligns to the business goals? Imagine if “wasted” resources and dollars lost on software delivery failures could be used to innovate — to create new products or to pursue new market opportunities. Think of the positive impact to the business’s bottom-line. There are plenty of businesses that, by mitigating risks and having a systematic (but not bureaucratic) approach to the software delivery process, have achieved improvements in their success rates leading to a decrease in their development costs and a better and greater impact to their business outcome. In this paper, you will learn how requirements and performance management can help to reduce risks and lower business costs by: • Achieving consensus on project requirements and delivering quality products that meet stakeholder’s business needs • Understanding the impact of changes to your deliverables and having the ability to accurately track and communicate these changes • Providing the ability to analyze, monitor, and trend project status across the entire software lifecycle for objective and informed decision making • Assessing and measuring process and project performance to drive continual process improvements
  • 3. Mitigating risk in the software delivery lifecycle Page 3 Defining software delivery risks Highlights In everyday life a risk is an exposure to loss or injury: A factor, thing, element, or course involving some degree of danger. Similarly, in software development a risk is something that can compromise the success of a project. Examples of potential sources of risk in software delivery are listed below: • Missing, incomplete or changing requirements and specifications • Manual or undefined development processes and practices • Incomplete testing and validation • Lack of stakeolder input • Disconnected distributed teams • Project interdependencies and lack of team collaboration • Changes to regulatory compliance • Insufficient time or schedule expectations • Unclear business goals and objectives Making informed decisions by Making informed decisions by consciously assessing what can go wrong, as consciously assessing what can go well as the likelihood and severity of the impact, is at the heart of defining wrong, as well as the likelihood and software delivery risks. Risks are exposed and can be addressed through the severity of the impact, is at the heart identification, analysis, planning, tracking, controlling, and communication of of defining software delivery risks. the software delivery lifecycle. Balancing risks with value Risk is a potential manifestation of the likelihood of unexpected things happening to the project, and risk stands in the way of value creation. Every project carries an amount of risk. If project risks are not identified and addressed, there is a very real chance that they will arise at some point in the project lifespan. The longer a risk goes unnoticed, the more costly it is to correct. Risk is directly proportional to uncertainty in estimates, and stakeholders typically want to know sooner rather than later what value the project can deliver in the stipulated time. In many cases, you reduce risk when you create value by implementing and testing the most critical capabilities. Risk-driven development focuses on identifying high risk areas and addressing those items early in the project lifespan. The goal is to flush these issues out early before you spend a considerable amount of time on project development and any re-work is required.
  • 4. Mitigating risk in the software delivery lifecycle Page 4 Value-driven development focuses on identifying those features most Highlights important to the customer and business, and completing those items early so the stakeholders can see progress as well as provide feedback on those features early and on-going. Risk-driven development recommends focusing on those high risks areas that are critical to the success of the project, while value-driven development focuses on those functional requirements perceived to be of high value to the stakeholders. The risk response requires careful Risk response should be in proportion to the significance of the risk. balancing of competing priorities to However, there are situations where risks and business value are at odds maximize stakeholder value. with each other. Thus, the risk response requires careful balancing of these competing priorities to maximize stakeholder value. A risk-driven iterative approach involves iterations that strike a balance between high-risk issues crucial to the project and features that bring value (see Figure 1). Figure 1: A risk-driven iterative approach balances risks with value
  • 5. Mitigating risk in the software delivery lifecycle Page 5 In reviewing the project lifecycle phases (Inception, Elaboration, Construction and Highlights Transition) shown in Figure 1, risks are normally higher in the Inception phase, and they continue to decline over subsequent project lifecycle phases as risks are identified and addressed. In the Inception phase the initial risk assessment is performed and core project requirements and key features are defined. In the Elaboration phase, the primary objective is to mitigate the key risk items identi- fied by analysis. The Elaboration phase is where the project starts to take shape: the problem domain analysis is made and the architecture of the project gets its basic form. This is the phase where there is a balance between risk and features that are perceived to be of high value to the stakeholders. Creating value by reducing uncertainty is the best way to reduce costs and improve project success. The cost of failure Software delivery is a team-based activity. In order to avoid the high cost of failure teams must work together to mitigate and manage risks for successful outcomes to the business. To avoid the high costs of failure and reduce risks, there must be repeatable, predictable processes and best practices in place throughout the software delivery lifecycle that improve productivity and quality. Stakeholders typically have an abstract idea of what they want as an Typical software delivery activities include requirements elicitation, end result, but not what the software planning, design, implementation, testing, documentation, deployment, and should do. Project requirements need maintenance. With so many activities of the software delivery lifecycle, it is no to be accessible so that all team wonder that failures frequently occur. members understand their part of the whole project. “Requirements elicitation” refers to those activities focused on understanding your stakeholders’ business goals and objectives, which serve as the starting point for gathering project requirements. Only when you understand the business goals and objectives can you begin defining a solution that will solve stakeholders’ business needs. The planning phase within the software delivery lifecycle involves the important task of defining the requirements or requirements analysis. Stakeholders typically have an abstract idea of what they want as an end result, but not what the software should do. Project requirements need to be accessible so that all team members understand their part of the whole project and are informed as changes occur.
  • 6. Mitigating risk in the software delivery lifecycle Page 6 Missing requirements is one of the biggest contributors to schedule delays and Highlights budget overruns; there’s nothing worse than being half way done with a project and then realizing a major stakeholder need has not even been addressed. Incomplete, ambiguous, or even contradictory requirements need to be analyzed and extracted prior to defining the scope of a project. Making changes to a deployed system Requirements analysis and management is a high-leverage activity because is much more costly than getting it making changes to a deployed system is much more costly than getting it right right the first time. The immense cost the first time. The immense cost associated with reworking existing code and associated with reworking existing tests when requirement errors are identified is one of the key areas of risk in the code is one of the key areas of risk in software delivery lifecycle. the software delivery lifecycle. Organizations must have the ability to review, assess, and improve current proc- esses within each phase of the software delivery lifecycle. Having accurate insight into enterprise data, processes, and practices is a key component of success. How- Measuring project and process out- ever, many organizations suffer from a lack of visibility into the software delivery comes allows for continual process lifecycle. Additionally, they struggle with data gaps and manually created metrics, improvements across the software which creates data blind spots that put an organization’s success at risk. Measuring delivery lifecycle, which reduces project and process outcomes allows for continual process improvements across project failures and lowers business the software delivery lifecycle, which reduces project failures and lowers business costs. costs. Building the right thing: Requirements management Requirements management is the process of eliciting, defining, elaborating, documenting, analyzing, prioritizing, and agreeing on requirements and then controlling changes over the course of a project to ensure that deliverables remain aligned to the stakeholders’ goals. Requirements management thus helps ensure that risks are minimized, stakeholder problems are solved, and business costs are lowered. What is so hard about requirements management? Words can be ambiguous. It is difficult to clearly communicate a vision to all team members. It is complicated to show relationships or dependencies between requirements. Requirements come in a variety of shapes and sizes. Some may be more complex, more risky, more important, or less stable than others, and the sheer number of requirements can be grueling to manage. But most of all, requirements frequently change.
  • 7. Mitigating risk in the software delivery lifecycle Page 7 Understanding the impact of changes to other requirements and to your project, Highlights then tracking and communicating those changes to all team members, is one of the greatest challenges in the requirements management discipline. It is clear that doing things right can take us down a path of risk mitigation and value creation. But how do we know when we are doing the right things? When evaluating fourteen software development and delivery projects in six coun- tries of Latin America (Mexico, Brazil, Chile, Argentina, Peru, and Colombia), in different sectors of the economy (finance, insurance, telecom, ISVs, government agencies, and energy) and covering several technology platforms (mainframe, Java development, creation of new products, and ERP maintenance), we discovered a common problem: a pervasive lack of effective requirements management. Each of the projects presented a variety of requirements issues, including the inability to properly test or validate functionality, rework and churn due to constant change of features and functionality, and high development costs. The fact was that all projects invested very little time in planning and managing their requirements. The conclusion of this project evaluation is that most organizations are very good Most organizations are very good at at proposing new ideas and solutions. But they are commonly ineffective in plan- proposing new ideas and solutions. ning and managing requirements and executing software delivery with reduced But they are commonly ineffective in risks and costs. planning and managing requirements. CIO Magazine reported that “as many as 71% of software projects that fail do so because of poor requirements management, making it the single biggest reason for project failure.”4 Domain experts such as Rikki Kirzner cite the need for require- ments management for project success. He was quoted in a recent article: The successful outcome of any project starts with defining, creating, and distrib- uting project requirements in a form where all stakeholders can easily access, collaborate, and contribute to creating requirements. While this seems simple enough to explain, time and again, good intentions are undermined by the capabilities of the tools you are using and the environment in which you are working. This situation only exacerbates the problems encountered when all the stakeholders don’t understand the original business intent, goals, or cannot con- nect those goals with what the team is doing. Geographic dispersion, communi- cation difficulties and conflicting priorities can also cause problems.5
  • 8. Mitigating risk in the software delivery lifecycle Page 8 One of the core principles of requirements management is promoting team Highlights collaboration. It is imperative to make the requirements accessible to every- one on the team, thus facilitating team collaboration and providing visibility to the impact of change. IBM has found that the investment in a requirements management solution, such as IBM Rational Requirements Composer, IBM Rational RequisitePro, or IBM Rational Doors facilitates team collaboration and helps implement requirements management best practices. This in turn reduces costs and helps mitigate risks. Rational Requirements Composer is a collaborative requirements definition and management solution, perfect for teams that want to focus on definition and need “just enough” requirements manage- ment. It provides textual and visual techniques to elicit, elaborate, and vali- date requirements collaboratively with your stakeholders, and it helps deliver quality solutions that meet their business and product requirements. Both Rational RequisitePro and Rational Doors provide traceability and impact analysis that keeps analysts, architects, developers, and testers aligned to business needs and requirements throughout the software delivery lifecycle. Visibility into project and process outcomes: Performance measurement and management Performance measurement and management helps software delivery teams make the right decisions by providing deeper insight into an organization. It enables organizations to measure, monitor, and analyze project and process performance against business objectives for trending, to identify issues, and to drive continuous process improvement. When data is gathered manually, when it comes from different sources that may not align, or where there is an inability to gather information from the various teams (thus creating data silos), it is nearly impossible to make the right deci- sions for an organization. It becomes hard to react to organizational and market changes, and to measure the effectiveness of processes and practices to improve them. And of course, this ineffectiveness can directly impact costs and business risks.
  • 9. Mitigating risk in the software delivery lifecycle Page 9 You cannot improve what you cannot measure. Raising the visibility into an Highlights organization by having real-time information in a single view across the various projects, products, and geographical boundaries helps project teams to review, You cannot improve what you cannot assess, and improve current processes within each phase of the software delivery measure. Real-time information lifecycle. in a single view across various projects, products, and geographical Having access to the right data at the right time helps organizations make objec- boundaries helps project teams to tive and informed decisions. They are able to measure organizational effectiveness review, assess, and improve current to improve processes and practices, which not only increases efficiency and speed, processes. but allows for quick detection of problems and continual status monitoring for reduced costs and risks. IBM Rational Insight, a performance measure and management solution, allows Measuring organizational organizations to measure, monitor, analyze, and trend project and process per- effectiveness improves processes formance as well as continually improve organizational outcomes through process and practices, which not only improvements. It eliminates inefficient time wasted on manual data collection increases efficiency and speed, but through automatic collection of data presented in a single view. Rational Insight allows quick detection of problems. also helps deliver the IBM Measured Capability Improvement Framework (known as MCIF) for process improvement and best practice guidance. This aligns guid- ance with performance measurement for faster improvements to an organization, thus lowering costs while raising team capabilities.
  • 10. Mitigating risk in the software delivery lifecycle Page 10 Conclusion Highlights Lowering business costs by mitigating risks in the software delivery lifecycle is not simply an aspiration among businesses today. During these challenging economic times, it is imperative to improve the success rate of projects with reduced costs. Improving the success rate of projects requires that teams focus on business outcomes, become as productive as possible, and mitigate risks with proven tools and techniques. This requires the right mix of information, collaboration, and automation — all at the right time. Successful leaders will leverage innovation to help them seize business opportuni- Successful leaders will leverage ties, manage to objectives, and execute with reduced cost and risk. To drive busi- innovation to help them seize ness transformation, companies need greater agility and responsiveness from their business opportunities, manage to teams. They demand greater differentiation in their products and services in order objectives, and execute with reduced to surpass the competition and increase profits. cost and risk. Requirements management helps achieve consensus with your stakeholders. It focuses on the ability to deliver quality solutions that align project deliverables to stakeholder business needs. Performance measurement and management helps to monitor, analyze and trend process, resources, and project outcomes to drive execution of projects and proc- esses with consistent and predictable results. Doing the right thing means to be able to: • Reduce risks across the software delivery lifecycle through team collaboration to clarify actual business issues, increase individual and team productivity, compress development cycles, and rapidly deliver high-quality software • Make better decisions based on real-time, accurate information and consen- sus across stakeholders • Drive faster project delivery by providing requirements collaboration, history and context that team members need to reduce rework, and allow for efficient reuse of requirements artifacts for future projects • Iterate quickly by analyzing and managing change for continual alignment with business priorities.
  • 11. Endnotes © Copyright IBM Corporation 2009 IBM Corporation 1. IDC Whitepaper: How Project and Portfolio Management Solutions Are Delivering Value to Software Group Organizations, September 2008 Route 100 2. Standish Group Chaos Report, CHAOS Summary 2009 Somers, NY 10589 3. “The Standish Group” - http://www.standishgroup.com/newsroom/chaos_2009.php U.S.A. 4. Christopher Lindquist, “Fixing the Requirements Mess,” in CIO Magazine, Nov. 15, 2005 5. Rikki Kirzner, “Requirements Management: A Core Part of the Development Lifecycle,” Produced in the United States of America DevX.com, Aug 8, 2008, at http://www.devx.com/ibm/Article/38819/4047 August 2009 All Rights Reserved IBM, the IBM logo, ibm.com, Rational, IBM Rational Requirements Composer, IBM Rational RequisitePro, IBM Rational Insight and IBM Measured Capability Improvement Framework are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Other company, product, or service names may be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml The information contained in this document is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this documentation, it is provided “as is” without warranty of any kind, express or implied. RAW14172-USEN-00