Agile Certification

agile manifesto

1. Individuals and interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a plan

Scaled Agile Framework (SAFe)

A proven, publicly available, framework for applying Lean‐Agile principles and practices at an enterprise scale. bigger programs

release planning.

A release planning meeting is used to create a release plan, which lays out the overall project goals, objectives and backlog of stories. The release plan is then used to create iteration plans for each sprint. The purpose of the Release planning meeting is to have everyone in the team understand and commit to delivering the agreed release. A release generally fixes only the target date or target scope, but not both since the time and effort to complete all the work is defined only at a high level. The project team and the scrum master are present at a release planning meeting as well as the product owner who determines the priority of items on the release backlog list. High level estimated road map Serves as a base to monitor progress in a project To create a release plan you need: 1) A prioritization ans estimation backlog 2) Velocity of the scrum team (estimated) 3) Conditions to satisfaction (goals for the schedule, scope, resources) Can be feature driven or data driven

Extreme Programming (XP)

A team-based agile method that features frequent releases of workable software, short time boxes, programmers who work in pairs, and a focus on testing

DEVOPS

CI/CD which improve deployment velocity

automated continuos integratin

Continuous integration with automation of test execution aids in achieving the sprint goal

WIP Limits

Limiting Work in Progress so that the team maintains focus on completing work, maintaining quality, and delivering value. stops starting and starts finishing history data and capacity planning capacity /average effort

deep dive track

Provide the concepts of engineering practices that are used in agile projects

Sprint Planning Meeting

The Sprint planning meeting is a negotiation between the team and the product owner about what the team will do during the next sprint. Often new backlog items are defined during the meeting. This portion of the sprint planning meeting is time-boxed. Typically the team will then excuse the product owner from the room and break the backlog Items down into tasks. The product owner is expected to be on call during this phase (previously called the sprint definition meeting) for renegotiation or to answer questions that affect the time estimates. This portion of the sprint planning meeting is time-boxed as well.

scrum

The most common framework for Agile Development. backlog , team sprint planning, sprint backlog, sprint starts , daily meetings , review, delivery

Agile Projects

When requirements are evolving shorter releases iterative proceee

tracer bullet

a new feature is introduced to gauche the effectiveness of business/ technical idea

scrumban vs agile

agile- short lead time CI minimize waste just in time approach scrumban- jobs maintenance projects event dricen help desk support new prod development

management approach

all scrum practices

simple design

architecture envision iteration modeling model storming test first desigcode refactoring ( key to keeping the design simple) continuous integration

infy agile

bring predictability deliver enhanced value ensure derisking

INFyagile global

burn down charts dsu mid spying demo risk management sprint review sprint retrospective

in xp

coding and recuse can happen in parallel

Measurement Focus

commitment made to customer

CMMI

contains practices that cover project management , process management, systems engineering, hardware engineering, software engineering risk vs quality/performance

Risk Management

contractual aspect financial Specscope skills competency availability of development teamsavailabily ofnproduct owner

pillars of agile manifero

customer satisfaction welcome to change frequent rollouts constant pace daily cooperations between business and developers

xp roles

customer, programmers , coach (monitors process implementation and issue resolution), tracker ( monitors progress )

features

defined by product manager

TDD

developers writes the automated test cases before actual changes code is written

challenges of distributed agile through indy agile

effective communication in offshore effective daily stand up collaboration among team improving predictability

Build automation

ensures the code is integrated from the beginning interested the tools for code review unit tests and code coverage and ensure quality at source

self organization

equal and collective ownership of the team in planing , designing , development and delivery of software product

planning game phases

exploration - crate user story commitment - commits to date and functionality steering- adjust plan and requirement change

iteration planning

exploration - create task cards commitment -take estimation and allocation steering - perform the tasks

Contract management

finances and risk

deep dive management track

generic management or acted by the team to make them discipline

User Stories

independent negotiable valuable estimable small testable

req. workshop

investment themes , epics, features, user stories

challenges in agile

lack of understanding of the practice unavailability of cross functional teams getting self organized and disciplined collaborative team functioning rather than common and control

Risk Management Plan

managing risks that may impact the projects e deliverables

CMMI

mandates a set of process for system and software development management

large scale scrum

many teams working one one project

spike (analysis and research)

method used when team follows makeshift development which is meant for validating different technical approaches that are considering for developing another complex feature

user stories

minimum requirements

TDD rest driven development

only writing code for failing tests to pass

boundary spanners

people who connect one network to another within the company or even across organizations

4 types of variants in package led projects

premise implementation cloud implementation rollout upgrade

scrum roles

product owner , team , scrum master

Importance of infrastructure

proper planning and management becomes more important in distributed environment for agile projects. VIP to ensure adequate infrastructure like hardware software tools connectivity testing environment per production

Disciplined Agile Delivery

prople furrt

agile primer track

provides a basic understanding of agile concepts , gives generic view of different agile methodologies

quantativr project management

provides platform to establish and maintain the qusnyarivr understanding of project performance manage project quantativrlu to acheivr process and quality performance objectives

quantatice project management

quantatice planning, tracking and process control, thereby achieving the objectives

Refactoring

regular improving of existing design whd code

scrum events

release planning meeting sprint planning daily scrum sprint review sprint retrospective

Scaling agile methodology

safe dad less spotify

key drivers

scalability - to meet client need by addressing the growing demand of work profitability - makes the and cost advantages available to the client achieving cost arbitrage- reduces investments on large teams since vari oh s location can deliver the same service as work happens across talent management - availability of teams with varied skills

Scrumban

scrum x kanban integrate agile and kanban processes

hybrid agile

select practices from agile and other methods (waterfsll, it'erative, spiral) based on a given context

Brand Ambassadors

senior technical experts who ensure the flow of information between teans

Quantitive Project Management

set of techniques to achieve the buff done goals

manage flow kanban

should be updated daily cycle tome / production lead time(time elapsed from the moment w team started working to they are done) customer lead time( time that elalses from the moment a customer or user subfloors work into backlog to the pt. they can use it) throughout - measure of productivity or efficiency of features common takt: available work time/ customer demand during available work time

epics

sponsored by director

key drivers for agile

stronger communication between business and It costs shorter feature releases

Spotify

structure in culture mandatory practices avoid hierarchy al structure squad - basic unit of development (similar to scrum) tribe - collection of squads less than 100 ppl chapter - group of people with similar skills within same tribe guild-group of people having similar skills and competenciess

social knowledge management

team shares the knowledge through discussions and forums instead of calassroom sessions

Sprint Burndown Chart

the trend of work remaining across time in a sprint. the source of data is the sprint backlog with work remaining tracked on the vertical axis and days of a sprint on the horizontal axis

Release Burndown Chart

the trend of work remaining across time. in a release or product, the source of data is the product backlog with work remaining tracked on the vertical axis and number of sprints on the horizontal axis

devops transition

transition from development to support team

niko niko calendar

update calendar with mood

engineering approach

using CI to deliver simultaneously and have multiple branches of code ready to merge and move to the next stage . shared version control bff

Kanban

visual board encisuoning the existing workflow todo doing done

agile methology

xp, dsdm, fdd, lean , kanban, scrum