Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective -events for inspection and adaptation.

1. Product Backlog 2. Sprint Backlog: 3. Increment: 4. Definition of “Done”: 5. Monitoring Progress

towards a Goal: 6. Monitoring Sprint Progress: - 6 artifacts

Sprint review -
Discussion on backlog what have been “Done” with demonstration and what has not been “Done”;
The entire group collaborates on what to do next, provides input to subsequent Sprint Planning;
Review of the timeline, budget, and potential capabilities
Retrospective:
Inspect how the last Sprint went with regards to people, relationships, process, and tools;
Identify and order the major items that went well and potential improvements;
Create a plan for implementing improvements to the way the Scrum Team does its work.

Self-empowerment, fostering self-organization, technical understanding, conflict mngt – dev team

A project is a unique series of actions with a specific goal within specific time and cost limitations.

Reason for project failures is:

Insufficient product definitions / Lack of communication/ Poor estimation of time and cost

The Initiation Stage has the following main outputs - four strategy documents (i.e., Risk, Quality, and
Configuration & Communication Management), The Business Case document, The Project Plan, Product
Descriptions, Roles & Responsibilities / Project Management Team Structure

What kind of skills do you think a Project Manager should have?

They should include good communication, cost management, an ability to understand the quality
process, process change requests, monitor the project, as well as planning, leadership and team-
building qualities, including teamwork, problem-solving, reporting, facilitating meetings and conducting
workshops. Another important task is the ability to anticipate problems and to be proactive in solving
them. In other words, a good Project Manager does not sit around and wait for things to happen.

Quality Management activities are: defining quality by finalizing acceptance criteria and plan for
achieving the agreed quality goals, quality control is techniques and activities to inspect & test products.
Quality assurance assures planned Quality activities are done (d) quality improvement.
Prepare the schedule:

Define activity sequence • Assess resource availability • Assign resources • Level resource usage • Agree
control points • Define milestones • Calculate total resource requirements & costs

There are three steps to Risk Management which are Identification, Assessment and Control: •
Identification: How to identify and describe the risk. • Assess the Risk: Ask what the likelihood of the risk
is, its impact on objectives and when it is expected. • Control the Risk: How best to respond to a risk;
assign a risk owner, execute responses and monitoring.

Risk Register Example • Risk Identifier: • Risk Author: • Date Registered: • Risk Category: such as quality,
network, legal and supplier. • Risk Description: • Probability Impact: • Proximity: • Risk Response
Category: • If a threat, decide to avoid, reduce, fallback, transfer, accept or share. • If an opportunity,
decide to enhance, exploit, reject or share. • Risk Response: • Risk Status: • Risk Owner

Change priorities by MoSCow technique. Must have, Should have, could have, wont have.

The process are: • Starting Up a Project • Initiating a Project • Directing a Project • Controlling a Stage •
Managing Product Delivery • Managing a Stage Boundary • Closing a Project

The following Activities are to be done in the Starting Up a Project Process: • Appointing the Executive
and the Project Board (by Corporate or Program Management & Executive). • Designing & appointing
the project management team. • Preparing the outline Business Case. • Selecting the project approach
and assembling the Project Brief. • Planning the initiation stage. The Initiating a Project Process is the
process that defines the Project Product, product quality, project timeline and costs, risk analysis,
commitment of resources and assembles the PID . Process The Controlling a Stage Process is where the
Project Manager does most of their work. The Project Manager watches over the work, takes corrective
action, observes changes, and communicates with stakeholders, which includes reporting. The
Controlling a Stage process monitors each stage and is repeated for each stage in the project.

sprint planning, daily scrum, saprint review, sprint retrospective.

Time to market less, risk less, continious improvement. ROI high.

Agile iterative software development methodologies, where requirements and solutions evolve through
collaboration between self-organizing cross-functional teams. Agile encourages transparency, frequent
inspection and adaptation. It is an iterative and incremental approch to optimize predictibility and
control risk.

Scrum is subset of agile divided into the three categories of Roles, Artifacts, and Time Boxes.

Shorter Period preferred because it’s easier for team to estimate, plan and complete the work, product
owner gets enough time to change priorities and allows team to adapt market pressures.

Sprint planning is consequently divided into two parts:

Sprint planning I : Product owner presents priority wise user stories from the product backlog to the
team, and team taking stories based on the capacity which can be deliver by end of sprint.
Sprint planning II : Team adds details to user stories in sprint backlog, estimate and split them into tasks,
identifying parts which needs clarification, agreeing about who will be working on which tasks.
Should be servant leader that means leading the team at the same time understand the problem which
is faced by team and having insights of the team. Need to be convincing. Should be team player/ friendly
enough with the team so that team is able to share the problem with scrum master. Patience is needed
for listening the team , leading with an example is also required, so that team is very much motivated
like giving the demo of whatever functionality team is implemented to product owner or customer,
improve bonding and faith within the team. He should have capability to removes obstacles which may
affect to fulfill sprint goals, maximizing productivity of the team, Guides team and product owner to
follow agile principles.
Burn Down : Working days vs remaining effort, used to track sprint status.
Velocity : average number of points from past 3/4 sprints. It is used to help predict when backlog items
will be delivered.
Tool : Selenium for automated testing, Jira/TFS for ALM, Jenkins for CD, GIT for Code Repository

A story is done only when it is development complete + QA complete + acceptance criteria are met +
DoD is complete+ it is eligible to be shipped into production. In this case if there are defects, the story is
partially done and not completely done, so I will spill it over to next sprint.

What qualities should a good Agile tester have?

