Chapter 17: Common Agile Methodologies

Question 1

Agile Methodologies

Answer 1

Lean Product Development (зонтик над agile & kanban)
Знать 7 принципов:
1. Eliminate waste - хорошо выявляются через Value Chain и Value Stream Mapping . E.g.: wait time, incomplete work, extra processess, task switching, defects
2. Amplify learning (расширять) - постоянный фитбек и улучшение. E.g. - daily standup, iteration reviews/retrospectives.
3. Decide as late as possible
4. Deliver as fast as possible
5. Empower the team - trust, trainings
6. Build integrity in - строим не просто хороший продукт, но полезный для клиента. E.g. делаем “Personas” чтоб смотреть глазами клиента
7. See the whole - думать системно и видеть картину целиком

……………………….

Kanban
Отдельная карточка
……………………….
Scrum
Отдельная карточка
……………………….
eXtreme Programming (XP)
Отдельная карточка
……………………….
Crystal
Group of methods that the PM and team tailor to find a situation-specific solution.
См. картинку
……………………….
Dynamic Systems Development Method (DSDM)
More prevalent in the UK. 8 принципов (см. картинку)
……………………….
Scaled Agile Framework (SAFe)
Отдельная карточка
……………………….
Feature-Driven Development (FDD)
Focuses on feature delivery, starting from an overall model.
1. Develop an overall model
2. Build a feature list (аналог backlog-a)
3. Plan by feature

Popularized commulative flow diagrams and parking lot diagrams (one-page summaries of project progress)

—————— НЕ БЫЛО У РИТЫ ———-
Lean
Seven Wastes Of Lean (!): (1) Partially done work (2) Extra processes) (3) Extra features (4) Task switching (5) Waiting (info/resources) (6) Motion (много пыли, делай одно дело одновременно) (7) Defects (especially escaped, пропущенные на тесте)

Feature-Driven Development (FDD)
* Characteristics: (1) domain object modeling, (2) developing by feature, (2) individual class code ownership, (3) feature teams, (4) inspections, (5) configuration management, (6) regular builds, and (7) visibility of progress and results.

Agile Unified Process (AUP)

• .

Question 2

Kanban

Answer 2

Не agile, а отдельная методология фактически

Знать для экзамена:

• Kanban (pull system) - Low-tech high-touch information radiator,
• Kanban - отдельная методология, может использоваться для ведения проектов, НЕ требует итераций. Но Kanban Boards используются в различых agile методологиях
• 5 принципов:
  
  1. Visualize the workflow - любой SH должен мочь увидеть статус в любое время
  2. Limit WIP (E.g. iteration backlog)
  3. Manage Flow - следуя первым двум принципам, и фокусируясь на незавершенных задачах до принятия в работу новых, ПМ делает manage flow
  4. Make process policies explicit - команда должна знать весь продукт и процесс хотя бы на HL уровне. Тогда будут понимать свой вклад и практиковать systems thinking
  5. Improve collaboratively - приветствуется и поддерживается, как и continuous improvement

Question 3

Scrum

Answer 3

Знать - Scrum and Generic Agile Terms (like sprint vs iteration) - используются взаимозаменяемо на экзамене.

Виды Backlogs:

• Product - all the known product scope. Features are continuously added and removed as the customer makes decisions about product scope
• Project (не всегда используется, иногда заменяется на “Product Backlog”) - часть Product Backlog, которая будет реализована в конкретном проекте
• Sprint (iteration) - specific increment(-s), selected for the current/next sprint

Core Concepts

• Iterative and incremental development
• Dedicated team - одна и та же команда из проекта в проекта
• Cross-functional team - взаимозаменяемость
• Pillars
  
  • Transparency - creating a common understanding among all parties. E.g. -creating project/product vision, team charter, DoD.
  • Inspection - examination of how the work if going on a regular bases, assessings how the team is progressings, needs for changes to continuously improvement
  • Adaptation - making changes appropriate to the findings from inspection. E.g. of Inspection and Adaptation: Sprint Planning, Daily Scrum, Sprint review/retrospective

Daily Scrum (Daily Standup)

• Вопросы для обсуждения:
  
  1. Что я сделал с последней встречи?
  2. Что буду делать сегодня?
  3. Есть ли impediments?
• Правила:
  
  • have something to report? -> must attend
  • nothing to report? -> shouldn’t speak
  • Talk is restricted to addressing the three questions
  • Impediments taken up after the meeting

Question 4

eXtreme Programming (XP)

Answer 4

• Values:
  
  1. Simplicity - find the simplest thing that could possibly work (no unnecessary design or functional features)
  2. Communications - all members know what other members are working on, understand big picture
  3. Feedback - “fast failure”. E.g. delivering prototypes
  4. Courage - encourages collaboration and transparency. E.g. - pair programming and collective code ownership
  5. Respect
