Traditional software engineering deals with two phases of a product lifecycle: Development and Maintenance. In this short paper we propose to take a different approach and look at the product’s lifecycle using an analogy with the human lifecycle. We use this analogy to define roles that we call ‘research’, ‘engineering’, and ‘support’ to accommodate all the required activities that will keep a product useful for the longest period possible, while at the same time giving rapid response to customer needs.
A big part of process improvement is managing the transition. Many books have been written about how to do this, yet there is a paucity of strategies that can be tied to real life variables. In this Appendix to our book (in translation from Spanish) we explore such strategies and suggest a parsimonious approach whenever possible.
This is the second chapter of the authors' own translation of the award winning book The Story of Tahini-Tahini: Process Improvement and Agile Methods with the MPS Model. Originally published in Portuguese and already in Spanish. This Chapter deals with Process Improvement and how to make it work.
The value of DevOps is most often considered from the supply-side view of Dev. But Demand is what makes DevOps important, and Ops is central to the demand-side view.
Mary Poppendieck: The Aware Organization - Lean IT Summit 2014Institut Lean France
We now have a pretty good idea of what Just-in-Time means in software development. With Continuous Delivery moving to the mainstream, rapid flow of value through the development process is becoming routine. However, as software systems get larger and more complex, we may lose sight of what Jidoka has to offer. At the Lean IT Summit 2014, Mary Poppendieck explained what Jidoka, or situational awareness, means for groups developing large software systems.
A big part of process improvement is managing the transition. Many books have been written about how to do this, yet there is a paucity of strategies that can be tied to real life variables. In this Appendix to our book (in translation from Spanish) we explore such strategies and suggest a parsimonious approach whenever possible.
This is the second chapter of the authors' own translation of the award winning book The Story of Tahini-Tahini: Process Improvement and Agile Methods with the MPS Model. Originally published in Portuguese and already in Spanish. This Chapter deals with Process Improvement and how to make it work.
The value of DevOps is most often considered from the supply-side view of Dev. But Demand is what makes DevOps important, and Ops is central to the demand-side view.
Mary Poppendieck: The Aware Organization - Lean IT Summit 2014Institut Lean France
We now have a pretty good idea of what Just-in-Time means in software development. With Continuous Delivery moving to the mainstream, rapid flow of value through the development process is becoming routine. However, as software systems get larger and more complex, we may lose sight of what Jidoka has to offer. At the Lean IT Summit 2014, Mary Poppendieck explained what Jidoka, or situational awareness, means for groups developing large software systems.
How to Build Organizational Change Capabilities - Prosci WebinarTim Creasey
Prosci Webinar - How to Build Organizational Change Capabilities. Agenda: 1) What is Project ECM? 2) The case for Project ECM; 3) The status of Project ECM; 4) Current state, Future state, Transition state; 5) Prosci ECM Suite. Visit www.prosci.com/ecm to learn more about the Prosci ECM Suite.
Prosci Building Organizational Agility WebinarTim Creasey
Prosci's webinar "Building Organizational Agility" - delivered live on Wednesday, Feb 3 11:00 AM EST and Thursday, Feb 4 4:00 PM EST. Register at www.prosci.com/webinars
Many organizations struggle with implementing process improvement. Senior managers set goals and timelines. Process groups develop improvement plans. Appraisals are held. But at a fundamental level, the engineers, project managers, and functional manager simply refuse to change their behaviors. The organization “goes through the motions”, but there is no visible progress, or simply rote adherence to process, not an embracing of mature practices.This presentation will examine the principles behind process improvement, as they relate to attitudes, beliefs, and behaviors about CMMI. Specific attention will be given to the psychological reasons for resistance, and how they differ among practitioners. Methods for identifying resistance will be identified, and practical guidance will be given for overcoming barriers and challenges resulting from personal resistance to change. The presentation will be useful to anyone looking to jump-start improvement, revitalize a failing initiative, or maintain a maturity level.
Benefits of Agile Software Development for Senior ManagementDavid Updike
This is a presentation to Senior and Executive Managers which is used to explain how Agile Software Development processes and practices benefit them, their organization and their customers.
This is a session on Lean Principles for Agile Teams presented at ERUC in October 2013. This is the deck used with the LEGO building block exercise PDF.
Lean & Agile Enterprise Frameworks: For Managing Large U.S. Government Cloud ...David Rico
This is a presentation on "Lean & Agile Enterprise Frameworks: For Managing Large U.S. Government Cloud Computing Projects," which are emerging models for managing high-risk, time-sensitive R&D-oriented new product development (NPD) projects with demanding customers and fast-changing market conditions (at the enterprise, portfolio, and program levels). It establishes the context, provide a definition, and describe the value-system for lean and agile program and project management. It provides a brief survey and comparative analysis of the pros and cons of emerging lean and agile frameworks such as Enterprise Scrum, LeSS, DaD, SAFe, and RAGE. Then it describes the Scaled Agile Academy's Scaled Agile Framework (SAFe) in greater detail (which is the de facto international standard for scaling the use of agile methods to the enterprise, portfolio, and program levels for both systems and software development). SAFe is hybrid model best known for "blending" megatrends such as lean and agile principles into a single unified framework, establishing an authoritative foundation for scaling agile methods to large-scale private and public sector programs, and unifying East (lean) and West (agile) into a common language for systems and software development that is both lean "and" agile. In addition to SAFe case studies, late-breaking developments on the use of "Continuous Delivery," "DevOps," and bleeding-edge "Unstructured Web Databases" at Google and Amazon to automate large sections of the enterprise value stream will be discussed (which has been successfully used by some of the world's largest firms to boost organizational productivity by one or two orders of magnitude). This briefing has been warmly received by multiple U.S. government agencies, contractors, and PMI audiences throughout Baltimore-Washington, DC.
Make it better: the importance of a risk-based approach to DFMATeam Consulting Ltd
Team Consulting's Stuart Kay was invited by PMPS Magazine to talk about why analysing risk as part of the manufacturing process is as important as the traditional approach to DFMA.
Follow PMPS on Twitter: @PMPSmagazine
subscribe to PMPS: http://www.samedanltd.com/magazine/15
In software development, Agile’s practices have the advantage of encouraging teamwork by breaking down barriers between various teams in sales, development, business consulting, operations, and IT.
This was a presentation given by Penny Hubbard-Brown and Stephen Wong of Mace to the APM Hong Kong branch membership and guests. The presentation was entitled 'What is proactive project management?'
How to Build Organizational Change Capabilities - Prosci WebinarTim Creasey
Prosci Webinar - How to Build Organizational Change Capabilities. Agenda: 1) What is Project ECM? 2) The case for Project ECM; 3) The status of Project ECM; 4) Current state, Future state, Transition state; 5) Prosci ECM Suite. Visit www.prosci.com/ecm to learn more about the Prosci ECM Suite.
Prosci Building Organizational Agility WebinarTim Creasey
Prosci's webinar "Building Organizational Agility" - delivered live on Wednesday, Feb 3 11:00 AM EST and Thursday, Feb 4 4:00 PM EST. Register at www.prosci.com/webinars
Many organizations struggle with implementing process improvement. Senior managers set goals and timelines. Process groups develop improvement plans. Appraisals are held. But at a fundamental level, the engineers, project managers, and functional manager simply refuse to change their behaviors. The organization “goes through the motions”, but there is no visible progress, or simply rote adherence to process, not an embracing of mature practices.This presentation will examine the principles behind process improvement, as they relate to attitudes, beliefs, and behaviors about CMMI. Specific attention will be given to the psychological reasons for resistance, and how they differ among practitioners. Methods for identifying resistance will be identified, and practical guidance will be given for overcoming barriers and challenges resulting from personal resistance to change. The presentation will be useful to anyone looking to jump-start improvement, revitalize a failing initiative, or maintain a maturity level.
Benefits of Agile Software Development for Senior ManagementDavid Updike
This is a presentation to Senior and Executive Managers which is used to explain how Agile Software Development processes and practices benefit them, their organization and their customers.
This is a session on Lean Principles for Agile Teams presented at ERUC in October 2013. This is the deck used with the LEGO building block exercise PDF.
Lean & Agile Enterprise Frameworks: For Managing Large U.S. Government Cloud ...David Rico
This is a presentation on "Lean & Agile Enterprise Frameworks: For Managing Large U.S. Government Cloud Computing Projects," which are emerging models for managing high-risk, time-sensitive R&D-oriented new product development (NPD) projects with demanding customers and fast-changing market conditions (at the enterprise, portfolio, and program levels). It establishes the context, provide a definition, and describe the value-system for lean and agile program and project management. It provides a brief survey and comparative analysis of the pros and cons of emerging lean and agile frameworks such as Enterprise Scrum, LeSS, DaD, SAFe, and RAGE. Then it describes the Scaled Agile Academy's Scaled Agile Framework (SAFe) in greater detail (which is the de facto international standard for scaling the use of agile methods to the enterprise, portfolio, and program levels for both systems and software development). SAFe is hybrid model best known for "blending" megatrends such as lean and agile principles into a single unified framework, establishing an authoritative foundation for scaling agile methods to large-scale private and public sector programs, and unifying East (lean) and West (agile) into a common language for systems and software development that is both lean "and" agile. In addition to SAFe case studies, late-breaking developments on the use of "Continuous Delivery," "DevOps," and bleeding-edge "Unstructured Web Databases" at Google and Amazon to automate large sections of the enterprise value stream will be discussed (which has been successfully used by some of the world's largest firms to boost organizational productivity by one or two orders of magnitude). This briefing has been warmly received by multiple U.S. government agencies, contractors, and PMI audiences throughout Baltimore-Washington, DC.
Make it better: the importance of a risk-based approach to DFMATeam Consulting Ltd
Team Consulting's Stuart Kay was invited by PMPS Magazine to talk about why analysing risk as part of the manufacturing process is as important as the traditional approach to DFMA.
Follow PMPS on Twitter: @PMPSmagazine
subscribe to PMPS: http://www.samedanltd.com/magazine/15
In software development, Agile’s practices have the advantage of encouraging teamwork by breaking down barriers between various teams in sales, development, business consulting, operations, and IT.
This was a presentation given by Penny Hubbard-Brown and Stephen Wong of Mace to the APM Hong Kong branch membership and guests. The presentation was entitled 'What is proactive project management?'
This Book https://bin95.com/ebooks/quality-course-management.htm is Currently Used At Universities And The Q-Course Foundation Exams Are Approved By State Ministry For Education.
This book is for everyone involved in quality in an organization. This book will help you obtain total quality management, a must-read for the organizational change management process. Also offers experience in testing & quality standards and methodologies of TMap, Testframe, ITIL, ISO 9001, TQM, Prince2, RUP, CMM, TMM, and ISEB.
The book excerpts here are ...
* Quality & Organization
* The Development Process
* Quality in the Project Organization
A short introduction of the book "From Zero To Agile".
How you can introduce change to your organisation to BE agile.
Every chapter is summarised and the main concepts outlined.
A retrospective example is presented for each topic.
A design process is a systematic problem-solving strategy, with criteria and constraints, used to develop many possible solutions to solve or satisfy human needs or wants and to narrow down the possible solutions to one final choice.
In this Slideshare i had define about product and services.
difference between product and services.
types of product and services.
if you like my presentation do like and follow.
Thank you
Presentation by Joan Starr at Code4Lib 2007 in Athens, GA
Academic digital libraries face serious challenges in trying to adopt agile project management techniques. While there have always been significant differences between how an academic and a corporate team might solve a problem, today, digital library and corporate offerings are often in direct competition. Time-to-market is more important than ever before. This talk will identify the most troublesome characteristics of academic bureaucracies and make suggestions for working around these obstacles.
A MAPPING MODEL FOR TRANSFORMING TRADITIONAL SOFTWARE DEVELOPMENT METHODS TO ...ijseajournal
Agility is bringing in responsibility and ownership in individuals, which will eventually bring out effectiveness and efficiency in deliverables. Agile model is growing in the market at very good pace.Companies are drifting from traditional Software Development Life Cycle models to Agile Environment for the purpose of attaining quality and for the sake of saving cost and time. Nimbleness nature of Agile is helpful in frequent releases so as to satisfy the customer by providing frequent dual feedback. In Traditional models, life cycle is properly defined and also phases are elaborated by specifying needed input
and output parameters. On the other hand, in Agile environment, phases are specific to methodologies of Agile - Extreme Programming etc. In this paper a common life cycle approach is proposed that is applicable for different kinds of teams. The paper aims to describe a mapping function for mapping of traditional methods to Agile method.
Increasing project success rates using project behavioral coachingWGroup
This strategy brief discusses the use of project behavioral coaching, which is a technique based on the science of human behavior that can be used with any methodology to drive up success. Covers the high level steps used in performing the project behavioral coaching™ (PBC) technique as a guide for project professionals that desire an introduction to learning the basics.
Design Thinking : Prototyping & TestingSankarshan D
The design team will now produce a number of inexpensive, scaled down versions of the product or specific features found within the product, so they can investigate the problem solutions generated in the previous stage. Prototypes may be shared and tested within the team itself, in other departments, or on a small group of people outside the design team.
https://www.interaction-design.org/literature/article/5-stages-in-the-design-thinking-process
Similar to From Lust to Dust: A Product Life Cycle (20)
MPS and Agile Methods references in englishJorge Boria
The references for the whole Tahini-Tahini story. So far the Prologue, and Chapters 1 and 2 have been uploaded. You can write me for versions in Spanish and Portuguese.
Small organizations have very limited resources. This implies that traditional approaches to SPI will probably sink before they succeed for lack of sustaining funding. This white paper shows a proven approach to institutionalizing a managed behavior and beyond, by effecting small incremental changes that are easy to install individually but that collectively achieve most of the required specific practices at ML2. The presentation addresses a niche audience that usually has great difficulty in finding applicable processes and experiences that match their needs. In particular, small organizations, or process engineers working with small organizations; but also, organizations that cultivate individual dissonance in opposition to synchronicity or democratic decisions can benefit from it.
La última entrega de mi serie sobre el CMMI SVC. Como en la anterior, me enfoco en una de las dos áreas de gestión de trabajo que son exclusivas del modelo SVC, en este caso continuidad de servicios (SCON)
This is the second upload of the book "The Story of Tahini-Tahini: Software Process Improvement with Agile Methods and Maturity Models". We are seeking help to find mistakes and perfect the book.
The Story of Tahini-Tahini: Software Process Improvement with Agile Methods a...Jorge Boria
This is the first part of the book "The Story of Tahini-Tahini: Software Process Improvement with Agile Methods and Maturity Models" that we are crowd reviewing. Please review and send us comments to improve its quality. Thanks.
Versión final del libro "Mejora de Procesos de Software con Métodos Ágiles y Modelo de Madurez MPS: La Historia de Tahini-Tahini" Para una versión Kindle o en papel, recurrir a Amazon.com.
This is a mock up appraisal of an imaginary oilfield services organization, performed against the CMMI SVC practices. It is based on my own experience as a certified high maturity lead appraiser of the CMMI DEV and SVC constellations and a past experience in one of the world's leaders in consulting with a specialty in oilfield services. The article is meant to illuminate how the practices are pertinent in that particular industry. It was developed a few years ago as part of the requisites to become certified for SVC by (then) the SEI.
Although Causal Analysis and Resolution (CAR) is staged at Level 5 of the CMMI, it is a useful compendium of good practices for a company that starts its process improvement road. This mapping is designed to help organizations perform CAR at all levels. Borrowing from the defunct "advanced practices" paradigm, it describes what the practice would be like at different levels of capability within the process area. For example, almost all practices are described for capability level 1, thus providing guidance on how to start preventing defects from recurring.
Effectiveness of Organizational TrainingJorge Boria
The request to measure effectiveness of the training performed at an organization is not met by the "beauty contest" survey taken at the end of an activity. Moreover, since 85% of knowledge acquired by adults is lost in two weeks unless used, as reported by Jane Tippett in Nurses’ acquisition and retention of knowledge after trauma training, it is of fundamental importance that the gauge corresponds to the needs. In this presentation we describe a low tech yet highly effective method for measuring the improvement in productivity gained by training attendees. The method, used since last century in a large telecom organization, is based on some premises: training is only useful if aligned with job outcomes; training should be timely and not carried out solely for consuming the training budget; training objectives should be described as learning objectives, that is to say, what behavioral changes the training is attempting to achieve; managers are responsible for the skills and competencies of their employees.
An introduction to the latest addition to the CMMI constellations of the SEI. This material reflects the model as it was in July 2011. Since the SEI can and will introduce changes to the model, this material could be dated when you access it. Treat it as a simplistic view of the true content and DO find the current status from the right source: The SEI itself.
Three original implementations of the quality assurance role in two different companies. How creative management can solve the problem of making QA be both a career path and a positive influence in the process improvement path.
Software organizations that want to maximize the yield of Software Testing find that choosing the right testing strategy is hard, and most testing managers are ill-prepared for this. The organization has to learn how to plan testing efforts based on the characteristics of each project and the many ways the software product is to be used. This tutorial is intended for Software professionals who are likely to be responsible for defining the strategy and planning of the testing effort and managing it through its life cycle. These roles are usually Testing Managers or Project Managers.
"𝑩𝑬𝑮𝑼𝑵 𝑾𝑰𝑻𝑯 𝑻𝑱 𝑰𝑺 𝑯𝑨𝑳𝑭 𝑫𝑶𝑵𝑬"
𝐓𝐉 𝐂𝐨𝐦𝐬 (𝐓𝐉 𝐂𝐨𝐦𝐦𝐮𝐧𝐢𝐜𝐚𝐭𝐢𝐨𝐧𝐬) is a professional event agency that includes experts in the event-organizing market in Vietnam, Korea, and ASEAN countries. We provide unlimited types of events from Music concerts, Fan meetings, and Culture festivals to Corporate events, Internal company events, Golf tournaments, MICE events, and Exhibitions.
𝐓𝐉 𝐂𝐨𝐦𝐬 provides unlimited package services including such as Event organizing, Event planning, Event production, Manpower, PR marketing, Design 2D/3D, VIP protocols, Interpreter agency, etc.
Sports events - Golf competitions/billiards competitions/company sports events: dynamic and challenging
⭐ 𝐅𝐞𝐚𝐭𝐮𝐫𝐞𝐝 𝐩𝐫𝐨𝐣𝐞𝐜𝐭𝐬:
➢ 2024 BAEKHYUN [Lonsdaleite] IN HO CHI MINH
➢ SUPER JUNIOR-L.S.S. THE SHOW : Th3ee Guys in HO CHI MINH
➢FreenBecky 1st Fan Meeting in Vietnam
➢CHILDREN ART EXHIBITION 2024: BEYOND BARRIERS
➢ WOW K-Music Festival 2023
➢ Winner [CROSS] Tour in HCM
➢ Super Show 9 in HCM with Super Junior
➢ HCMC - Gyeongsangbuk-do Culture and Tourism Festival
➢ Korean Vietnam Partnership - Fair with LG
➢ Korean President visits Samsung Electronics R&D Center
➢ Vietnam Food Expo with Lotte Wellfood
"𝐄𝐯𝐞𝐫𝐲 𝐞𝐯𝐞𝐧𝐭 𝐢𝐬 𝐚 𝐬𝐭𝐨𝐫𝐲, 𝐚 𝐬𝐩𝐞𝐜𝐢𝐚𝐥 𝐣𝐨𝐮𝐫𝐧𝐞𝐲. 𝐖𝐞 𝐚𝐥𝐰𝐚𝐲𝐬 𝐛𝐞𝐥𝐢𝐞𝐯𝐞 𝐭𝐡𝐚𝐭 𝐬𝐡𝐨𝐫𝐭𝐥𝐲 𝐲𝐨𝐮 𝐰𝐢𝐥𝐥 𝐛𝐞 𝐚 𝐩𝐚𝐫𝐭 𝐨𝐟 𝐨𝐮𝐫 𝐬𝐭𝐨𝐫𝐢𝐞𝐬."
Enterprise Excellence is Inclusive Excellence.pdfKaiNexus
Enterprise excellence and inclusive excellence are closely linked, and real-world challenges have shown that both are essential to the success of any organization. To achieve enterprise excellence, organizations must focus on improving their operations and processes while creating an inclusive environment that engages everyone. In this interactive session, the facilitator will highlight commonly established business practices and how they limit our ability to engage everyone every day. More importantly, though, participants will likely gain increased awareness of what we can do differently to maximize enterprise excellence through deliberate inclusion.
What is Enterprise Excellence?
Enterprise Excellence is a holistic approach that's aimed at achieving world-class performance across all aspects of the organization.
What might I learn?
A way to engage all in creating Inclusive Excellence. Lessons from the US military and their parallels to the story of Harry Potter. How belt systems and CI teams can destroy inclusive practices. How leadership language invites people to the party. There are three things leaders can do to engage everyone every day: maximizing psychological safety to create environments where folks learn, contribute, and challenge the status quo.
Who might benefit? Anyone and everyone leading folks from the shop floor to top floor.
Dr. William Harvey is a seasoned Operations Leader with extensive experience in chemical processing, manufacturing, and operations management. At Michelman, he currently oversees multiple sites, leading teams in strategic planning and coaching/practicing continuous improvement. William is set to start his eighth year of teaching at the University of Cincinnati where he teaches marketing, finance, and management. William holds various certifications in change management, quality, leadership, operational excellence, team building, and DiSC, among others.
3.0 Project 2_ Developing My Brand Identity Kit.pptxtanyjahb
A personal brand exploration presentation summarizes an individual's unique qualities and goals, covering strengths, values, passions, and target audience. It helps individuals understand what makes them stand out, their desired image, and how they aim to achieve it.
Implicitly or explicitly all competing businesses employ a strategy to select a mix
of marketing resources. Formulating such competitive strategies fundamentally
involves recognizing relationships between elements of the marketing mix (e.g.,
price and product quality), as well as assessing competitive and market conditions
(i.e., industry structure in the language of economics).
Cracking the Workplace Discipline Code Main.pptxWorkforce Group
Cultivating and maintaining discipline within teams is a critical differentiator for successful organisations.
Forward-thinking leaders and business managers understand the impact that discipline has on organisational success. A disciplined workforce operates with clarity, focus, and a shared understanding of expectations, ultimately driving better results, optimising productivity, and facilitating seamless collaboration.
Although discipline is not a one-size-fits-all approach, it can help create a work environment that encourages personal growth and accountability rather than solely relying on punitive measures.
In this deck, you will learn the significance of workplace discipline for organisational success. You’ll also learn
• Four (4) workplace discipline methods you should consider
• The best and most practical approach to implementing workplace discipline.
• Three (3) key tips to maintain a disciplined workplace.
Buy Verified PayPal Account | Buy Google 5 Star Reviewsusawebmarket
Buy Verified PayPal Account
Looking to buy verified PayPal accounts? Discover 7 expert tips for safely purchasing a verified PayPal account in 2024. Ensure security and reliability for your transactions.
PayPal Services Features-
🟢 Email Access
🟢 Bank Added
🟢 Card Verified
🟢 Full SSN Provided
🟢 Phone Number Access
🟢 Driving License Copy
🟢 Fasted Delivery
Client Satisfaction is Our First priority. Our services is very appropriate to buy. We assume that the first-rate way to purchase our offerings is to order on the website. If you have any worry in our cooperation usually You can order us on Skype or Telegram.
24/7 Hours Reply/Please Contact
usawebmarketEmail: support@usawebmarket.com
Skype: usawebmarket
Telegram: @usawebmarket
WhatsApp: +1(218) 203-5951
USA WEB MARKET is the Best Verified PayPal, Payoneer, Cash App, Skrill, Neteller, Stripe Account and SEO, SMM Service provider.100%Satisfection granted.100% replacement Granted.
VAT Registration Outlined In UAE: Benefits and Requirementsuae taxgpt
Vat Registration is a legal obligation for businesses meeting the threshold requirement, helping companies avoid fines and ramifications. Contact now!
https://viralsocialtrends.com/vat-registration-outlined-in-uae/
[Note: This is a partial preview. To download this presentation, visit:
https://www.oeconsulting.com.sg/training-presentations]
Sustainability has become an increasingly critical topic as the world recognizes the need to protect our planet and its resources for future generations. Sustainability means meeting our current needs without compromising the ability of future generations to meet theirs. It involves long-term planning and consideration of the consequences of our actions. The goal is to create strategies that ensure the long-term viability of People, Planet, and Profit.
Leading companies such as Nike, Toyota, and Siemens are prioritizing sustainable innovation in their business models, setting an example for others to follow. In this Sustainability training presentation, you will learn key concepts, principles, and practices of sustainability applicable across industries. This training aims to create awareness and educate employees, senior executives, consultants, and other key stakeholders, including investors, policymakers, and supply chain partners, on the importance and implementation of sustainability.
LEARNING OBJECTIVES
1. Develop a comprehensive understanding of the fundamental principles and concepts that form the foundation of sustainability within corporate environments.
2. Explore the sustainability implementation model, focusing on effective measures and reporting strategies to track and communicate sustainability efforts.
3. Identify and define best practices and critical success factors essential for achieving sustainability goals within organizations.
CONTENTS
1. Introduction and Key Concepts of Sustainability
2. Principles and Practices of Sustainability
3. Measures and Reporting in Sustainability
4. Sustainability Implementation & Best Practices
To download the complete presentation, visit: https://www.oeconsulting.com.sg/training-presentations
1. From Lust to Dust: A Product’s Life Cycle
And the Roles that Make it All Worth It
Jorge Boria, M Eng
SEI Authorized Lead Appraisers, Liveware Inc.
jorge.boria@liveware.com
Abstract:
Traditional software engineering deals with two phases of a product lifecycle:
Development and Maintenance. In this short paper we propose to take a different
approach and look at the product’s lifecycle using an analogy with the human lifecycle.
We use this analogy to define roles that we call ‘research’, ‘engineering’, and ‘support’ to
accommodate all the required activities that will keep a product useful for the longest
period possible, while at the same time giving rapid response to customer needs..
Introduction
In his novel cum essay “Zen and the Art of Motorcycle Maintenance: An Inquiry into
Values” Robert Pirsig defines quality not as an attribute but as a relation between the
object in which quality is perceived and the person that perceives that quality. His point
is that quality is elusive even if so simple, because it is so personal. Perhaps we could
paraphrase the lyrics of ‘Happiness Is’ and say Quality is different things to different
people! Even if they are discussing the same object they might have a completely
different sense of its quality.
In an in-depth tutorial on agile processes held during SEPG 2001 in New Orleans, Brian
Nejmeh pointed out that our “one-size-fits-all” approach to strategy and processes does
not meet the needs of organizations. His thesis, based on “Crossing the Chasm” is that
at every stage of a product’s life different processes are required. For example, at Stage
1 innovation and speed are key elements to capture the innovators’ minds, therefore
“quality” in this stage is measured in the bells and whistles; but moving on to the next
stage entails a different approach, where quality switches from being measured in the
number and diversity of features to reliability and availability of the product. Further down
the lifecycle, support and maintenance activities are the paramount of quality. As the
product ages, the needs of the customer change too. Hence, if we can see how a
product ages throughout its life cycle and tie it to the emphasis on one or another type of
engineering, we will be better off in dealing with the product’s (and hence, the
customer’s) needs.
The product life cycle
If we break down the life cycle of a product from before its creation to the moment it is no
longer supported, drawing from our own (human) life cycle as an analogy, we have the
following stages:
2. 1: Pre-conceptual Stage
Before a product is even conceived, a number of influences are already in place to
support its launch into this world. We can distinguish amongst them environmental
conditions, external to the organization that will use the product, including technological
assets and market needs; internal conditions including training needs and cultural drives
that make the product concept acceptable, personal skills of individuals, managers and
line personnel, together with inclination to use the new system and a desire to achieve
better results through technology. All these forces start acting together until some formal
documents are assembled to start a project with the purpose of delivering a product.
This is the pre-conceptual stage of a product. The moment the formal documents that
define the product as a concept are created we call the conception moment.
2: Engineering Stage
Once the product is envisioned, many roads are possibly explored, both inside and
outside the organization, to help with its conception. In an ideal world, there should be a
defined instant in which a project is created (budgeted and staffed) to engineer the
product. We will call the time used in the execution of this project the engineering stage.
A well-defined engineering stage has a well-defined process to describe it. Engineering
is to a product like pre-natal stages are to a person: Everyone expects the newcomer, no
one is sure what it will look like, many expectations surround it, and it almost sure that it
is going to keep us sleepless for many weeks after it arrives!
3: Birth
The engineering stage ends in deployment, also called “cut over”. This is not a stage,
but an event. It is the “birth” of the product.
4: Deployment Stage
Once a product is deployed, it usually suffers from many problems due to the
dissonance between what was required and what was produced. This stage, of tentative
use, is very much like early childhood: the product does not stand on its own, it babbles
when it wants to speak, and, in general, has to be cleaned every few hours. Think of this
as the Beta phase of the software product, usually extended well into the user’s first
attempts to apply the product in a working environment.
5: Early Adoption Stage
If the product survives its childhood, the next stage is not nice, but definitely better: it
enters its inception stage, in which many things are overlooked with the expectancy that
they will be solved in the future. A product is usually in this stage during its first two
versions, which constantly act up, destroy your expectations, and need urgent corrective
measures. Inception is a lot like adolescence.
3. 6: Institutionalization Stage
As a product matures the users learn to trust it, and at one point it becomes
institutionalized into common use. The product has achieved, like some grown-ups,
maturity and reliability. During this stage most changes are enhancements that are not
difficult to implement and possibly some adjustments to environmental changes.
7: Decay Stage
The accumulation of changes over long periods of time, or new technological developments, finally take a toll on the design and the product ages rapidly. During the decay
stage, the product is progressively less reliable, it becomes harder and harder to
maintain, it cannot be adjusted to the new technology, and people tend to work around it,
instead of through it. Then, one day, someone pulls the plug and the product is gone,
possibly replaced by a newer one, which the demised one has partially supported during
its childhood. A pictorial view of the life cycle is presented in Figure 1.
Development Roles
The figure below depicts the relationship of customer needs to the engineering and
support environment. We prefer the names ‘engineering’ and ‘support’ to the traditional
‘development’ and ‘maintenance’, since we do not think of maintenance as a phase in
the development cycle, or as the environment that is created after delivery, which we call
support (the tiny arrows that show as quick fixes in the figure). Maintenance activities
take place either in the support environment or in a normal project environment.
We define maintenance here as the application to an existing product of any one of the
following four processes: “additions”, “fixes”, “adjustments”, or “migrations”. Additions are
extensions to the product. Fixes are changes done to the product to eliminate its defects.
Adjustments are changes done to the product to accommodate external changes (e.g.,
the basic tenets in the underlying discipline have changed.) Migrations are induced by
changes in the underlying technology platform. As a general rule, only fixes are done
during support, while for additions, adjustments, large clusters of fixes, and migrations,
new projects are created and they operate in the engineering mode. These activities are
therefore part of the normal development cycle for a subsequent version of a product
that has already been created. During the life cycle, the people that work with the
product operate in different “roles” to achieve their goals. We will use a model that
describes three different roles [Trab90].
4. Figure 1: Product Life Cycle vs. Project Life Cycle
Role 1: Research and Exploration
Ideas that end up in a product are often initially created by a group that is guided by
spontaneity and inspiration [Olso93]. This group works best following an evolutionary
model, that is, building bits and pieces and tying them together into a less than
completely coherent work product, often called a “proof of concept.” The emphasis of
such a group lies in innovation. Exploration (of new technologies and ways to apply it)
and redoing are encouraged. Control is lax, although these groups usually work under a
fixed budget. Whatever they turn out is usually well received. The goals are set in long
term visions. The costs incurred in research are sunken costs to the company, that is,
they are incurred without immediate accountability.
Role 2: Engineering
The economic viability of a software product lies in its quality and in its development
costs. If quality is low, the product is not viable (see role 3 for an explanation.) If the
development costs are too high, there might not be enough market to compensate these
costs. When people work in this role they should be less concerned about innovation
and more about quality. This role is best managed through a well defined process
model, in which a requirements-gathering phase precedes the design phase, that in turn
precedes the implementation phase. (Although this so-called “waterfall model” is strictly
sequential, it is seldom the case that the developers “run” the activities in such clear-cut
order. They usually go back and forth from requirements to design. They might even
move forward to implement a little, then back to gathering requirements. However, the
nature of each activity and where each belongs in a documentation scheme should be
kept clear at all times.) Exploration is discouraged and rework is considered a necessary
evil. Control is strict, and budgetary constraints are strongly tied to project management.
Goals are now midterm, counted in the order of months, not years. The costs of activities
performed in this role are fixed, but not sunken. A product is expected as an outcome,
and the costs of the product are indirectly (as we shall see when we look at Role 3)
dependent on the expenses of the phase.
5. Role 3: Quick Fixes
Under this role, only urgent patches are tackled. Larger fixes and enhancements are
then rewoven into the fabric of the product through newer versions developed in an
iteration of role 2 (version n, n>1.0). In role 3, the process changes to “fix and ship,” the
emphasis at this time residing in immediate response. Exploration and redoing are now
punished, because otherwise control is even less attainable. The lack of control tied to
this role is linked to the fact that the costs for the role are a function of the quality of the
product. Products with poor quality are harder to maintain and enhance, incrementing
the costs of repair. This is truly bad, since now these costs are variable costs, a function
of both the number of problems found during operation and the number of corresponding
calls received.
CHARACTERISTIC
Guiding Force
Personnel
Characteristics
Ruling Principles
Control
Costs
Working Paradigm
Outcome
RESEARCH AND
EXPLORATION
Spontaneity and
Inspiration
Creative (a solution in
search of a problem)
Individual exploration
Lax
Sunken
Evolutionary
Set of Inspirational
Ideas
ROLE
ENGINEERING
Quality and
Personal Pride
Problem Solver
(applied creativity)
Discipline
Strict
Fixed
Sequential or
Spiral
Product Version
IMPLEMENTATION
AND SUPPORT
Customer Satisfaction
Problem Patcher (on-thefly fixes)
Reaction Time
Very Lax
Variable
Patch’n’go
Customer Payments
Table 1: Different Characteristics in the Roles of Operation
This means that you have to set up a “project” approach for the engineering role, and
that what you have not included in the project you cannot do later, unless you start a
follow-up project (no quick fixes will help you.) This idea of follow-up projects to modify
the product so as to comply with a set of requested changes and enhancements is
central to a good maintenance structure. It is a big part of the solution, but not all of it. It
is called ‘versioning’ and it allows for very good management practices for updates and
fixes to the product. A simplified model of versioning can be stated as managing
requests for changes by classifying them into two categories: ‘Done Immediately’ (by the
‘support’ role) and ‘Will be part of the next version release’ (and you start a follow-up
project to do it, or incorporate the requirement to an existing project.)
Conclusions
Summing up, if you don’t have creativity (research), your product runs serious risk of not
having a market, but if you don’t have engineering, the risk is that the cost of dealing
with requests for changes from customers is going to be larger than your benefits. There
is very little you can do to remedy poor quality when you are working in role 3. If you
6. want to control maintenance and support costs, since they are the only variable costs in
all three modes, you must focus on the engineering role: Focus on quality increments
the fixed costs of that role, but lowers the variable costs of the support role. Counter
intuitively for some, focusing on quality will also help raise productivity, because it
eliminates costly rework.