Agile tester should be able to understand the requirements quickly.
Agile tester should know Agile concepts and principals.
As requirements keep changing, he should understand the risk involve in it.
Agile tester should be able to prioritize the work based on the requirements.
Communication is must for a Agile tester as it requires a lot of communication with developers and
business associates.

Zero sprint - Activities like setting development environment, preparing backlog etc needs to be done
before starting of the first sprint and can be treated as Sprint zero.

Some major principles of agile testing are:

Customer satisfaction
Bug-free clean code
Changes are welcome by customer
Whole team business people and developers work collectively
Instead of lengthy documentation, focus on essence
It focuses on face to face conversation
It promotes sustainable development

Agile manifesto defines 4 key points:

i. Individuals and interactions over process and tools
ii. Working software over comprehensive documentation
iii. Customer collaboration over contract negotiation
iv. Responding to change over following a plan

Sprint review meeting – Live demonstration of potential shippable product increment. And feedback
from stakeholders resulting in additional items added to PB.
Retrospective is a meeting to know how things went during the sprint and discuss possible
improvements areas.
What is the biggest challenge you faced in your project while handling the Scrum team members?
Adoption of Scrum: The team was new to this framework. Hence I had hard time in motivating them.
Had to train them on regular basis until the team members picked up.
During initial stages of scrum stabilizing the velocity was challenge due to less technical capability,
arranged technical training for new team members
Defect density was higher due to requirement ambiguity in the code. Suggested to use Static code
analysis tool like Sona , resharper.
Infrastructure issue – delayed access in source system, escalated to higher management and personally
followed it up with IT team. Without source system dummy workflow created.
Conflicts between two resources having same band, due to this environment became very bad, they
were not ready to work as a team. This requires my attention, First I did not know where the problem is.
Then I talk to them individually multiple times. Arrange a football match where both of them in a team,
that’s how I have managed the situation, it took long time.
Continuous integration not happening, so tester having problem, they are not getting enough time for
testing. Regression was not happening, implemented continuous integration.
Meeting were not time box, discussions are happening but not to the point in daily stand up. I told if you
need Technical discussion then do it one to one after daily scrum.
Prioritization of PB was not done properly arranged meeting with Product Owner and team to do
requirement once again.
If team fails to meet commitment what Scrum Master should do?
Would like to talk with team to understand the problem area like is there any over commitment, is there
any impediment, next check is estimation part and grooming has been done properly on not for
estimation. After analyzing and discussing with the team, all the aspects I usually come to a solution
what can be done to improve the productivity of the team. Understanding on the requirement was not
good enough, they are estimating on basis of just gut feeling, they were not asked questions which were
required, they did not have clarity on dependency of other system. So I have initiated a joint technical
discussion with other related teams. Need to discuss with PO and manage the scope again. They were
not using planning poker method, not able to relate user story points with the task break down.

Storypoint estimation by planning pocker(fibonaci serise) - relative metric to determine the complexity
and effort and size which is associated with user story.

Product Backlog Iteam – I(indipendent)N(negociable)V(Valueable)E(estimable)S(Small)T(testable) user

story

A project is a unique series of actions with a specific goal within specific time and cost limitations.

 Over 13+ years of IT Experience including, analysis, design, development

and implementation of Data warehousing focusing telecom and automobile
industry.
 BI Solution Architectures, effort estimations and volumetric analysis and
dimensional data modelling of multiple DW / BI projects.
 Having experience in analyzing and building the DWH data models from
scratch and reengineering existing model after analyzing existing database
and ETL structure. Having Working experience in creating Technical
documents , ETL Specification , System specifications documents and Unit
test scripts.
  Expertise in Reporting &ETL Platform used tools like BODS , BOXI , CRXI,
Datastage, Informatica etc.
ABM _ HMS – BI developer - 2003

CTVA -2006- Revenue Assurance (RA) is about building controls to all the revenue
leakage risks in the Switch to Mediation or from Mediation to Rating or from Rating
to Billing etc processes. The key process of the RA solution is to identify the cost
drivers & root causes of revenue leakages. The scope comprises of Extraction,
Transformation and Loading of almost 450 million records (CDRs/Day) from
Swt,Intec, Arbor, Billing, IN, and Mediation both for Airtel & Infotel.

BSL- 2007- Xerox Capital Services (XCS) - Data Modelling ,ETL design, Making of
Universes, Reports. tool - SAP BO, ER WIN, Data Stage, and SQL
E-Plus – worked as Data Modeller, Before modelling there was two steps -
analysing multiple data source by Reengineering existing model after analyzing
existing oracle DB and Informatica work flow to explore the in depth business logic
and then writing design doc. Prepare db structure and ETL architecture , mapping
doc. We have followed agile framework. Skills: SAP BO, ER WIN, BODI, and Oracle,
Crystal, Informatica.
VW –Worked as Subject matter expert for data migration, which was a
maintainance project. There was lots of CRS to be handled by gathering
requirement from user/ cutomer then writing design doc and data model
respectively which helped to transform data and create desired reports. Prepared
the estimation matrix and educate team on business flow. Skills – SAP BO, ER WIN,
BODI, SAP Dash Board, and Oracle 11 g.
DU - I was part of the team for reporting financial and project performance data. I
was responsible for ETL architecture designand , managing data integration creation
of reporting layer. And educating team with the business flow and responsibilities.
ER Win, Universe designer, Oracle, Crystal report, Informatica.
Continental –This project includes design and development of Web based online
vehical tracking System and fleet management app. Data Architect in agaile
environment – was initally responses to RFP , so that I was part of gathering the
intial requirement. During sprint 0 prepare the basic architectual framwork and data
flow diagram and risk analysis. from sprint 1 which broken down to lowest
granularity level. Tool - ERWin, MongoDB, BODS.