SDLC

STLC
methodologies
scrum master role
agile
scrum- 35335
3 pillars
5 values
3 artifacts
3 roles
5 events / ceremonies

agile metrics 15 metrics

other topics:
Kanban
SAFe
Project management

stakeholder
project owner / product
project manager ( traditional manager )
agile project manager
release train engineer
agile coach
scrum
delivery manager ( internal stake holder )
sme
business architech
business analyst
developers
testers
support
devops-- deliverable
marketing
HR
================================================
SCRUM MASTER
co-ordinator
facilitates the meetings
bridge between the team and the PO

the scrum team leader, also reffered to as the scrum master is a person who
takes
care of to and for communication between the product owner and the entire
team

Roles
trainer
product owner
free lancer
organization development

Qualities :
status
communication
reporting
planning
meeting
 communciation
protecting the team
tool maintanence ( jira, Azure devops )
reporting
meeting facilitation
agile coaching
team support
remove impedements

i will be
======================================================

Methodologies involved in project development :

ex.agile

=======================================================
SDLC:
software development life cycle
>requirement gathering
>requirement analysis
>SIGN OFF DOCS
>DESIGN ( ui/ux desing )
>Development
>Testing
>Production
>Deliverables
>Maintanence

-----------------------------------------------
STLC:

>requirement analysis
>test plan document
>test enviroinment setup
>test case creation
>test execution
>test cycle closure

--------------------------------------------------------------------

DEV:
frontend :
html, css, php , react, angular

backend :
java, python , c#

database
oracle, mongo DB

Test
manual testing - no codes
automation testing - selenium
api - manual - postman
automation - rest assured
GIT - storing datas
JENKINS - server - CICD pipeline

=========================================
Project Development Methodologies:

Waterfall
V-Model
Spiral
BigBang
Agile

Waterfall
defined process
which is known as linear sequential lifecycle model

project development team only moves to the next level / phase of development
or testing if the previous step completed succesfully

**business team only involved in the planning and end release of the product

Drawbacks:
back tracking is not possible
clients are not into the process
testing at the last stage
no changes can be accomodated at during executions
requirements will be freezed
more of documentation works
----

Agile :
Emprical process
iterative approach
specific approach for planning, managing and executing of work
light weight approach
**business team works along with the development team to get the
project/product success

Drawbacks:
less documents
lot of changes
demands
==========================================

Requirement
part ( login ,, home, , logout )
part2 ( home 2.,, payment )
part3 ( offers, subscription )

=======================================================================
THE STACEY MATRIX
Uncertainity of Requirements:
level of uncertainity of WHAT you have to do or build

Uncertainity of Technology:
level of uncertainity of HOW you build a project

Close to the certainity and aggrement-- SIMPLE -- WATERFALL

far from certainity and aggrement -- COMPLEX -- AGILE

----------------------------------------------------------
AGILE
Agile is a Methodology
Product Owner > Requirements > AGILE > Product Succes

Agile is a general term for various approaches to developing software that

have emerged in response to the dismal results of the waterfall approach

Agile Manifesto : ( 4 )
*individual and interaction over processes and tools
*Working software over comprehensive documentation
*Customer collabration over contract negotation
*Responding to change over following a plan

*individual and interaction over processes and tools

connecting with the people
PO working with the team
Face to face meetings
*Working software over comprehensive documentation
working software is the primary key
less docs
*Customer collabration over contract negotation
connect with the customer ( PO, STAKE )
customer should be invloved in all the process
*Responding to change over following a plan
responding to the customer change request
accept the changes and do the needful
===================================================================

12 principles:
Customer satisfaction
welcome changes
delivery frequently
work together
trust and support
face to face conversation
working software
sustainable development
continous attentation
maintain simplicity
self organizing team
reflect and adjust

Does agile project fails ??

==================================================================
Being agile vs Doing Agile
Doing Agile :
means practicing all the processes and guidelies of agile methodology
without understanding or analysing the rationale and the sprit of these
guidelines
or processes
practices
20% benefits
ability to manage changing priorities
improved visibility

Being Agile:
an individual or an organization is AGILE when theyre able to quickly adopt
or evolve
in response to changing requirements/ circumstances
200% + success + profit
mindset
customer satisfaction, engagement
innovation, continous learning

==========================================

AGILE GOAL:
the goal of agile development:
to create highest business value in the shortest span of time in a
sustainable way

AGILE METHODOLOGY:

light weight approach fuller weight approach

