Agile methodologies

-> how we work together on technologies

(manager, project managers, software engineers, everyone that involves in project)

Agile and why it works

Agile requirements and estimation
Scrum
agile planning
lean software development
agile patterns and anti-patterns

comparing development processes

-> Winston Royce's waterfall model
Unfortunately, for the process illustrated the design iterations are never confined
to the successive steps.
Manifesto for agile software development

The big difference->

between plan driven software development and agile software development
plan driven software development-->> planning-> analysis-> develop-> test->
integrate-> validate-> deploy
agile software development-->>analysis->develop-> test-> integrate-> validate. ->
again same process multiple times-> deploy

graphing agile vs plan driven

-> Visibility
-> ability to change
-> business value (money)
-> risk

what agile is and is not

dispelling common myths
touchstones of ability -> comeback to these things to recall what we are trying to
accomplish -> documents and principles
two parts of the agile discussion -> processes and methodologies and techniques and
practices
Agile is -> iterative -> adaptive -> value based -> easy to understand -> hard to
implement
agile is not -> just about writing code -> undisciplined -> unstructured ->
whatever you want it to be -> a placebo for pesky developers

contemporary agile methodologies

XP - extreme programming
-> good practice
-> pushed to the extreme

XP's 12 practices
1. the planning game
2. small references
3. metaphor
4. simple design
5. testing
6. refactoring
7. pair programming
8. continuous integration
9. colle4ctive ownership
10. on site customer
11. 40 hour week
12 coding standards
Scrum:- an iterative project management process
sprint -> means scrum

lean software development

eliminate waste
amplify learning
respect people
deliver fast
recognize and optimized the whole

Feature driven development

FDD practices
-> domain object modeling
-> developing by feature
-> individual code ownership
-> feature teams

creative effective requirements

INVEST->
Independent
Negotiable
Valuable
Estimable
Sized appropriately
Testable

User stories
-> As a <role> I want to <feature> so that <benefit>
the user stories works do well

Estimation work
estimates are necessary
-> to plan and proceeds deliberately
-> to get a feel for costs
-> to calculate potential ROI
-> to understanding size of something
-> to know if work even can be done
-> to weigh options

ways to estimate software

-> darts
-> give it to manager
-> ask the expert

above mentioned are difficult ways to estimate software

how do we measure software work?

story points-> using numerical units to get clarification

poker planning ->

Options for handling conflicts->

wait for convergence
average the estimates
toss out high and low
send the item back for re-definition

Scrum :-

1.origins of scrum:-
The new new product game
type A - sequential
type B - overlapping
type C - overlapping
are phases of development

-> Lean manufacturing

-> learning organization

2.principles
scrum promotes these principles
->small working teams
-> embracing changing requirenments
-> deliver finished work frequently
-> small batches
-> enable releasing product whenever required

characteristics of scrum:-
-->activities are boxed
-->all project metrics, reports and deadline are prominently displayed
-->multi disciplinary and self organizing teams
--> no specific engineering practices prescribed
--> product progresses in series of sprints
--> requirements are captured as items in a product backlog
--> continuously test product as it is created

3.the scrum model (Framework)

what is it?
-> a project management technique
-> one of the agile practices
-> an effective way to deliver products

scrum in nutshell
-> demo with customer
-> initial product to show on demo
-> get feedback form for the demo

scrum :-
(product backlog
|
sprint backlog ---> 2-4 week sprint (24 hour iteration) ) -> fully functional
product

Roles:-

Scrum is a framework where a Scrum Team works together to achieve a Product Goal.
The team is small (usually ≤10 people), cross-functional, and self-managing.

Key Roles in Scrum

->Scrum Team
Composed of a Scrum Master, Product Owner, and Developers
No sub-teams or hierarchies
Responsible for all product-related activities
Works in Sprints for better focus and consistency.
->Developers

Create a usable product Increment every Sprint

Responsible for:
Planning work (Sprint Backlog)
Ensuring quality (Definition of Done)
Adapting plans toward the Sprint Goal
Holding each other accountable
->Product Owner

Maximizes product value

Manages the Product Backlog by:
Defining and communicating the Product Goal
Prioritizing backlog items
Ensuring backlog visibility and clarity
Solely accountable for backlog decisions
->Scrum Master

Ensures Scrum principles are followed

Improves team effectiveness by:
Coaching the team in self-management
Removing obstacles
Facilitating Scrum events
Supports the Product Owner and the organization in Scrum adoption
Each role is crucial in delivering valuable increments efficiently within the Scrum
framework.

