All Rights Reserved - AgileSparks
Implementing Agile in an
environment that requires
strict certification
Dr. Ronen Bar-Na...
All Rights Reserved - AgileSparks
Agenda
• DO178
• Main challenges
• Flow example for implementing Agile & DO178
• My 2c -...
All Rights Reserved - AgileSparks
3
What is DO-178?
• Addresses the life process of developing embedded
software in aircra...
All Rights Reserved - AgileSparks
3
Traceability
Matrix
Configuration
Item )CSCI)
SW Req.
HLRs
CSCI Req .
Spec
Req.
Review...
All Rights Reserved - AgileSparks
DO 178
CSCI
All Rights Reserved - AgileSparks
Main Challenges
Certification Project
• Full Traceability
• Verification /Validation
• N...
All Rights Reserved - AgileSparks
DO 178B
‫של‬ ‫אינטגרציה‬
‫עבר‬ ‫שכבר‬ ‫מוצר‬
‫רישיון‬
‫ב‬ ‫פשוט‬ ‫פיתוח‬-
‫סגור‬partitio...
All Rights Reserved - AgileSparks
Key Lean/Agile Frameworks
Kanban
Focus on optimizing the end
to end flow of value and
en...
All Rights Reserved - AgileSparks
Kanban Practices in a Nutshell
+ Make process policies explicit
+ Improve collaborativel...
All Rights Reserved - AgileSparks
Optimize the whole value stream
End to End Flow – The States
Planning Phase
• Plans &
St...
All Rights Reserved - AgileSparks
End to End Flow – The States
Scrum Iteration – 3w
(Design, dev, integrate,
free run)
• C...
All Rights Reserved - AgileSparks
Some tips
• Do not mix between Backlog management and
requirements management (trace)
• ...
All Rights Reserved - AgileSparks
My 2c - ScrumBan Implementation Tips
• Quality backlog
• Full, “ice berg” approach (elab...
All Rights Reserved - AgileSparks
ScrumBan Implementation Tips
• Emphasis retrospective importance and policies
adherence
...
All Rights Reserved - AgileSparks
ScrumBan Implementation Tips
• Agile testing
• Test plan as part of DOD (light ATDD)
• F...
All Rights Reserved - AgileSparks
Upcoming SlideShare
Loading in …5
×

Implementing Agile in environments that require strinct certification - Agile Israel 2014

1,025 views
836 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,025
On SlideShare
0
From Embeds
0
Number of Embeds
546
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Implementing Agile in environments that require strinct certification - Agile Israel 2014

  1. 1. All Rights Reserved - AgileSparks Implementing Agile in an environment that requires strict certification Dr. Ronen Bar-Nahor
  2. 2. All Rights Reserved - AgileSparks Agenda • DO178 • Main challenges • Flow example for implementing Agile & DO178 • My 2c - ScrumBan Implementation Tips
  3. 3. All Rights Reserved - AgileSparks 3 What is DO-178? • Addresses the life process of developing embedded software in aircraft systems. • Must pass certification held by regulatory organizations such as the FAA (Federal Aviation Administration)
  4. 4. All Rights Reserved - AgileSparks 3 Traceability Matrix Configuration Item )CSCI) SW Req. HLRs CSCI Req . Spec Req. Review HLRs Allocation Design Arch Design Document Arch Desig Review Source Code LLR Review Coding Design LLR Phase Design Architecture- Phase Code Review Design LLR QA LLR & Traceability to HLRs Software Requirements Phase Safety (Derived Reqs) Configuration Management PCR Management Test Management QC RM CM Reqs Management Phase Integration & Testing Accomplishment Phase Testing TEST Review HL TESTS Trace to HLR LL TESTS Trace to LLR SUMMARY DOCUMENTSAccomplishment 2 3 4 TEST Execution & Analysis Planning Phase PLANS /STANDARDS Planning 1 System Requirements System Req . Spec. System Req . Valid Review Requirements allocation to HW, SW Customer Req . System Requirements Phase Traceability Matrix Coding Phase DO-178 SDLC Traceability to LLRs Integration Trace to LLR
  5. 5. All Rights Reserved - AgileSparks DO 178 CSCI
  6. 6. All Rights Reserved - AgileSparks Main Challenges Certification Project • Full Traceability • Verification /Validation • Need for evidence • Documentation up front • Independency • CSCI approach • Applying Agile process to a legacy environment • SQA Agile • People & communication • Agile testing , team own quality • Working SW over Comprehensive documentation up front • Endorse changes, postpone decisions to the last responsible moment • Functional/user centric backlog • Continuous Improvement (process)
  7. 7. All Rights Reserved - AgileSparks DO 178B ‫של‬ ‫אינטגרציה‬ ‫עבר‬ ‫שכבר‬ ‫מוצר‬ ‫רישיון‬ ‫ב‬ ‫פשוט‬ ‫פיתוח‬- ‫סגור‬partition ‫בגישת‬ ‫פיתוח‬ prototyping Waterfall
  8. 8. All Rights Reserved - AgileSparks Key Lean/Agile Frameworks Kanban Focus on optimizing the end to end flow of value and ensure JIT certification Release management Scrum Focus on team level and early feedback Development management How many know Kanban ?
  9. 9. All Rights Reserved - AgileSparks Kanban Practices in a Nutshell + Make process policies explicit + Improve collaboratively, evolve experimentally http://www.kanban101.com/ 9
  10. 10. All Rights Reserved - AgileSparks Optimize the whole value stream End to End Flow – The States Planning Phase • Plans & Standards • HL System Requirement • System decomposition • HL SW Architecture • Operational guidelines • HL integration plan • Project Backlog • PDR Selected (Top 5 epics) • CSCI Consideration Discovery Elaborating •System requirements in Doors (+trace) •Elaborate epics in TFS + HL Test (DOD, ref. to Req.) • SW HL requirements, allocated to CSCI (Doors ) - Draft Team Elaborating • SRR + Finalize HLR (SW internal baseline) • User stories (INVEST) + main tasks (TFS) • Ensure architecture alignment Ready Story (1-1.5 Iterations) • Condition to pull : • Ability to complete epic • Defects threshold SOI 1 Requirement Analysis & backlog grooming
  11. 11. All Rights Reserved - AgileSparks End to End Flow – The States Scrum Iteration – 3w (Design, dev, integrate, free run) • Coding • [ Design - LLR (draft) ] • Test Design in QC (ATP & STD) • Free Run at lab • Update HLR • [ Traceability (sys- HLR-LLR-TCs) ] Done • Condition to pull: • Enough epics/CSCI Partial ATP & Wrap up • RDCI + checklists • Delta handling (certified area) • Align documents • Partial ATP [ & informal code coverage ] • Baseline Formal ATP & Final wrap up SOI2- ~60% SOI 3Scrum Development Acceptance & JIT Certification
  12. 12. All Rights Reserved - AgileSparks Some tips • Do not mix between Backlog management and requirements management (trace) • Early feedback - balance between functional approach and CSCI certification needs • People & communication before formal documentation! • Baseline as part of “Done” definition in Epic level • DO activities are part of the backlog
  13. 13. All Rights Reserved - AgileSparks My 2c - ScrumBan Implementation Tips • Quality backlog • Full, “ice berg” approach (elaborate JIT), • Prioritized + story points estimation • Importance of “ready stories” • Pre-planning in pairs, with the PO • Minimal investment in estimations • Team Lead estimation is enough (story points) • Do not check if team estimate “correctly” (no actuals!) • The goal is not to meet Iteration “commitments” ! But: • Velocity improvement • PO satisfaction • PO is part of the team - acceptance ASAP
  14. 14. All Rights Reserved - AgileSparks ScrumBan Implementation Tips • Emphasis retrospective importance and policies adherence • Importance of tool - Visibility and predictability – calm down the “wolves” • Start with flow management (Kanban) than team agility (scrum) • Engage managers across the value stream • Focus on “stop starting start finishing” • Early testing
  15. 15. All Rights Reserved - AgileSparks ScrumBan Implementation Tips • Agile testing • Test plan as part of DOD (light ATDD) • Free run/exploratory as part of the iteration (by PO) • Defects policy  zero defects !!! • Priorities • Low – we will never fix • Medium – need to be fixed but not for next milestone • High – need to be fixed for next milestone • Urgent – showstopper • Defects threshold • Should impact velocity
  16. 16. All Rights Reserved - AgileSparks

×