Framework framework
Scrum Scrum - of - scrums
Scrum - at - scale
kanban Scaled agile framework ( SAFe)
lean Agile Project management
Extreme Programming Agile unified process
Continous Delivery open unified process
Continous Integration

==============================================================================
SCRUM
35335
3 - pillars
5 - values
3 - roles
3 - artifacts
5 - ceremonies

Scrum
Is a framework, and it is one of the lighter weight approach in the agile
methodology
Currently , the most popular agile approach in te world is SCRUM

Scrum is a generic framework for solving complex problem such as product

development, project creation & project execution
 Is a framework for project management commonly used in other field,
Research, Sales, Marketing and Advanced Technologies

Scrum Pillars:
TIA
Transperancy
Inspection
Adaptation

Transperancy:
Everyone should know whats going in the process
Giving visibility in the process
"meetings " promotes , helps with transperancy ( DSM,Review meeting etc )

Inspection:
check the process towards the sprint goal
a process to evaluate the work done by the developer and tester

Adaptation:
adjusting a process as soon as possible to minimize any further devation or
issues Adapt to the feedbacks given by the customer
adapt to the results by inspecting the process

5 - values
FORCC
Focus
focus on the work, team, goal
focus on the requirement , process
focus on the customer feedback
Openness
being transperant
open to the new challenges
Respect
Team memeber should respect each other in the team
indepedent people
Commitment
commit to the work, complete the work
Courage
courage to face the situation
do the right thing and work on the tough situation
Courage to agree / disgaree

Scrum Attributes:
Self managing team
ask the team
value - driven
time boxing
inspect & adapt
transperancy

Scrum Roles:
Roles in scrum
Product Owner
Scrum Master
Scrum team /Development team
Product Owner :
Brain of the product
managing the product
vision on the product
the person who represents on behalf of the customers
the person who creates backlogs ( requirements )
business domain skills
decides the process ( methodology )
defines the relase date of the project
prioritizes the work

Characteristics:
One Person
authority over the product decision
accountable for the product success

Responsibilities:
proper requirement sharing
on - going vision
optimize the developer work
ensure team has proper data
co-ordinate with scrum master

===================================================================
Scrum Master
Backbone of the product
Removes obstacles/ roadblockes
resolves the problems in the team
motivates the team
problem solving
protect the team / support the team
co-ordiante between the team
encourge team in decision making
timely deliver the project
Owns the process
you are not the boss

Characteristics:
"leader who severs"
no authority
role model - scrum pillars, values
not a manager
not an admin
system thinker

Responsibilites
Helps people understand scrum,
make them understand their roles and responsibilities
increase the visibility in the project
facilitate the meeting as needed
improve the system ( organization )

Scrum Team :
development team
developers and testers
transperancy
 self-organizing
cross functional team
participating in all the ceremonies

characteristics:
self- managing team
cross fucntional team
no sub team
full time, dedicated

Responsibilities:
decide how to do the work
track the progress in the sprint
estimate the work
collaborate with PO , Stakeholder to maintain backlogs

-
===================================================================================
===============
BACKLOGS
Product Backlog
Sprint Backlog
Product Increment

================================================
Product Backlogs
Login
logout
logo
homepage
payment
upi
credit
debit
=25 deliverables
duration = 1.5 year

Sprint-
a small time boxed event, which helps to complete the process
1 week ( mon- fri 5 days )
2 weeks (10)
3 weeks (15)
4 weeks (20)
custom
74
37
24
18

===================================================================================
=======
Sprint Planning Meeting

Planning Meeting - Planning for the upcoming sprint

when the team meets to determine which backlog items will be handlled in the next
sprint / upcoming sprint
the sprint planning scrum ceremony is a collaborative process that allows team
memebs to have a say in when work happens

for planning meeting

* capacity planning ( SM )
* Product backlog to sprint backlogs
* Acceptance criteria
* INVEST criteria
* DOR & DOD
* JIRA dashboard should be ready

Product Backlog
A product backlog is a particular / prioritized list of work for the
development team that is derived from the requirements , the most important items
that to be delivered in the project
* Features we want to implement but have not yet prioritized for release

Sprint Backlog :
user stories that need to be completed during a specific period of time

Requirements are in the form of

THEME
FEATURE
EPIC
USER STORY
TASK
THEME/ FEATURE :
BIRTHDAY PARTY PLAN

EPIC :

hall
open ground
guest
food
transport

USer story:
epic 1: hall
a/c, non a/c, seating

epic 2 : open ground

decoration, ventilation, lights

epic 3 : food
veg , non veg , snacks

epic 4 : transport
bike parking, car parking, van parking