• Practices
  
  1. Whole team - dedicated cross-functional team
  2. Planning games - release planning and iteration planning are called planning games
  3. Small releases - like other agile methodologies
  4. Simple design - helps enable frequent small releases
  5. Metaphor - use methaphors and analogies to make tech concepts understandable to customers
  6. Sustainable pace -overtimes are bad. Цель - sustainable velocity
  7. Customer tests - use customer description like “When I click the Menu, options X,Y,Z should appear”
  8. Test-driven development - the code has to be built to pass the tests
  9. Pair programming - one is coding, another is watching
  10. Collective code ownership - the team as a whole owns the product. Any pair of programmers can change any code
  11. Code standarts - строго следовать стандартам
  12. Continuous integration - постоянно интегрировать новый код в продукт, чтоб точно знать, что он работает
  13. Refactoring - making code more efficient by removing dublicate or unnecessary code, making design simplification
• Roles . Team is collocated
  
  1. Coach (similar to the ScrumMaster)
  2. Customer
  3. Programmer
  4. Tester

Question 5

Scaled Agile Framework (SAFe)

Answer 5

Using the agile mindset in a larger context

• Особенности:
  
  • Agile teams may use Scrum or another approach at the team level. Their work is coordinated under the SAFe Framework
  • Каждая команда несет свой кусок delivery
  • Agile Release Train (ART) - “team of teams” oversees the work of individual teams
  • Release Train Engineer (RTE) - unique role
• Four core values
  
  1. Alignment - all teams are aligned to orga strategy, goals etc. and their work is aligned
  2. Build-in quality - build to the same quality standarts to fit together (пришло из lean principle “build integrity in”)
  3. Transparency - honesty, openness, trust. А также understanding of goals and vision
  4. Program execution - execute in according to the plans and the framework. Must be trained, coached, understand their role
• Level of work - each larger and more strategic that the prior
  
  • Team - an agile team using Scrum or another agile approach
  • Program - group of projects
  • Essential SAFe - the team and program levels are combined into it
  • Large Solution - a large, organization-wide solution
  • Portfolio - programs, projects and operational work supporting strategic business goal

Question 6

Agile Values (Manifesto), Principles, Mindset

Answer 6

Не зубрить, но понимать

Values
(правая часть тоже важна, но левая - наш фокус)
1. Individials And Interactions Over Processes and Tools (focus on people)
2. Working Software Over Comprehensive Documentation (barely sufficient, and just in time)
3. Customer Collaboration Over Contract Negotiation (we must to be flexible, контракты ограничивают это)
4. Responding to Change Over Following a Plan (we welcome change)

12 Principles

1. Customer Satisfaction
   To satisfy customers through early and continuous delivery of products
2. Welcome Changes
   Welcoming changing req, even late in development to maximize the customer’s competitive advantage.
3. Frequent Delivery
   Deliver working software frequently, from a couple of week to a couple of months, with a preference for the shorter timescale
4. Collocated Team
   Business people and devs must work together daily throughout the proj
5. Motivated Individuals
   Build projects around motivated individuals. Give them the empowerment, environment, support, and trust needed to complete a task successfully.
6. Face-to-Face Conversation
   The most efficient and effective way to communicate in order to receive direct feedback and influence osmotic communication.
7. Working Software
   Working sofrware is the primary measure of progress
8. Constant Pace
   Sustainable development. Sponsors, devs, users should be able to maintain a constant pace indefinitely.
9. Continuous Attention
   …to technical excellence and good design enhances agility.
10. Simplicity
    The art of maximizing the amount of work not done - is essential
11. Self-Organization
    The best architectures, reqs and designs emerge from self-organizing teams
12. Regular Reflection
    At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly

Agile Mindset Key Concepts
Mindset = не просто учим Values and Principles, а меняем образ мышления чтобы адаптировать эти принципы and ways of working

• Welcoming change - в отличие от plan-driven восприятия как “necessary evils”, agile - приветствует change
• Working in Small Value-added Increments
• Using Build and Feedback Loops - iteration review получают быстрый фитбек и changes. Нужно для того, чтобы не убежать далеко в сторону
• Learning through Discovery - экспериментировать важно для новых инновационных продуктов
• Fail Fast with Learning
• Value-driven Development - фокусировка на value, причем самом важное (80% фич клиентом не используется)
• Continuous Delivery - постоянно стремимся что-то показать клиенту, максимально быстро
• Continuous Improvement

Question 7

Traditional and Agile Triangle of Constraints

Answer 7