@inbook{doi:https://doi.org/10.1002/9781394203314.ch21,
    author = {Orosz, Michael},
    publisher = {John Wiley & Sons, Ltd},
    isbn = {9781394203314},
    title = {Managing Risk},
    booktitle = {Systems Engineering for the Digital Age},
    chapter = {21},
    pages = {463-470},
    doi = {https://doi.org/10.1002/9781394203314.ch21},
    url = {https://onlinelibrary.wiley.com/doi/abs/10.1002/9781394203314.ch21},
    eprint = {https://onlinelibrary.wiley.com/doi/pdf/10.1002/9781394203314.ch21},
    year = {2023},
    keywords = {risk, technical risk, system risk, obsolescence, risk management, agile risk management},
    abstract = {Summary Risk is generally defined as the measure of the potential inability to achieve overall program objectives within defined cost, schedule, and technical constraints. What is missing from this definition are risks associated with failing to identify and capture evolving user, system, and technical requirements, which are often driven by evolving end-user or marketplace demands. Ignoring these evolving needs introduces risks, meaning you may be developing an obsolete product or one that only partially meets end-user needs. There are many different flavors of risk management, but each of these includes considerations for defining and assessing risk (including the likelihood it will occur and the potential impact if it does), determining how to decide which risks to mitigate and how to do so, and risk monitoring. This chapter focuses on managing three types of risks to systems engineering and development: project development risk, technical risk, and obsolescence risk.}
}

{"_id":"t35ZDnCSvYScJEtxm","bibbaseid":"orosz-managingrisk-2023","author_short":["Orosz, M."],"bibdata":{"bibtype":"inbook","type":"inbook","author":[{"propositions":[],"lastnames":["Orosz"],"firstnames":["Michael"],"suffixes":[]}],"publisher":"John Wiley & Sons, Ltd","isbn":"9781394203314","title":"Managing Risk","booktitle":"Systems Engineering for the Digital Age","chapter":"21","pages":"463-470","doi":"https://doi.org/10.1002/9781394203314.ch21","url":"https://onlinelibrary.wiley.com/doi/abs/10.1002/9781394203314.ch21","eprint":"https://onlinelibrary.wiley.com/doi/pdf/10.1002/9781394203314.ch21","year":"2023","keywords":"risk, technical risk, system risk, obsolescence, risk management, agile risk management","abstract":"Summary Risk is generally defined as the measure of the potential inability to achieve overall program objectives within defined cost, schedule, and technical constraints. What is missing from this definition are risks associated with failing to identify and capture evolving user, system, and technical requirements, which are often driven by evolving end-user or marketplace demands. Ignoring these evolving needs introduces risks, meaning you may be developing an obsolete product or one that only partially meets end-user needs. There are many different flavors of risk management, but each of these includes considerations for defining and assessing risk (including the likelihood it will occur and the potential impact if it does), determining how to decide which risks to mitigate and how to do so, and risk monitoring. This chapter focuses on managing three types of risks to systems engineering and development: project development risk, technical risk, and obsolescence risk.","bibtex":"@inbook{doi:https://doi.org/10.1002/9781394203314.ch21,\n author = {Orosz, Michael},\n publisher = {John Wiley & Sons, Ltd},\n isbn = {9781394203314},\n title = {Managing Risk},\n booktitle = {Systems Engineering for the Digital Age},\n chapter = {21},\n pages = {463-470},\n doi = {https://doi.org/10.1002/9781394203314.ch21},\n url = {https://onlinelibrary.wiley.com/doi/abs/10.1002/9781394203314.ch21},\n eprint = {https://onlinelibrary.wiley.com/doi/pdf/10.1002/9781394203314.ch21},\n year = {2023},\n keywords = {risk, technical risk, system risk, obsolescence, risk management, agile risk management},\n abstract = {Summary Risk is generally defined as the measure of the potential inability to achieve overall program objectives within defined cost, schedule, and technical constraints. What is missing from this definition are risks associated with failing to identify and capture evolving user, system, and technical requirements, which are often driven by evolving end-user or marketplace demands. Ignoring these evolving needs introduces risks, meaning you may be developing an obsolete product or one that only partially meets end-user needs. There are many different flavors of risk management, but each of these includes considerations for defining and assessing risk (including the likelihood it will occur and the potential impact if it does), determining how to decide which risks to mitigate and how to do so, and risk monitoring. This chapter focuses on managing three types of risks to systems engineering and development: project development risk, technical risk, and obsolescence risk.}\n}\n","author_short":["Orosz, M."],"bibbaseid":"orosz-managingrisk-2023","role":"author","urls":{"Paper":"https://onlinelibrary.wiley.com/doi/abs/10.1002/9781394203314.ch21"},"keyword":["risk","technical risk","system risk","obsolescence","risk management","agile risk management"],"metadata":{"authorlinks":{}}},"bibtype":"inbook","biburl":"https://bibbase.org/f/4ZX4xZAQmtppNsqY5/mdorosz-2023.bib","dataSources":["QmcfkP8TTHWZR6A52","viXEDeFMSmYNxKQgF"],"keywords":["risk","technical risk","system risk","obsolescence","risk management","agile risk management"],"search_terms":["managing","risk","orosz"],"title":"Managing Risk","year":2023}