TASK:
 us1 : a/c
centralized a/c, split a/c , fan

=========================================================

Prioritize & estimations

prioritize are done by the PO
estimations are done by the Scrum Team / Dev team

techniques in prioritize
MoSCoW
HML

techniques in Estimations
Planning pocker
relative estimations
Absolute planning

==========================================
MoSCoW
Must - the most vital things you cant live without
Should - things you consider as important, but not vital
Could - things that are nice to have
Wont - things that provide little to no value you can give up on

HML
High
Medium
Low
Critical

Estimation technique:
planning pocker ( fibinocci series ) - user story / task / epic
0 .5 .5 1 1 2 3 5 8

e -1 - 5- 8 hours
m - 3 - 8- 12 hours
h -5 - 12-20 hours
c - 8 - 30 hours

merina to bessy -3,3,8

using bike - 3 3 5
bike, no traffic - 1 1 3

t -shirt size ( epic )

xs - 3 sprints
s - 3-5 sprints
m - 5- 8 sprints
l - 8-12 sprints
xl-12 + sprints

5 user stories
e-commerce - joshua
telecom - jeevin
banking - preethi
============================================================================
Epic - this is done by the PO
User stories - BA, PO, or Dev team
================================================

Acceptance criteria
these are the specific conditions or requirements that a product o feature
must meet to be considered complete and satisfactory , that helps to define the
scope and expectations of a deliverables
acceptacne criteria are n number

INVEST criteria
Independent -
ensure the user story we choose that should be independent
standalone PBI with no dependenceies
Negotiable
it can be changed in any time, they may be new request or request on
removing PBI's
Valuable
value , whenever a product is delivered a value should be created for
the end user,also for the team
Estimable
estimatable - the team is able to estimate the story points, estimate
the time
to deliver the product
Small
small enough to be completed within a sprint
small enough to be developed and tested
testable
testing should be done

DOR & DOD

Definition of READY
Definition of DONE
==========================================
Product backlog refinement activity
*grooming meeting
Product backlog
sprint backlog
estimation technique
prioritize technique
User story, Epic
dor vs dod

Capacity planning:

this is a process that helps organizations ddetermine how much production

capcity needd to meet customer demands

the goal is to have the right resurces available when you'll need them
=================================================================
Sprint Planning Meeting
Sprint Daily Stand up Meeting
Sprint Review Meeting
Sprint Retrospective Meeting

Sprint Planning Meeting

refine the product backlog
check the team availabilty ( capacity planner )
meeting agenda ( to complete the sprint goal )
time line ( 2 hours max )

sprit planning keys:

collaborate
focus on the sprint goal
involve the customer
encouraging the evolution
DOR & DOD should be ready

Sprint Daily Standup call:

sprint morning meeting
sprint daily standup
dsm
daily scrum meeting

the purpose of the DSM is to inspect the progress being made towards the sprint
goal and to adopt the work where necessary

1.What have you completed last day?

2.what is the priority work for today ?
3.what is getting in your way ? ( problems )

Identify the impedements and achieve the goal

daily standup helps to show the cross-functional skills
re-plan and adjust the work

stand-up call is not for problem solving

participants:
PO, Scrum Master, Devteam

15 min timeboxed

--------------------------------------------------------
Sprint Review Meeting
Team checkin process
backlogs are moved to done status
discuss on the sprint goal
review the status
demo to the team
value delivered
velocity chart
risk identified
reports ( jira reports )
 Feedback from the team

Each sprint end will give demo to the clients

*inspect and adopt the process
*only show the working software
*no ppt / no docs
*get the feedback from the team on the current status of the product

2 weeks/ 45-1 hour max

3 weeks/ 2 hours max
========================================================

Sprint Retrospective Meeting

As a SM, we have to figure out what went wrong and what went right inn the
completed sprint

inspect and adopt the process

how we are working as a team?
1-2 improvement actions
scrum values should be applied
last event of the sprint

template:
What went right?
what went wrong?
what could have been done better ?

start doing?
stop doing?
continue doing?

=========================
Metrics:
Agile + Scrum Metrics

lead time
cycle time
burn up chart
burn down chart
velocity
capacity
cumulative work flow
code analysis
static code analysis
defect density
escaped defects
RAG- Red Amber Green
RTM- Requirement tracebility matrix
Release burn down
value delivered
happiness index

Lead Time :
the lead time measures the time from the moment the customer makes a request
to the time they receive the product
this is calculated in KANBAN
Cycle Time :
the cycle time measures the time it takes the development team to work on the
request and deliver it
cycle time calculated in SCRUM

