Agile And Lean Frameworks Flashcards
Disciplined agile
A process decision framework that integrates several agile best practices into a comprehensive model:
People first - roles and organization at all levels
Learning oriented - collaborative improvement
Full delivery of lifecycle - fit for purpose
Goal driven - tailoring for specific outcomes
Enterprise awareness- cross departmental governance
Scalable - complexity
Enterprise scrum
Scrum for a holistic organizational level
All aspects of the org
Generalize scrum techniques
Scale the scrum method with supplements
Enable disruptive innovation
Large Scale Scrum (LeSS)
Extends the scrum method while retaining as much as possible
Cross team elements
Scaled Agile Framework (safe)
Economic view
Systems thinking
Assume variability preserve options
Build incrementally with fast integrated learning cycles
Based milestones on objective evaluation of working systems
Scrum of Scrums
Meta scrum
Coordinated scrum teams with reps meeting daily-2 or 3 times per week
Agile unified process
AgileUP
More accelerated lifecycles and less heavyweight processes
More iterative cycles across 7 key disciplines to incorporate feedback before formal delivery
Principles: team knows what it’s doing, simplicity, agility, focus on high value activities, tool independence, tailoring, situationally specific
Disciplines: model, implementation, test, deployment, configuration management, project management, environment
Dynamic systems development method
Designed to add more rigor to existing iterative methods in the 1990s
Constraint driven delivery!
Sets cost, quality, and time at the outset and uses formal prioritization of scope to meet constraints
Principles: focus on business need, deliver on time, collaborate, never compromise quality, build incrementally on firm foundations, develop iteratively, communicate continuously and clearly, demonstrate control
Feature driven development
Everything is around features and core software engineering best practices
Srumban
Transition from scrum to Kanban
Scrum as framework and kanban for process improvement
Crystal methods
Based on size of project (clear, yellow, orange, red)
Core values: people, interaction, community, skills, talents, communication
Properties: frequent delivery, reflective improvement, close or osmotic communication, personal safety, focus, easy to access experts, technical environment with automated test, configuration management, frequent integration
Kanban
Lean manufacturing method for scheduling inventory control and replenishment. Just in time delivery.
Visualize workflow
Continuous flow of work and value to customer
Less prescriptive and disruptive
No time boxes
Limits work in progress
Extreme programming (XP)
Frequent cycles
Improve the results of software projects
Shared ownership, lots of delivery, lots of collaboration
Greater responsiveness to changing requirements
Scrum
Single team
1 month or less
Consistent sprints delivering a prove to ally releasable increment of a product