artifacts:-
Scrum artifacts represent work and value while ensuring transparency and progress
tracking. Each artifact has a commitment to reinforce Scrum values.

Key Scrum Artifacts

->>Product Backlog (What’s needed)

A prioritized list of features, tasks, and improvements.

Continuously refined for clarity, size, and priority.
Commitment: Product Goal (long-term objective of the product).
->>Sprint Backlog (What’s planned for the Sprint)

Contains the Sprint Goal, selected backlog items, and an action plan.
Continuously updated as the Sprint progresses.
Commitment: Sprint Goal (single objective guiding the Sprint).
->>Increment (The result)

A usable and potentially releasable version of the product.

Multiple increments may be delivered in a Sprint.
Commitment: Definition of Done (quality standards to ensure completeness).

ceremonies:-

Scrum events ensure regularity, transparency, and adaptation of work. Each Sprint
includes all Scrum events and provides a structured way to inspect and improve
progress.

Key Scrum Events

->>Sprint (Main Container)

Fixed length (≤ 1 month) where work happens.

Includes Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective.
No changes should endanger the Sprint Goal.
->>Sprint Planning (Before Sprint Starts)

Defines Sprint Goal and selects Product Backlog items.

Developers plan how to complete the work.
Timeboxed: 8 hours max for a 1-month Sprint.
->>Daily Scrum (Daily Check-in)

15-minute meeting for Developers to track progress.

Focuses on adjusting Sprint Backlog to stay on track.
Improves communication and self-management.
->>Sprint Review (End of Sprint)

Team showcases work to stakeholders.

Discusses what’s next & updates Product Backlog.
Timeboxed: 4 hours max for a 1-month Sprint.
->>Sprint Retrospective (Final Event)

Reflects on what went well & what can improve.

Identifies and implements process improvements.
Timeboxed: 3 hours max for a 1-month Sprint.

activities:-

product backlog planning

->sprint planning-> sprint: daily scrums-> sprint review-> sprint retrospective

The Sprint
-> Non-sequential execution is key
-> Do a little of everything rather than all of one thing

Scaling Scrum:- mostly analyzing of what has been done till.

A scrum of scrum model
this changes the executive service model

Agile Planning
-> techniques for sharpening the saw

Traditional planning->
A good plan is -- clear, reliable, used, available

why we need plans

-> reduce risk
-> make informed decisions
-> reduce uncertainty
-> establish trust
-> convey a tangible vision
-> so customers can depend on you
Unspoken reality
->we can't accurately say what will be delivered
->as users see the software they come up with new ideas
->scope should change as new information is uncovered.

Agile planning
-> plan constantly, not just in the beginning
-> planning is an activity, not a document
-> Don't try to control change, encourage it
-> be constantly transparent
-> focus on historical performance, not hyper-optimal scenarios
-> changing the plan doesn't mean changing timing

product backlog ownership

1 team many products
many , many teams one huge product.

interaction planning
velocity vs. commitment based planning

commitment based interaction planning

2 basic type of planning

date target planning
feature target planning

The daily plan

->sharing commitment
->communicating daily and plans to the team and any observers
->identify impediments
->set direction and focus

perfect items for the team information radiator

-> starting late
-> sociallizing
-> missing pigs
-> gloom anmd doom
-> the meeting overload
-> impendiments aren't raised
-> squawking chickens
-> impendiments aren't resolved
-> the storyteller

SCRUM
Scrum is an agile framework that helps teams work collaboratively to deliver value
incrementally. It involves breaking work into small, manageable pieces and
incorporating continuous feedback loops to learn and improve throughout the
process.

Key Components of Scrum:

Scrum Team: A small, cross-functional group typically comprising a Scrum Master, a

Product Owner, and Developers. This team structure promotes collaboration and
flexibility.

Sprints: Time-boxed iterations, usually lasting two to four weeks, during which the
team works on specific goals. Sprints provide regular opportunities for inspection
and adaptation.

Scrum Events: Structured meetings designed to facilitate transparency and

continuous improvement, including:

Sprint Planning: Defining the objectives and work for the upcoming sprint.
Daily Scrum: A brief daily meeting to assess progress and plan the day's work.
Sprint Review: Demonstrating the completed work to stakeholders and gathering
feedback.
Sprint Retrospective: Reflecting on the sprint to identify areas for improvement.
Scrum Artifacts: Tools that provide transparency and opportunities for inspection,
including:

Product Backlog: An ordered list of everything needed for the product, serving as
the single source of work for the Scrum Team.
Sprint Backlog: A plan for the sprint, detailing the work to be done to achieve the
sprint goal.
Increment: A usable, potentially releasable piece of the product that adds value.