iterative development models and process improvement
TRANSCRIPT
Iterative Development Models and Process ImprovementTina M. Kister, PMP
IntroductionAbout Me
Education• Fine Art• Communications• Technical Communications• Online Communications
Work Experience• Fine Art• Remodeling and Construction• Advertising (Sales and Graphic Design)• Journalism• Sciences• Instructional Design (Military)• Engineering• Software• Health Care Information Technology
IntroductionAbout Me
Source: Federal Reserve Bank of St. Louis
IntroductionAbout Me
Passion• Bringing quality content together with great design to create technical communication
deliverables that are delightful, as well as informative, accurate, etc.
Sources: Huffington Post and YouTube
IntroductionAbout Me
Passion• Creating systems and tools that
streamline the delivery of communication deliverables, increasing quality and facilitating success.
Iterative Development ModelsAnalyze, Design, Develop, Implement, Evaluate (ADDIE)
Source:Source: ADDIE Solutions, LLC
Iterative Development ModelsAnalyze, Design, Develop, Implement, Evaluate (ADDIE)
Source:Source: ADDIE Solutions, LLC
Source: NorthlandStock
Iterative DevelopmentCommon Sense
Iterative DevelopmentDaily Life
Source: Allen Interactions, 2015
Iterative Development ModelsSuccessive Approximation Model (SAM)
Iterative Development ModelsWaterfall
Source: Douglas Hughey, University of Missouri, 2009
Iterative Development ModelsAgile
Source: GlobalTeckz, 2013
System Testing Release
Recording and Incorporating
Changes
Next Iteration
Yes
No
?
Sign-Off(Client Acceptance)
Start(Initial Planning)
Client Testing
Development and
Implementation
Initial Testing
Development and
Implementation
Higher-Level Planning
Requirements Definition
Iterative Development ModelsSurvey
Iterative Development ModelsDefinition
• Visual• Conceptual• Ideal• Sequential• Repetitive• Complex• Novel
Iterative Development ModelsDefinition
• Visual• Conceptual• Ideal• Sequential• Repetitive• Complex• Novel
Source: Integration and Application Network
Iterative Development ModelsDefinition
• Visual• Conceptual• Ideal• Sequential• Repetitive• Complex• Novel
Source: Competency Model Clearinghouse
• Visual• Conceptual• Ideal• Sequential• Repetitive• Complex• Novel
Iterative Development ModelsDefinition
• Visual• Conceptual• Ideal• Sequential• Repetitive• Complex• Novel
Iterative Development ModelsDefinition
Research BuildPlan Launch
• Visual• Conceptual• Ideal• Sequential• Repetitive• Complex• Novel
Order Received
Process Order
Ship Order
Goods Delivered
Discovery
• Discovery• Planning• Implementation• Review• Refinement• Maintenance
Planning
Implementation
Review
RefinementMaintenance
Iterative Development ModelsCommon Phases
• Discovery• Planning• Implementation• Review• Refinement
Iterative Development ModelsCommon Phases (Business Process Improvement)
• Identify topic.• Gain sponsorship and
support.• Form improvement
team.• Define customer
requirements.
Conti
nuou
s Im
prov
emen
t
Planning
Analysis
Integration
Implementation
Review
Source: Campano & Associates
• Discovery• Planning• Implementation• Review• Refinement
Iterative Development ModelsCommon Phases (Business Process Improvement)
• Identify topic.• Gain sponsorship and
support.• Form improvement
team.• Define customer
requirements.
Conti
nuou
s Im
prov
emen
t
Planning
Analysis
Integration
Implementation
Review
Source: Campano & Associates
• Discovery• Planning• Implementation• Review• Refinement
Iterative Development ModelsCommon Phases
• Flowchart current processes.
• Analyze current performance (capture data).
• Prioritize process inefficiencies.
• Document new processes, roles, and responsibilities.Co
ntinu
ous
Impr
ovem
ent
Planning
Analysis
Integration
Implementation
Review
Source: Campano & Associates
• Discovery• Planning• Implementation• Review• Refinement
Iterative Development ModelsCommon Phases
• Propose changes and implementation plan.
• Seek endorsement of proposals.
• Communicate with process stakeholders.
Conti
nuou
s Im
prov
emen
t
Planning
Analysis
Integration
Implementation
Review
Source: Campano & Associates
• Discovery• Planning• Implementation• Review• Refinement
Iterative Development ModelsCommon Phases
• Design, build, and test endorsed improvements.
• Implement endorsed improvements.
• Manage change.• Communicate with
process users.
Conti
nuou
s Im
prov
emen
t
Planning
Analysis
Integration
Implementation
Review
Source: Campano & Associates
• Discovery• Planning• Implementation• Review• Refinement
Iterative Development ModelsCommon Phases
• Review implemented changes.
• Re-measure performance.
Conti
nuou
s Im
prov
emen
t
Planning
Analysis
Integration
Implementation
Review
Source: Campano & Associates
• Discovery• Planning• Implementation• Review• Refinement
Iterative Development ModelsCommon Phases
• Review implemented changes.
• Re-measure performance.
Conti
nuou
s Im
prov
emen
t
Planning
Analysis
Integration
Implementation
Review
Source: Campano & Associates
Source: Science Buddies
Define the problem.
Do background research.
Specify requirements.
Brainstorm, evaluate, and choose solution.
Develop and prototype solution.
Test solution.
Communicate results.
Solution meets requirements.Solution does not meet requirements
or partially meets requirements.
Based on results and data, make design changes, prototype, test
again, and review new data.
• Discovery• Planning• Implementation• Review• Refinement
Iterative Development ModelsCommon Phases (Engineering)
Source: Science Buddies
Define the problem.
Do background research.
Specify requirements.
Brainstorm, evaluate, and choose solution.
Develop and prototype solution.
Test solution.
Communicate results.
Solution meets requirements.Solution does not meet requirements
or partially meets requirements.
Based on results and data, make design changes, prototype, test
again, and review new data.
• Discovery• Planning• Implementation• Review• Refinement
Iterative Development ModelsCommon Phases (Engineering)
Source: Science Buddies
Define the problem.
Do background research.
Specify requirements.
Brainstorm, evaluate, and choose solution.
Develop and prototype solution.
Test solution.
Communicate results.
Solution meets requirements.Solution does not meet requirements
or partially meets requirements.
Based on results and data, make design changes, prototype, test
again, and review new data.
• Discovery• Planning• Implementation• Review• Refinement
Iterative Development ModelsCommon Phases (Engineering)
Source: Science Buddies
Define the problem.
Do background research.
Specify requirements.
Brainstorm, evaluate, and choose solution.
Develop and prototype solution.
Test solution.
Communicate results.
Solution meets requirements.Solution does not meet requirements
or partially meets requirements.
Based on results and data, make design changes, prototype, test
again, and review new data.
• Discovery• Planning• Implementation• Review• Refinement
Iterative Development ModelsCommon Phases (Engineering)
Source: Science Buddies
Define the problem.
Do background research.
Specify requirements.
Brainstorm, evaluate, and choose solution.
Develop and prototype solution.
Test solution.
Communicate results.
Based on results and data, make design changes, prototype, test
again, and review new data.
• Discovery• Planning• Implementation• Review• Refinement
Iterative Development ModelsCommon Phases (Engineering)
Source: Science Buddies
Define the problem.
Do background research.
Specify requirements.
Brainstorm, evaluate, and choose solution.
Develop and prototype solution.
Test solution.
Communicate results.
Solution meets requirements.Solution does not meet requirements
or partially meets requirements.
Based on results and data, make design changes, prototype, test
again, and review new data.
• Discovery• Planning• Implementation• Review• Refinement
Iterative Development ModelsCommon Phases (Engineering)
Waterfall
Source: Comparing Traditional Systems Analysis and Design with Agile Methodologies
Using Iterative Development ModelsExpert-Level Understanding
Agile
Waterfall
Source: Comparing Traditional Systems Analysis and Design with Agile Methodologies
Using Iterative Development ModelsExpert-Level Understanding
Agile
Source: globalteckz.com
Using Iterative Development ModelsExpert-Level Understanding
System Testing Release
Recording and Incorporating
Changes
Next Iteration
Yes
No
?
Sign-Off(Client Acceptance)
Start(Initial Planning)
Client Testing
Development and
Implementation
Initial Testing
Development and
Implementation
Higher-Level Planning
Requirements Definition
Source: NextGeneration Recruitment
Using Iterative Development ModelsExpert-Level Understanding
Source: Commonplaces
Using Iterative Development ModelsExpert-Level Understanding
“…you never know if you are going to make it until the end… you don't actually get to test your design or architecture until late in the project… you don't even know if you are building [it] right until it's too late to make any changes.”
– Agile in a Nutshell, 2015
“If a requirement error is found, or a change needs to be made, the project has to start from the beginning with all new code.”
– – Base36, 2012
“Once a step has been completed, developers can’t go back to a previous stage and make changes.”
– Base36, 2012
Waterfall is characterized as:• Rigid• Cumbersome• Risky• Entirely sequential
“The Waterfall method is incredibly rigid and inflexible.”
– Kasia Mikolk, 2013
Using Iterative Development ModelsExpert-Level Understanding
Agile is characterized as:• Collaborative • Flexible• Iterative
“…testing starts from day one.”
– Agile in a Nutshell
“Agile offers an incredibly flexible design model, promoting adaptive planning and evolutionary development.”
– Kasia Mikolk, 2013
“… collaboration is more important… than design.”
– Kasia Mikolk, 2013
Using Iterative Development ModelsExpert-Level Understanding
“…top-down specification[s]… can be terribly misleading and dangerous.”
– Herbert D. Benington, 1956 (Republished in 1983)
Design
Testing
Operational Plan
Operational SpecificationsMachine Specifications
Program Specifications
Coding Specifications
Coding
Parameter Testing (Specifications)
Assembly Testing (Specifications)
Shakedown
System Evaluation
Using Iterative Development ModelsExpert-Level Understanding
“We had a need to… recognize that things would not work well the first, second, or third time, and therefore that much independent testing was needed in successive phases…”
– Herbert D. Benington, 1956 (Republished in 1983
)
Design
Testing
Operational Plan
Operational SpecificationsMachine Specifications
Program Specifications
Coding Specifications
Coding
Parameter Testing (Specifications)
Assembly Testing (Specifications)
Shakedown
System Evaluation
Using Iterative Development ModelsExpert-Level Understanding
“…the implementation described above is risky and invites failure.”
– Winston W. Royce, 1970
Using Iterative Development ModelsExpert-Level Understanding
Source: Winston W. Royce, 1970
Using Iterative Development ModelsExpert-Level Understanding
Source: ADDIE Solutions, LLC
Using Iterative Development ModelsExpert-Level Understanding
Source: Allen Interactions
Using Iterative Development ModelsExpert-Level Understanding
Source: Allen Interactions and Leaving ADDIE for SAM: Faster, Better Learning Product Development
“SAM is a different approach… that addresses the performance need through iterations… rather than with perfectly executed giant steps. SAM challenges the notion of moving through a linear process (like ADDIE)...”
– Allen Interactions
“The ADDIE process is past its prime.”
– Allen Interactions
Using Iterative Development ModelsExpert-Level Understanding
Instructional Systems Design (ISD) Model
Source: Branson et al., 1975
Using Iterative Development ModelsExpert-Level Understanding
Using Iterative Development ModelsExpert-Level Understanding
Using Iterative Development ModelsExpert-Level Understanding
Sources: udemy blog, CIO
“…more time-consuming than the Waterfall method”
– Kasia Mikoluk
“…focusing on continuous delivery has the effect of creating an unmanageable defect backlog...”
– Lajos Moczar
“… isn’t always consistent with responsible management”
– Lajos Moczar
“Agile promises solutions it cannot deliver. It promotes sloppy requirements, hides the true cost of development and prevents effective management. Contrary to what we're told to expect, this leads to long-running projects, dissatisfied customers and an overall IT ineffectiveness.”
– Lajos Moczar
Using Iterative Development ModelsExpert-Level Understanding
Using Iterative Development ModelsExpert-Level Understanding
“…relative novices… may cling to the model and treat it as a paint-by-numbers approach. Only later, when they become more proficient, do novices adapt a more flexible approach.”
– Wallace Hannum, 2005
Using Iterative Development ModelsExpert-Level Understanding
“On the far side of complexity lies profound simplicity.”
– Karl Weick, 2004
“Learn the rules like a pro, so you can break them like an artist.”
– Often attributed to Picasso
Using Iterative Development ModelsExpert-Level Understanding
Source: Google Maps
The process of gaining expert-level knowledge helps to clarify where you are, where you’re going, and why.
Using Iterative Development ModelsGetting Started
“The benefit from any methodology comes from the discipline of figuring out what you are going to do and how you are going to do it. The details of how that methodology gets you there, while important, are secondary.”
– Richard L. Hamilton, 2009
Using Iterative Development ModelsDocumentation and Communication
“You really need to write your vision down to make it work… Yes, if you want your vision to be effective, you have to not only document it, but actually tell people about it.”
– Ari Weinzweig 2010
“If the documentation does not yet exist, there is as yet no design, only people thinking and talking about the design, which is of some value, but not much.”
– Dr. Winston W. Royce, 1970
“I would suggest very strongly that the more we tolerate gaps… the lower our credibility as leaders…”
– Ari Weinzweig 2010
Using Iterative Development ModelsMinding the Gap
“In my experience, it’s infinitely easier to rewrite a system than to meaningfully change an organizational culture.”
– Ari Weinzweig 2010
Using Iterative Development ModelsMinding the Gap
“Experts use models… by first looking at them to understand the intent of the model and see the recommended processes, then by making adjustments when applying the model to their specific circumstances…”
– Wallace Hannum, 2005
The Cost of Change• Time• Tools• Training• Talent
“Failed projects can result in huge financial losses for an organization, but a failed strategic initiative has an impact far beyond just the financials. When an organization embarks on change, it’s likely that systems, processes, vendors and, perhaps, even the overall organizational mindset (or mission) will be impacted.”
– Tricia Cabrey and Amy Haughey, Project Management Institute, 2014
DangersCostly
Bottom LineTools for Facilitating Success
BenefitsSmoother Transitions
“Good process documentation is the single most important input to developing procedural manuals and the training materials used to indoctrinate new hires into the good practices you’ve so diligently designed.”
– Rob Berg, 2011
BenefitsClearer Expectations
“When Gallup decided in the early 1990s to methodically prioritize all the aspects of work life by the degree to which each drove concrete performance, a most basic statement bubbled to the top: ‘I know what is expected of me at work.’”
– Marcus Buckingham and Curt Coffman, 1999
BenefitsStreamlined Communications
BenefitsIncreased Efficiency
BenefitsIncreased Consistency
BenefitsIncreased Quality
BenefitsDemonstrable Quality
BenefitsDemonstrable Progress
Employee Morale
Qua
lity
Source: The Link Between Excellence and Happiness at Work
BenefitsHigher Morale
Refine
Research
Analyze
Synthesize
Plan
Prepare
Implement
Feedback
Feedback
Feedback
Feedback
Feedback
Feedback
Iterative Model for Technical Information DesignExample
Iterative Model for Technical Information DesignExample
Sources: ATS and Laser Scanning Forum
Refine
Research
Analyze
Synthesize
Plan
Prepare
Implement
Feedback
Feedback
Feedback
Feedback
Feedback
Feedback
Iterative Model for Technical Information DesignSteps – Research
Refine
Research
Analyze
Synthesize
Plan
Prepare
Implement
Feedback
Feedback
Feedback
Feedback
Feedback
Feedback
Iterative Model for Technical Information DesignSteps – Analyze
Refine
Research
Analyze
Synthesize
Plan
Prepare
Implement
Feedback
Feedback
Feedback
Feedback
Feedback
Feedback
Iterative Model for Technical Information DesignSteps – Synthesize
Iterative Model for Technical Information DesignSteps – Synthesize
Sources: Dash and a Pinch and My Modern Met
Refine
Research
Analyze
Synthesize
Plan
Prepare
Implement
Feedback
Feedback
Feedback
Feedback
Feedback
Feedback
Iterative Model for Technical Information DesignSteps – Plan
Refine
Research
Analyze
Synthesize
Plan
Prepare
Implement
Feedback
Feedback
Feedback
Feedback
Feedback
Feedback
Iterative Model for Technical Information DesignSteps – Prepare
Source: Woodsmith eTips
Iterative Model for Technical Information DesignSteps – Prepare
Refine
Research
Analyze
Synthesize
Plan
Prepare
Implement
Feedback
Feedback
Feedback
Feedback
Feedback
Feedback
Iterative Model for Technical Information DesignSteps – Implement
Refine
Research
Analyze
Synthesize
Plan
Prepare
Implement
Feedback
Feedback
Feedback
Feedback
Feedback
Feedback
Iterative Model for Technical Information DesignSteps – Refine
Iterative Model for Technical Information DesignSteps – Feedback
Refine
Research
Analyze
Synthesize
Plan
Prepare
Implement
Draft
Discuss
Modify Review
Iterative Model for Technical Information DesignFeedback
SummaryUsing Iterative Development Models
• Work from an expert-level understanding.- Know where you are, where you’re going, and why.
• Get started.- Developing an iterative development model is an iterative process.
• Document and communicate the model.- Documentation leads to clarification, and communication leads to
feedback and improvement.• Narrow the gaps.
- Gaps lead to a lack of credibility.- Change both the model and the process, as needed, to bring the two
into closer alignment.
SummaryDangers
Unsuccessful implementation can lead to wasted:• Time• Tools• Training• Talent
Smoother Transitions
SummaryBenefits
Clearer Expectations
SummaryBenefits
Streamlined Communications
SummaryBenefits
Increased Collaboration
SummaryBenefits
Increased Efficiency
SummaryBenefits
Increased Quality
SummaryBenefits
Demonstrable Progress
SummaryBenefits
Higher Morale
SummaryBenefits
Increased Productivity
SummaryBenefits
Success!
SummaryBenefits
ConclusionSuccess!
Facilitating Success!Keeping the end goal in mind can make it easier to navigate the often complex and stressful process of developing processes.
“Paying attention to process through expert modeling pays off. The efficiencies gained from these simple ideas often translate into hundreds of thousands of dollars in cost savings. Creating a process model provides the foundation for improvements that are part of a holistic – rather than simply tactical – approach to achieving operational goals.”
– Rob Berg, 2011
ConclusionQuestions??