Burn Up:
how much work has been completed and total scope of the project
shows the project scope changes
burn up for the PO

Burn Down:
this shows how much work is remaining to be done in the project
burn down for the team

Cumulative :
allows us to measure the progress and efficiency of the project
Is a visual summary of the information contained on the scrum wall, task
board

Velocity:
How much work has been completed/ delivered in each sprint
the velocity chart displays the average amount of work a scrum team completes
during the sprint

velocity changes :

Cumulative flow diagram:

allows us to measure the progress and efficiency of a project
is a visual summary of the information contained on the scrum wall , task
board

Code analysis/ code coverage

sonar qube
to check the code stability

80% and above - codes are stable code

80% and less - codes are not stable

-----------------------------------------
Static code analysis:
the visibility of a peojects code without running the software
Design > code >ANALYSIS > Build > Unit Test > checkin

---------------------------------------------
Defect Density:

the number of defects per thousand lines of code

it is a measure of the quality of the code -- the better the software
quality, the lower the density

Escaped defects:
escaped defect is a software bug or error that is discovered after the
software has been released , but before the end-user or customer
incompleted testing
inadequate test coverage
complexity
human error

----------------------------------------------------
RTM:
requirement tracebility matrix
rtm used to help the testing team understand the testing level for a product,
and ensure that all requirements are covered by test cases
rtm helps to identify missing requirements and datas

RAG
RED AMBER GREEN

=======================================================================
Other topics :
Agile Vs scrum
Agile gives flexibility to the project, collabration , customer feedback and
delivering incremental value
encouraging cross functional team to work closly together

key principles :
individual and interaction
working software
customer collabration
responding to change

agile is a methodology includes scrum framework

Scrum:
specified framework that provides a structured approach for organizing and
managing work
it defines roles, events and artifacts
Key elements :
roles
events/ ceremonies
artifacts
flexibility

--------------------------------------
Scope change vs scope creep

scope , defines what a product can and cannot do

outline

Scope change
an official decision made by the project management, product owner and the
stake
a change in the feature to expand or reduce its functionalities
involves adjusting the cost, budget , other feature or the timeline

Scope creep
when the project scope grows beyond what was originally defined in the
statement of work
small changes that generally impact your bottom line of the project
causes , scope creep:
changes in the requirements
not properly defined requiremtns
poor communication
dependencies

manage creep
transparency
document the project requirement
clear project schedule, agenda
verify the scope with stakeholders
adaptive planning, iterative delivery and continous feedbacks

=======================================================================

Technical Debt
Technical Debt is the extra effort that will later arise when the code that
is expected
in the short term is used instead of applying a solution optimized for clarity,
evalvability and maintanence

causes:
business pressure to release early
lack of alignment to standards
lack of automation testing
poor knowledge of how to craft high quality code
band-aid approaches
poor or low technical leadership

unit test report

code analysis

=================================
Spike
uncertainity of user stories
A spike is created when a user story or task cannot be estimated well enough
untill the team has done future research or investigation
a spike is a short, time-boxed activity that helps teams gain knowledge or
reduce uncertainity about the specific aspect of a user story or epic

=================================================================
Types :
sprint 0
sprint n-1
insprint automation

Sprint 0
kick off meeting
planning
resource allocation
user stories
epic works
Sprint n-1

A common approach in which testing activities start at leaset one sprint

behind the development process, and new functionalies are tested when they become
relatively stable

InSprint Automation

is a process that uses automation for the entore testing of an application ,

including test case creation, execution, planning and reporting
we do move the process to the devops

======================================================
Kanban
Scrum-of-Scrums
SAFE

Scrum-of-scrums ( SOS )
scrum event is to ensure effective co-ordination and synchronization among
multiple teams , ( scrum ) , working on a common project

Kanban

continous deliverables
=========================================
SAFe
Scaled Agile Framework
8-12 weeks
5 sprint

1 - 100%
2 - 80%
3 - 80%
4 - 50%
5 - UAT, REGRESSION, PRODUCTION

a set of workflow patterns for implementing agile practices at an enterprise level,

scale
expertise in team, deals with the big projects

scrum coach - is the one who handles the process

RTE- release train engineer, Program manager, solution architech, epic owners
this requires a high level of co-ordination and alignment across team and
management level which increases work dependency

Plan - Do - Check - Adjust

https://brightriver.recruitee.com/v/events/ew3pk25aot29

Public note Bright River video interview with members of our development team

Powered by Recruitee

One att
========================================================