Iterative Development Models and Process Improvement

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


Source: Federal Reserve Bank of St. Louis

https://research.stlouisfed.org/fred2/series/UTGRAN9URN


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

http://www.huffingtonpost.com/2015/04/20/elevator-one-world-trade-center-time-lapse_n_7105280.html

https://www.youtube.com/watch?v=22oJwUJQQkI

https://www.youtube.com/watch?v=22oJwUJQQkI


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

http://www.addiesolutions.com/addie.htm

Iterative Development ModelsAnalyze, Design, Develop, Implement, Evaluate (ADDIE)

Source:Source: ADDIE Solutions, LLC


Source: NorthlandStock

Iterative DevelopmentCommon Sense

http://italian-pitbull.deviantart.com/art/Remodeling-Stock-2-524716616

Iterative DevelopmentDaily Life

Source: Allen Interactions, 2015

Iterative Development ModelsSuccessive Approximation Model (SAM)

http://www.alleninteractions.com/sam-process

Iterative Development ModelsWaterfall

Source: Douglas Hughey, University of Missouri, 2009

http://www.umsl.edu/~hugheyd/is6840/waterfall.html

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

http://blogs.globalteckz.com/characteristics-of-agile-methodology-in-software-development/

Iterative Development ModelsSurvey

Iterative Development ModelsDefinition

• Visual• Conceptual• Ideal• Sequential• Repetitive• Complex• Novel



Source: Integration and Application Network

http://ian.umces.edu/ecocheck/report-cards/chesapeake-bay/2013/overview/



Source: Competency Model Clearinghouse


http://www.careeronestop.org/CompetencyModel/competency-models/advanced-manufacturing.aspx




Research BuildPlan Launch


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

http://www.capanoandassociates.com/coaching.htm


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





• 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





• 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





• 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





• Review implemented changes.

• Re-measure performance.

Conti

nuou

s Im

prov

emen

t

Planning

Analysis

Integration

Implementation

Review





• Review implemented changes.

• Re-measure performance.

Conti

nuou

s Im

prov

emen

t

Planning

Analysis

Integration

Implementation

Review



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.


Iterative Development ModelsCommon Phases (Engineering)

http://www.sciencebuddies.org/engineering-design-process/engineering-design-compare-scientific-method.shtml


Define the problem.





Test solution.










Define the problem.





Test solution.










Define the problem.





Test solution.










Define the problem.





Test solution.








Define the problem.





Test solution.









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



Agile

Source: globalteckz.com


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

http://blogs.globalteckz.com/characteristics-of-agile-methodology-in-software-development/

Source: NextGeneration Recruitment


http://www.nextgeneration.ie/Expert-Advice/agile-vs-waterfall-who-builds-the-better-house.html

Source: Commonplaces


http://www.commonplaces.com/blog/agile-vs-waterfall-how-approach-your-web-development-project

“…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


http://www.agilenutshell.com/agile_vs_waterfall

http://www.base36.com/2012/12/agile-waterfall-methodologies-a-side-by-side-comparison/



https://blog.udemy.com/agile-vs-waterfall/

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.”


“… collaboration is more important… than design.”



http://www.agilenutshell.com/agile_vs_waterfall



“…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


http://csse.usc.edu/csse/TECHRPTS/1983/usccse83-501/usccse83-501.pdf


“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





“…the implementation described above is risky and invites failure.”

– Winston W. Royce, 1970


http://www.serena.com/docs/agile/papers/Managing-The-Development-of-Large-Software-Systems.pdf


Source: Winston W. Royce, 1970




Source: ADDIE Solutions, LLC



Source: Allen Interactions



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



http://www.amazon.com/Leaving-Addie-Sam-Developing-Experiences/dp/1562867113/ref=sr_1_1?ie=UTF8&qid=1432683108&sr=8-1&keywords=leaving+addie+for+sam

Instructional Systems Design (ISD) Model

Source: Branson et al., 1975


http://www.dtic.mil/dtic/tr/fulltext/u2/a019486.pdf



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



http://www.cio.com/article/2385322/agile-development/why-agile-isn-t-working--bringing-common-sense-to-agile-principles.html








“…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

http://dose.wallacehannum.com/ISD%20Retrospective.pdf



“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

http://www.delaney.typepad.com/files/drop_your_tools.pdf



http://www.goodreads.com/quotes/558213-learn-the-rules-like-a-pro-so-you-can-break


Source: Google Maps

The process of gaining expert-level knowledge helps to clarify where you are, where you’re going, and why.

https://www.google.com/maps/@40.8066562,-80.2278556,441531m/data=!3m1!1e3!6m1!1e1

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

http://www.amazon.com/Managing-Writers-World-Technical-Documentation/dp/0982219105

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

http://www.amazon.com/Anarchists-Approach-Building-Business-Zingermans/dp/0964895684




“I would suggest very strongly that the more we tolerate gaps… the lower our credibility as leaders…”


Using Iterative Development ModelsMinding the Gap


“In my experience, it’s infinitely easier to rewrite a system than to meaningfully change an organizational culture.”


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

http://www.pmi.org/~/media/PDF/Publications/Enabling-Change-Through-Strategic-Initiatives.ashx

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

http://www.jiops.com/06/2011/why-process-modeling/

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

http://www.gallup.com/businessjournal/26281/the-first-element-of-great-managing.aspx

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

http://www.excellence.ca/en/knowledge-centre/articles/the-link-between-excellence-and-happiness-at

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

http://ats.se/suppliers-faro-products.html

http://www.laserscanningforum.com/forum/viewtopic.php?f=89&t=4083

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

http://dashandapinch.com/2012/07/jelly-bean-tini/

http://www.mymodernmet.com/profiles/blogs/kristen-cumings-jelly-belly-masterpieces-of-confectionary-art

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

http://www.woodsmithtips.com/2010/02/04/miters-on-the-table-saw/

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

http://www.jiops.com/06/2011/why-process-modeling/

ConclusionQuestions??

Iterative Development Models and Process Improvement

Design

addie source

process improvement

great design

addie solutions

form improvement team

process order ship order

client acceptance

quality content