Agile Principles (12) + Manifesto (4)

Day 2
SAFe Principles (10) ** --> Reqs + Resources + Automation =>Reqs +Time +Quality
+Satisfy
1. Take an economic view -> high/ detailed requirement , customer centric,
situation
2. Apply System Thinking -> Application execution, check the complexity
3. Assume variability and preserve options - storage of data, usage, inputs
4. Build incrementally with fast and integrate with other
5. Base milestone an objective - inline or in scope
6. Apply Cadence, sync with domains - a limit and flow of work in sequence
7. Visualize and create a WIP limit charts ( Work In Progress ) eg., SCRUM Board
8. Unlock the intrinsic motivation of knowledge workers ***
9. Decentralize decision making - develop fast and deliver *** DevOps ( CI/ CD )
10. Organize around the values - deliver the solution more quicker *** DevOps
( CI/CD )

SAFe Big picture or Full Config - Agile + SAFe Lean + SCRUM + Kanban + XP

SCRUM - Transparency , Inspect, Adapt, Sprint

> PO ( Backlogs), SM ( monitors ST), ST ( DBT)
> 7 - 9 (ST) + 2 ( PO , SM )
> 2 to 4 weeks

Kanban - Support / Maintainenance project - LIVE GO Apps

> small change request
> New request
> Improvement of code
> Visualize workflow, LIP ( Limit In Progress)
-> TODO | InProgress | DONE
T4 T1 - Anusha
T2 - Rajesh
T3 - Anusha

Extreme Programming - Support / Maintainenance project - LIVE GO Apps

> Quality Practices - Pair Programming, Test Driven Development (TDD),
Behavioral Driven Development (BDD), Refactoring
***********************************************************************************
***********
BUILD A TEAM *** Roles & Responsibilities

Agile Team - PO, SM, ST

SAFe Team - PO, SM, ST + 5 ppl
> Business Owner - Client or Stakeholder
> Product Manager - Owns, Prior, define the Program Backlog gives to PO
> System Team - process & tools - assets for development
> System Engg - guide in architecture & technical
> RTE - Release Train Engg - acts as a chief SM - monitor the SM
All these roles are part of ART ( Agile Release Train )
> plan, demo, integration, deploy, release
> focus on local concerns - impediments
***********************************************************************************
***********
PREPARE BACKLOG - TEAM *** List of Requirements - Plan & Analyse the reqs

Creating Backlog - List of Requirements - Team Backlog

1. Epic - Solution eg., Online Shopping App ( 600++ requirements)

> Lean Budget - Portfoli Backlog ( strategy for execution )
 > Identity Enablers for this Epic (add on / support activities) **
> Identity Features ( attributes of Epic) **
2. Group the Features ( Categories the features )
> Create User Story -> assign to the team - Team Backlog ( US + Enablers )
3. User Story - Design, Build, Test - benefit hypothesis ( measure end user )
> Story + Accp. Criteria ( user + validate ur correct implementation )
eg., As a Online Shopping App registered user
I will provide Uname & Pwd
So that i can login and shop
USER STORY
> INVEST properties - Independent, Nego, Value, Estimate, Small, Test
> 3 C's - Card - sticky note, Conversation - detailed, Confirmation- with
Accp.Criteria
> Enablers - Support - Infr, Arch, Exploration - add on explaination, Compliance -
policy
eg., Payment (us) + 3rd party banking ( enabler ) + Compliances (enabler)
> Split the US into small / unit - 4 techniques
- Condition, business rule
- Multiple steps
- Complexity
- Exception
> Accp.Criteria - Testing point ( Validate and Verify the US)
> BDD - GIVEN - WHEN - THEN - Automate - CUCUMBER plugin

Who will create the US ? - > Agile Team (PO, SM, explicitly ST to develop US )
Who owns the US ? -> SCRUM - PO, SAFe - Product Manager ( Prior,Categ,Seq,Group)
> PM distribute the US to PO based on the Release
> SCRUM - PO will interact with SH
> SAFE - PM will interact with BO
***********************************************************************************
***************
ITERATION PLANNING
>Iteration - a work that repeatedly for different reqs( duration, effort ,
complexity, uncertainity )
* Purpose - COMMIT ur US that u r going to develop
* Process - What & HOW ?
* Result - outcome
* Commit - based on prior , expectation

Iteration Planning - 4 hrs or less - 2 weeks ITERATION - Analyse & Estimate US

- by the team & for the team
- include SME's based on needs
- Estimating the US - effort take to develop ( duration, resources,
capacity, complexity etc)
- Team Velocity - size, duration, effort
- Techniques - Planning Poker Estimation
> Fibonacci Series - 0,1,1,2,3,5,8,13...... - Story Points
- Integers
- Difference between the points considered 9 buffer time to
work on the below aspects
- Volume: How much is there?
- Complexity: How hard is it?
- Knowledge: What do we know?
- Uncertainty: What’s not known?
Reason why Fibonacci series in much suitable approach for story pointing as
compared to the regular numeric scale :
1. The numbers in Fibonacci series are not evenly distributed, as we go down the
Fibonacci series the numbers get bigger.
2. The jumps between the sizes gets much bigger as the stories gets bigger.
3. Similarly, the stories in a product backlog are smaller and more refined at the
top and as we go down in the product backlog the stories get bigger and bigger.
4. In a way, a story with size 2 is slightly bigger than story of size 1 but a
story of size 13 is much bigger than a story of size 8.
This way Fibonacci series kind of brings that scientific approach and logic to the
planning poker and pointing system.

***********************************************************************************
****************
ITERATION GOAL - COMMITMENT given by the developers
> Tasking Stories - US with less sp we will start - COMMIT
> Enables - Support activities
> Change request - Kanban apporach or XP approach
> Split the US
***********************************************************************************
****************