What are Latest Agile Interview Questions and

answers ?
In my previous articles I have tried to give you the details of Scrum Master tips and techniques with
How to pass Professional Scrum Master 1 certification. In this article I would like to throw light on
Latest Agile Interview Quest ions and answers with follow up explanations. Now a days so many
people are moving their career from Technical lead and Project Managers to Scrum Masters or Agile
Coach. This article will give the clear idea about Latest Agile Interview Questions and answers which I
have already faced in many interv iews.
4.The Agile model helps customers incrementally software because it is fast to deliver and they deliver
a product that works with each increment.
5.Customers can review the product before and after each increment, giving them peace of mind that
the development process is on track.
Disadvantages :
1.Because requirements change frequently, developers may not be able to fully quantify the effort
involved in the development process.
2. Agile methods put less emphasis on documents that could cause problems down the road, especially
for new project members.
3.Continued involvement from the client team is expected. This requires the client team to be able to
join the meeting.
4.If the customer team cannot articulate the end result of the system, the project may derail. Agile
development processes require experienced developers who have the skills to develop systems and who
can make quick and critical decisions during the process.
5. Continuous interaction is expected from each team member, increasing the team’s investment of time
and energy.
I hope you like this article on Latest Agile Interview questions and Answers. If you like this article or if
you have any concerns with the same kindly comment it in comments section.
Answer :
Agile testing is a software testing process that follows the principles of agile software development.
Agile development process is an iterative process where requirements are constantly changing
according to customer needs. Agile testing is a continuous process that runs concurrently with the
development process. Agile testing involves continuously testing a system until the desired software
quality is achieved.
Methods of Agile testing :
 • BDD Meaning “Behavior Driven Development”
• ATDD Meaning “Acceptance Test-Driven Development “
• Exploratory Testing
• Session-Based Testing
Question 20 : What are Advantages and Disadvantages of Agile Framework?
Answer :
Every coin has two sides. So there are few advantages and disadvantages of Agile framework :
Advantages :
1.The Agile model facilitates rapid and continuous delivery of software.
2.The Agile model is a flexible model, which helps you respond to changes proposed by your
customers.
3.Agile processes involve high-level interactions between various team members to help quickly
identify problems in the development process.

Question 1 : What is Agile Framework? (100% asked Latest Agile Interview Questions )
Answer :
The agile methodology is employed in the creation of software. It emphasizes on incremental
development techniques, where the goal is to provide the product as rapidly as possible.
Question 2 : What distinguishes agile technique from conventional methodologies?
Answer :
Agile approach uses an incremental development model, whereas traditional methodologies follow a
sequential paradigm. This is the primary distinction between agile methodology and other traditional
methodologies.
The development and testing phases run concurrently in the agile methodology. According to
conventional approach, testing begins once the development process is finished.
Question 3 :Can you give some examples of agile frameworks?(100% asked Latest Agile Interview
Questions )
Answer:
Here are a few examples of agile frameworks:
1.Scrum
2.KANBAN
3.Test Driven Development (TDD)
4.Dyanamic System Development Method ( DSDM)
5.Adaptive Software Development
6.Lean Software Development .

Question 4 : What is mean by Agile Manifesto?

Answer :
A statement supporting agile software development called the agile manifesto was created by 17 like-
minded software development professionals and released in February 2001. It is supported by 12
guiding concepts and built on 4 core ideals.
Question 5 : What are four important values of Agile Manifesto?
Answer :
1.Individuals and interactions over processes and tools :People and interactions above procedures
and equipment.
2.Working Software over comprehensive documentation: Working software is preferred over
thorough documentation.
3.Customer collaboration over contract negotiations: Collaboration with the customer during
contract negotiations
4.Responding to Change over following a plan: Adapting to Change rather than sticking to a plan.
Question 6 : Which are most important 12 Principles of Agile manifesto? (100% asked Latest Agile
Interview Questions )
Answer :
• Continuous Delivery : Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
• Volatile requirements handling : Welcome changing requirements, even late in development.
Agile processes harness change for the customer’s competitive advantage.
• Continuous / Frequent Deployment : Deliver working software frequently, from a couple of
weeks to a couple of months, with a preference to the shorter timescale.
• Daily Connects :Business people and developers must work together daily throughout the
project.
• Motivated Team : Build projects around motivated individuals. Give them the environment and
support they need and trust them to get the job done.
• Clear Conversation :The most efficient and effective method of conveying information to and
within a development team is face-to-face conversation.
• Progress Oriented : Working software is the primary measure of progress.
• Sustainable Development : Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace indefinitely.
• Technical excellence : Continuous attention to technical excellence and good design enhances
agility.
• Maximize the work : Simplicity–the art of maximizing the amount of work not done–is
essential.
 • Self Organized team : The best architectures, requirements, and designs emerge from self-
organizing teams.
• Connect Regular intervals : At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.
Question 7 : What is Test Driven Development with its stepwise process?
Answer :
The answer is that the test cases are written first in the Test-Driven Development (TDD) method of
software development, followed by the coding. Test cases are created to verify what the code ought to
accomplish.
The fundamental guidelines for the TDD development process are as follows:
1.The system feature is first described in a unit test.
2.Running the test is the next step. Due to the lack of the feature in the system, it will fail.
3.Create the code necessary for the system to support the functionality. The basic concept is to create a
straightforward test that will pass the test scenario.
4.Refactor the code where necessary.
For further system features, follow the same procedures as above.
Question 8 : What is mean by DevOps in simple words?
Answer :
DevOps is a collection of principles and techniques that integrate software development (Dev) with
information technology operations (IT Ops) (Ops). DevOps combines the efforts of the development
and operations teams to produce high-quality, dependable software while shortening the development
cycle.
Question 9: How do scrum and agile differ from one another and resemble one another?
Answer :
Software development uses an agile methodology. It emphasizes on incremental development
techniques, where the goal is to provide the product as rapidly as possible. While scrum is one of the
agile frameworks that is included in agile project management. It is also employed in the creation of
software.
Agile completes projects via an incremental and iterative process. Scrum is an iterative and incremental
process.
Question 10 : What is Extreme programming with its principles?
Answer :
Extreme programming, sometimes known as XP, is one of the widely used methods for developing
agile software. It employs an object-oriented methodology and adheres to the same guidelines as the
agile manifesto.
User stories, continuous integration, and test-driven development are just a few of the ideas that
extreme programming is credited with bringing. Extreme programming has the ability to accommodate
changing requirements at any stage of the development life cycle, which is one of its benefits.
Five Core Principles of Extreme Programming are :
1.Communication :This idea emphasizes prompt and direct communication between all parties (mainly
developers and stakeholders).
2.Simplicity :This principle’s fundamental tenet is to keep things straightforward and focus on the
immediate aspects first. The code should be written in a way that it may be quickly implemented and
changed if necessary.
3.Feedback :There are three places where feedback is gathered. Unit testing is a method for gathering
system feedback. Customer feedback is gathered through acceptance testing, while feedback from the
other software team members is gathered through the planning game.
4.Courage :
This approach focuses primarily on the now and emphasizes the bravery needed to design for current
features. A team that practices agile development should also have the guts to admit that needs may
change in the future and will need to be incorporated into the code.
5.Respect: This guiding principle emphasizes respect for oneself, respect for others, and respect for
other team members.

Question 11 :What do you mean by refactoring?

Answer :
Refactoring is the process of making changes to existing source code without affecting how it works.
Question 12 :What is pair programming with its advantages?
Answer :
Pair programming is an agile software development methodology in which two developers work
together as a team. Of the two developers, one writes the code, called the driver, and she reviews the
code, called the observer. You can switch roles as needed.
Advantages of Pair Programming :
Better Code Quality :Pair programming results in better code quality and fewer code bugs. This is
because other developers are constantly checking the code as they write it.
Solution Oriented : Pair programming makes it easy to find solutions to problems that arise while
coding. This is because other partners will help you. If one of the partners is more experienced, they
can teach other developers, making it easier to transfer knowledge.
Question 13 :What are different Agile estimation techniques and explain any 1 Agile Estimation
techniques with example? (100% asked Latest Agile Interview Questions )
Answer :
• Planning Poker
• T-shirt sizes
• Affinity Estimation
• Sorting Method
• The Bucket System
• Three-Point Method
• Dot Vote
About Planning Poker step by step :
Planning poker is an estimation technique that involves collaboration between team members. With the
developer’s help, it runs before the iteration starts.
Step 1 :
Each member receives a deck of planning poker cards. Card values are similar to Fibonacci numbers.
The number represent story points/ estimated days.
Step 2 :
Product owners read user stories and explain them to the team. Developers are available for further
discussion if you have any questions.
Step 3 :
After discussion, each member estimates the effort required to develop the story and personally chooses
a card to represent that effort.
Step 4 :
If all cards are revealed at the same time and all are equal, the story is inferred based on the value of the
cards. If the cards have different values, continue discussing until all team her members agree on the
same number.
Question 14 :Explain Tshirt Sizing technique with steps?
Answer :
T-shirt sizing is an estimating technique used to measure the size of user stories, and is primarily used
when relatively large backlog items need to be estimated.
T-shirt sizing uses your t-shirt size (XS, S, M, L, XL) to extrapolate your story.
Determining sizing requires open discussion and decide size of the story.
Question 15 : What is mean by Lean Software Development?
Answer :
1.Lean software development is an iterative, agile methodology that borrows the principles of the lean
manufacturing process and implements them in the software development process.
2.Lean principles adopted include fast delivery, elimination of waste, optimization of development time
and resources, and building product quality.
Question 16 : What do you mean by Kanban?
Answer :
Like Scrum, Kanban is one of the popular frameworks for Agile software development. Kanban is a
Japanese symbol. In this framework, work items or user stories are displayed on a Kanban board and
the team can see the status of each user story on the board. Kanban allows you to develop your product
in one big development cycle instead of iterating (like Scrum). Kanban is incremental, not iterative.
Question 17 : What do you mean by ScrumBan?
Answer :
1.Scrumban is an agile development methodology that combines Scrum and Kanban.
2.Scrumban is primarily used for maintenance projects that use Kanban principles to improve the
Scrum process. It helps project teams optimize their processes.
3.The scrum part of scrumban is determining the scope of work that can be completed in the sprint and
prioritizing tasks.
4. The Kanban part of Scrumban is used to improve processes and visualize workflows. Scrumban uses
the Kanban pull system. Items are continuously pulled from the backlog.
Question 18 : What is difference between Iterative development and Incremental Development?
Answer:
Iterative Development :Software is developed and delivered to customers through an iterative
development process. As customer feedback is received, it is incorporated into the software,
redeveloped in sprints, and delivered to the customer.
Incremental Development:In the incremental development process, software is developed in stages.
Each increment contains the complete functionality of several sub-features of the system.
Question 19 : What is mean by Agile Testing with its methods?

What are 5 scrum values with examples?

In my previous article I have given the multiple examples of scrum and scrum theory in detail. In this
article i would like to elaborate more on different values of scrum mentioned in the scrum guide. I have
already explained about the 3 pillars of scrum i.e. Transperancy,Inspection and Adaption in detail.
These three pillars are important in scrum theory to ensure that team will work collaborative manner,
team will have to respect each others decision and team have to adapt the change happened within or
outside organization.In this article i would give you more information about 5 scrum values with
examples.
5 Scrum Values :
As you know that scrum is a framework which is used to resolve complex adaptive problems to deliver
the product productively and creatively. The scrum framework mostly dependent on the core values of
scrum. The following are 5 Scrum Values :

1.Commitment

2.Courage

3.Focus

4.Openess

5.Respect

I would like to give the examples and explanation of each value so that it will be easy for readers to
understand.
Scrum Values

Reference :

https://www.scrum.org/resources/blog/5-scrum-values-take-center-stage
Value 1 : Commitment :

The commitment is most important value of scrum where team should be committed to complete the
sprint goals. There are three types of commitments for the scrum team.

1.Commitment towards sprint Goal : The most important is to complete and focus on the sprint goal.

2.Commitment as teamwork : The scrum theory is based on inspection and adaption strategies. Team
should be committed to inspect the deliverables and needs to adapt the changes.

3.Commitment as yourself : As a part of scrum theory we require to give the best to achieve the scrum
goal asap.

Example : If google needs to complete delivery of google doodle on daily basis and the team should be
committed to deliver it on daily basis.
Value 2 : Courage :

The courage is another important factor of scrum framework. The scrum is about to take a risk and find
the more optimal solution. Scrum team members have courage to do the right work and deal with
complex problems. The scrum team have courage to work with tough problems.

Examples of Courage :

If we can see the google 15 years before and google today. Every team of google have showed the
courage to implement multiple ideas which will improve google algorithms. One of the example of
courage is google is doing daily deployments and one of the best example for it is google doodle.
Value 3 : Focus :
The scrum gives the new approach which is different than the traditional approach and all it is based on
theory of empiricism. The scrum is following iterative and incremental approach and it gives the focus
to complete sprint goal. Once the requirements for sprint are clear the goal has been created. The team
as well as individual in scrum team have focus on the goal. If team have focus on the goal then it will
impact positively on the product delivery.
Value 4 : Openness :

This is another important value of scrum. As we are working in cross functional team together the
people from different teams needs to work together. The induction of sprint requires openness and
gives all the knowledge to the team openly. Team members should have to be open towards work and
progress.

Example :

In Facebook if we require to complete one functionality as a sprint. They have scrum team of 6
members which has different technical skills. Each should have to give the knowledge to the team
members to achieve the goal.
Value 5 : Respect :

The respect is another important value of scrum where scrum team should respect the opinion of team
members. Every team member should have right to present their opinion and not only product owner
but also scrum master and team should have to respect the team members opinion to achieve the sprint
goal. Scrum team should respect the colleagues ,their opinions and their experience.

These are above important values of scrum. I hope you like the article on 5 scrum values. If you like
this article on 5 scrum values of if you have any issues with the same kindly comment in comments
section.

What are different uses of scrum with

examples?

Object 1

In my previous article i have given the definition for scrum with one real world industry example. I
would like to explain the multiple uses of scrum with real industry examples. As we all know that the
scrum framework initially used in 1990s or earlier to manage and develop the multiple products. The
scrum is not only used in software industry but also it is been used in multiple complex problems. The
essence of scrum is to deal with complex adaptive problem with using small -small teams and
iterations. In this article i would like to throw light on how scrum was used in 1990’s and I will explain
every uses of scrum with real industry example.
Uses of Scrum with examples :
In this section i would like to explain you different uses of scrum with real life industry examples.
According to scrum guide following are different uses of scrum,
Use 1 : Research and identify the viable market,their technologies and product capabilities
The first use mentioned in scrum guide is scrum has been used in early 90’s to do the research and
identifying the viable market. Also the scrum has been use to check multiple technologies and product
capabilities of it.
Example : Microsoft Suit
The best example is microsoft suit. The microsoft suit is in early stages in early 90’s period. The
microsoft company might have did some research related to market using scrum practices and
developed and enhanced the product accordingly.
Use 2: Develop product and enhancements
The scrum has been used for development of multiple products and do the enhancements on it
according to the market changes.
Example : Microsoft Suit
If you can see the microsoft suit product at 90’s and microsoft suit today. There is vast difference
between it. The product remains same but multiple enhancements has been done in the period.
Use 3 : Release Product Enhancements as frequently many times per day
When user or organization wants to see continuous improvement on product we need to do the frequent
deployments for adding multiple functionalities. The scrum framework gives you ability to do frequent
deployments.
Example : Google doodle
If you can see the google doodle is changing on daily basis. This is best example of frequent
deployments.
Use 4 : Develop and sustain the cloud which is online,secure and on-demand and other
operational enviroments for product use
The scrum provides ability to develop and sustain the cloud .It provides the cloud which is online-
secure and on demand for operational product use.
Example : Applications needs to migrate on cloud
 Object 2

Now a days so many application migrating on cloud. We can use scrum to check for continuous
improvement.
Use 5 : Sustain and renew products
Now a days the demand from client is changing day by day. So to sustain and to do continuous
improvement on products scrum is used.
Example : Uber application
The uber has enhanced the uber eats and other functionalities to sustain the product in market. It also
uses the renewed product which is user friendly in nature.

These are above some important uses of scrum mentioned in the scrum guide. Apart from that now a
days scrum is used in multiple situations,
Use of scrum in daily lives and individual ,societies :
The scrum is useful in developing software,hardware,embedded software, networks interacting
function, autonomous vehicles,schools,government organizations,marketing,managing operations in
organizations and almost everything we are using in our day to day life as individual and societies.
Handling complex problems :
Now a days the complexity of environment and market as well as technologies increased rapidly. The
new technologies are coming on frequent basis which gives multiple new functionalities. The scrum’s
utility has proven day to day basis to deal with such problems.
Knowledge Transfer :
The scrum has proven that it is useful for effective and incremental knowledge transfer. So now a days
most of parent organizations are using scrum for managing the products, services and parent
organization management.
Effective product delivery using small team :
In scrum we are focusing on small teams .The individual teams are highly flexible as well as adaptive.
These strength are important for operating single,several and many networks of teams that
develop,release,operate and sustain the work and work products with thousand people.
These are some most important uses of scrum. I hope this article will be useful for you. If you like this
article or if you have any suggestions kindly comment in to comments section.

What is mean by Agile Vision Statement

Object 3

In my previous articles i have given the information about the different phases of Agile process and
Sprint Zero of Agile scrum process. In this article i would like to give you the information about the
Agile Vision Statement with multiple examples of how to write Agile Vision Statement in detail. The
Vision statement is most important step for Agile development project because without vision
statement we cant start work on the project. It will give the base path for project initiation and
completion. The Agile Vision Statement is part of initiation process for scrum zero.

Sprint Zero : Starting with Vision Statements :

As i have already explained about Sprint zero process in detail . After we complete the on-boarding of
team we require to start with vision statement. It is most important part or starting point to kick off the
project. So we have question in mind that what exactly mean by vision statement and why this is so
much important to kick off or to start the project?
Project Vision : The Project vision statement is important statement which will give us quick summary
about how the project or the product will support the company or organization. You can say that it is
the statement which will give you information about the goals of product or project.
The vision statement simply gives us idea about the project in one simple statement where we can
explain the best meet the needs of multiple stakeholders. Every project wants to go with proper
direction in initial phases. That will be the best way to succeed your project. The Vision statement
always guides us for choosing current and future course of action in high level.
Initiation phase for Sprint Zero :

Steps to write vision statement :

In this section i would like to give you multiple steps to write vision statement. The product owner is
responsible for knowing the project about the goals of the project or product.The vision statement will
give us “what we are trying to achieve” so that all the teams like development team,scrum master and
stakeholders.
Kindly check the following important guidelines to create a vision statement :
1. Vision Statement always should be unambiguous.
2. Vision statement will be easy to understand and clear.
3. Vision Statement should give information about organization culture and its values.
4. Vision statement should be rational / realistic.
5. Vision Statement should be shorter so that they are easier to memorize.
The following are different stages to create a vision statement

1.Understanding the project and develop the objective of project :

The first and important step to create a vision statement is to understand the project objective. We
require to check multiple questions related to product or project. The questions are as follows :
1.How will the project or product will benefit the company?
2.Who are the end users and stakeholders of the project or product?
3.How is this product/project similar to already existing products?
4.How is this project or product different than already existing products/projects and how company will
get benefit of it?

Example :
Lets take previous example where we require to build E-Commerce website for the Nordics
countries.So we require to analyse and ask the questions given above. The analysis will be as follows :
1.How will the project or product will benefit the company?
–We are creating E commerce site first time for the company so all third party dependencies for
Nordic clients will be removed by this.
2.Who are the end users and stakeholders of the project or product?
-All Nordic clients and users are the users and stakeholders we have not yet got any.
3.How is this product/project similar to already existing products?
-We have website for Asia so we can use skeleton for that website so that we can reduce the cost
of designing.

Object 4

4.How is this project or product different than already existing products/projects and how company will
get benefit of it?
-The Website will get all the clients from Nordic countries.

2.Create a simple draft version of vision statement :

Once you ask the multiple questions related to project or product second step is to have good
understanding of vision in first go. We require to create multiple vision statements and we need to
discuss direct with customer.Here face to face communication is more important.In this section i would
like to give you draft of vision statement ; you can say that as skeleton of vision statement.
Template :
For: «The customers we are targetting»

Who: «needs the product or project»

The: «product/project name»

Is a: «product/Project category»

That: «product benefit. Reason to buy»

Unlike: «competitors»

Our product: «differentiation or value proposition»

At the end we require to write company strategy and how it will be beneficial to the organization in
following format :
This supports our company strategy to «insert name or description of strategy»

The above is standard template to design the vision statement.

3.Revise,validate the vision statement :

This is another important step to create the vision statement for the project. We require to give the time
to multiple teams to think on the vision statement correctly and they also have right to contribute in
vision statement.In this phase we require to send draft version to multiple teams like : 1. Project
stakeholders 2.Scrum master 3. Team lead 4.Scrum team
Find out what other people think; Whether the statement is clear, if they understand the objectives of
the products or project and if they have any additional input.

Take the feedback and revise the vision statement accordingly. Do this as many times as it takes until
everybody is clear about what you want to convey.

4. Finalize the vision statement

After your final revision is done and dusted, print it out (or write it down) and hang it up somewhere
prominent where you and the scrum team can see it. Depending on your organizational structure you
may need official sign-off from a senior manager. However, this shouldn’t be a problem if the last step
was executed well.

Example :
For the Ecommerce project we have created following statement as vision statement ,
“We intend to provide our customers across Nordics with the best online shopping
experience end to end, with a smart website compatible across different mobile
devices, easy-to-follow instructions, clear and secure payment methods using mobile
money ensuring excellent customer experience. Unlike contemporary online stores, we
will offer huge variety of products yet unique collections. We also accept orders for
customized products at competitive prices. With our effective distributed warehouse,
we are able to take the products to the customers at an optimal time and cost. We
want to reach the $5 million mark by 2022 and want to be the “most reliable” e-
commerce portal. We also want to capture to the all Europe market including baltics
and eastern Europe by 2025”

Hope the above vision statement will give us clear idea about the vision and what we need to achieve in
future.
Following are multiple things scrum team needs to recommend ,
Let’s look at the Scrum’s recommendation about the vision statement.
• Scrum master will make sure that the statement is shared with all stakeholders and product
owner.
• Face to face communication or video conferencing meeting will be the best way to launch the
vision statement.

Sprint Zero | Sprint 0 | Sprint Zero in Agile

Object 5

In my previous article i have given the idea about the agile framework as well as multiple roles in agile.
I have explained about what exactly the Sprint is and different sprints as well.In this article i would like
to explain the Sprint Zero with real life example. I would like to explain thee Sprint zero discovery
process in details so that user will get idea about the process in depth.

What is Sprint Zero?

In this section i would like to give the description of Sprint Zero with its execution steps.Before that we
need to know what is sprint.
The sprint is nothing but the short time period in which scrum team needs to complete
identified amount of work.

Now we need to discuss about what exactly the Sprint Zero in detail. Sprint 0 is nothing but the period
where we require to complete the high level planning to execute the large transformations.
Sprint Zero bulletpoints :
1. Sprint 0 will use to define the high level planning for other sprints
2. Sprint 0 time-span might vary from 2-4 weeks
3. Planning for team and team building will be done in this phase

There are multiple phases in Sprint zero :

Phase 1 : Defining the Objective of Sprint

In this phase user or scrum master needs to define the Objective of the sprint in detail.It involves high
level planning and defining the objective and benefits of the solution.
Example :
If you want to build eCommerce website for the Post office for Maharashtra state. You want to define
objective clearly and the short term and long term benefits of it.
kindly check the following important objectives :
• Place the Post office Maharashtra as player and website will be in all languages supported
globally.
• What will be the probable enhancements as per the demand.
• Provide user friendly system in major Indian languages
• fetch the revenue up to 5 crore rupees
• Define budget allocation to the teams
 • Define multiple external dependencies for the teams – example – Payment gateway system
needs to be used.

Phase 2 : Success Factors Identification

We need to identify the success factors with using multiple metrices.
By considering the online solution for the postal system and eCommerce solution following will be the
metrics used to identify the success factors for the sprint.
1.Value of the Sprint :
It defines nothing but the revenue of the delivered features.
2.Bug Fixes per Sprint :
It defines nothing but the fixes we require to do per sprint.
3.Velocity :
Velocity is nothing but number of story-points.
4.Efforts :
Efforts are nothing but the efforts we spent for completion for sprint.
5.Defects Density :
Defect density is nothing but the total number of defects per sprint.

Object 6

6.Percent Rework :
The Percent rework is nothing but the rework we require to do to complete the sprint one by one.
7.Total test cases :
The total test cases we require to complete the testing features.
The above metrics are used to fine tune the process of scrum.
Phase 3 : Identify and Onboard the team
The third and important step for the Scrum zero is to identify the correct team for the project and
onboard it accordingly. As i have explained in previous articles that the following are three important
roles we require to consider in scrum :
1. Developer Team
2. Scrum Master
3. Product Owner
Developer Team :
By considering the eCommerce project for Maharashtra post department we require to build the team
or onboard the team.
Developer 1 : Which has knowledge of Designing the website.
Developer 2 : Who will complete code part for the eCommerce Website.
Subject Matter Expert : Who is the expert in eCommerce sites.
Client : Client who is the product owner
Technical Architect : Who can design the architecture for the website
Content writer : Who can build the content
Business Analyst : Who can collect the requirements from the customer and give that requirements to
the developer.
Testers Team : We require the functional testing team to test multiple functionalities.
The developer team is nothing but the mixed team with the architects,testers,developers and subject
matter experts.Following 3 points we need to consider while onboarding the team :
• The team has to have mixed experiences with freshers and experienced people
• There is need of technical architect who may guide the team according to technical things
• We require to take adequate number of developers and testers
Scrum Master :
The vital role of Scrum process is on-boarding scrum master. Scrum master should be the person who
can have good experience in managing the projects who can own the scrum process and resolve the
issues related to the scrum process. He is responsible for :
1. Scrum Process : He/She is responsible for the actual scrum process.
2. Problem Solver : He/She is the problem solver.
3. Protector : He has to be protector and he is responsible for any loss in scrum process.

Responsibilities of Scrum master in Sprint Zero :

a. Identify the skill sets required
b. Onboard a stable and cross-functional team
c. Ensure availability of product owner or identify a proxy product owner if customer and team is not
co-located
Product Owner :
The person who is responsible for the vision and goal of project with the actual release management as
well. The product owner is responsible for multiple sprint releases. The customer is the good or best
choice for product owner. We can hire project managers,Customers or business analysts as well.
1. A Proxy product owner is the person who is mirror image for product owner who is responsible
for the all product releases or product related activities.
2. Availability of product owner is a must for Scrum to succeed
3. It is a good idea to have one product owner identified for a team rather than have multiple
people playing that role to avoid confusions and conflicts in requirements.
4. It is recommended to use the client as product owner and business analyst as proxy product
owner for success for scrum

What us mean by Scrum theory with examples?

In my previous article i have given the definition of scrum and uses of scrum with real life industry
examples. IN this article i would like to throw light on Scrum theory with examples. According to
scrum guide scrum is founded with empirical process control theory you can call it as empiricism. Here
the question in mind – What exactly the empiricism means? In this article i would like to give scrum
theory in detail.
Empiricism in Scrum theory :

The empiricism is nothing but the theory which states that the knowledge only comes from sensory
experience. Scrum also follows the process of empiricism which means knowledge comes from the
experience and making decisions are based on what is known? Scrum uses the approach which is
different than the traditional approach – it uses the iterative approach and incremental approach which
optimizes the predictability and controls the risk.

The following are pillars of empiricism :

1.Transparency

2.Inspection

3.Adaption

We will discuss all the above points with example in next section.
SQL Comments
1.Transparency :

The transparency is nothing but the condition of being transparent to the people who are part of the
product development. The process must be visible significant to those who is responsible for outcome.
The transparency requires those aspects which has common standards so that observers can share the
common understanding about what is being seen.
For Example :

The common understandable language must be shared with all participants of the process.

2.Those who are performing in work and those people who are inspecting and resulting the increment
must shared a definition of “Done”.

In Facebook if we require to complete one feature in 2 weeks sprint then all the required people will
know what exactly in the previous sprint deployment in simple language and those people needs to
decide the definition of done.(What exactly needs to complete during the sprint)
2.Inspection :

There are three important points,

1.Scrum users who are part of the scrum will have to inspect the progress towards the sprint goal to
inspect undesirable variances.

So what is mean by undesirable variances? – These are nothing but unavoidable circumstances during
the project where the actual cost is greater than the project cost. Those are the times where scrum team
needs to alert the company that the actual profit will be less than the profit expected.

2.The inspection should not be so frequent that it will affect the product delivery work.

3.The inspections will be more beneficial when those are performed by skilled inspectors at the time of
actual work.
3.Adaption :

At the time of inspection the person who is doing inspection found one or more aspects of process
deviates that are outside acceptable limit. Those are the times when product will be unacceptable. There
are times where we require to revisit the process or the product being process must be adjusted. Those
adjustments must made as quick as possible to avoid further deviation
Events for Inspection and Adaption in scrum theory :

Those are above three pillars of empiricism. Now we can discuss more about the events which needs to
be completed for inspection and adaption in scrum. Those events i will explain better in Events of
inspection and adaption but here i just need to give you flavor of it.

1.Sprint Planning : Here we can do the actual plan for the sprint.

2.Daily Scrum : This event is useful for checking daily progress on sprint.

3.Sprint Review : In this event product owner and development team will review the sprint.

4.Sprint retrospective : Those are the session where we can discuss more about what we are doing
better and what could be better in sprint.
Definition of scrum with real industry examples

Object 7

In my previous article i have given the idea about the Agile framework in detail. In this article i would
like to give you definition of scrum with multiple real life industry examples. The definition of scrum
will be useful in preparation of CSM ( Certified Scrum Master ) and PSM ( Professional Scrum Master
examinations). I have referred the scrum guide in detail and created the content which is simple to
understand to the user.

About Scrum Framework :

Before we go in to deep about understanding the definition of scrum we need to know more about the
scrum. So what exactly the scrum is? The scrum is framework which is used for developing, sustaining
and delivering the complex product.
Things to remember :

1. Scrum is a Framework

2.The Scrum framework utilized mainly in following tasks

a. Delivering the complex product

b. Developing a complex product

c. Sustaining the complex product

There might be another question about who is the father of scrum? The answer is – 1.Ken Schwaber
and Jeff Sutherland.

Definition of Scrum :
Before we start with definition of scrum framework we need to understand more about traditional
software development model. In traditional software development model like waterfall model it was
really difficult to deliver the product on time and there might be so many issues after the delivery. So
Ken Schwaber and Jeff Sutherland come up with some rules are regulations and designed the
framework which is useful to resolve the complex problem for product development and delivers the
product at highest possible value.
Before we discuss about the definition of scrum we need to understand about framework. So what is
framework? Framework is basic structure for building the complex products or to deal with complex
issues.According to scrum guide,
 Scrum is nothing but a framework with using which people can address complex
adaptive problems; using which the productivity and creativity delivering the product
is at highest possible value.

The definition of scrum looks straightforward but i need to explain the definition of scrum with real
world industry example.Before giving you the example of the scrum i would like to give some
important pointers to remember about scrum.

Object 8

1. Scrum is not a specified process , not technique or it is not a definitive method; rather the scrum
is a framework in which you can create your own processes and techniques which are useful to
resolve the complex adaptive problems more easily.
2. Scrum is very useful in continuous growth of the product
3. Scrum is also useful to improve teams and working environments
4. Scrum framework tactics are vary project or organization wise
5. According to scrum guide scrum is , 1.lightweight, 2.Simple to understand 3. Difficult to
master
6. According to scrum guide Scrum consists of multiple scrum teams and their associated
rules,roles,events and artifacts which is important for scrum success and usage.
The above points are very important points to remember when you try to understand definition of
scrum. The understanding will be simple when you understand with real life example.

Real world industry example :

The google is the most successful product in the world. They are following the scrum within the
team.They are not following the specified rules and regulations or neither they are following traditional
software development concepts. When you see the 15 years before google search engine and google
search engine now there is big difference. The user interface for google is very simple where you can
search whatever you want. But now a days if you can see they have added the multiple features to the
google in 15 years continuous development without any downtime. The features are really user centric
and user friendly. They are following the scrum and their focus is to enhance the product creatively.
They are tackling the complex problems in scrums rather than big deployments they are concentrating
on small deployments. The best example of creativity is google doodle.(They might do deployment for
daily basics with using scrum methodologies for the same).
I hope you get clear idea about the scrum definition with simple google.com example. If you like this
article or if you have any concerns of difficulties with the same kindly comment in comments section.

What are different Roles in the scrum team ?

Object 9

In my previous articles i have given the basic idea about the scrum and multiple sprint processes. In
this article i would like to give you the brief description about different scrum roles with real life
industry example.I would like to give you the examples of multiple types of Scrum Roles with the real
industry examples. We can able to give the existing roles in organization to give the real Scrum
Roles.As an example you can give the role of Scrum Master to Project Manager and Project Manager
can play the role of Scrum Master.These are multiple roles in the scrum team .

Scrum Roles With Examples :

In this section i would like to give multiple roles information about the scrum with real life industry
examples.First I would like you to give the multiple type of important Roles in the scrum.

Product Owner Role :

The most important role for Scrum is product owner role. The customer which has vast experience in
the specified product and the business analyst which has mid scale experience are the best people for
product owner role.
Following are some important responsibilities of Product Owner :
1. Responsible for defining stories.
2. Responsible for all type of releases and its planning.
3. Responsible for the backlogs.
4. Responsible for prioritizing the project tasks and execute the important project tasks.
5. Evaluation of Progress of the product.
6. According to the project requirements we need to appoint one or two product owners.One from
Customer side and other from company side who has good Business analyst experience.
Example :
You have new client for Indian postal services. They want to grow the business in Nordic countries like
Finland,Sweden and Norway.The requirement is to create the E commerce website for Nordic
countries. Here we need to build the scrum team and need to hire Product owner as sprint zero process.
We require to hire one 20 Year experience customer and 6-7 year experience business analyst.
As a first step we need to hire customer side manager who can act as a Product owner .
Mika K – We have hired customer side manager who has 20 years of vast experience about multiple
products of ECommerse.
Rahul S – We have hired the Business analyst with 5-6 years of experience.
Scrum Master Role:
Another important role is scrum master role in agile process. The scrum master is a person who is
responsible for the agile or scrum process and responsible to execute the sprints. The scrum master is a
person who is mostly experienced in management and who has experience to manage the
projects.There are following important responsibilities of scrum master :
 Object 10

1. Interaction between scrum team and Organization : With small stand up meetings scrum
master is responsible to have interaction between the scrum team and organization or client.
2. Clearing Obstacles : The scrum master is responsible to clear the obstacles in the scrum
process.
3. Team Productivity : The scrum master is responsible to improve the productivity of the team.
4. Relationship between team and Product Owner : Scrum master needs to ensure that the good
relationship between Product Owner and team.
5. Team Protection : Scrum Master is responsible for protecting the team from outside
interruptions and distractions.
6. Team Success : Scrum master is responsible for scrum team success with his skillset and
communication skills.
7. Agile Coach : Scrum master is responsible to teach the different agile practices to the team.
Example :
In the same Indian Postal project we require to appoint the scrum master . The best candidate we need
to choose from set of following people.
• Customer – Rokul (Busy, has critical opinions and good business knowledge )
• Customer Representative – Rambo (Agile enthusiast and available for clarification of queries )
• Business analyst – Rohan (Has good business expertise and team management experience)
• Project Manager –Kishore S (Respected by people)
• Technical Lead–Amit S (Sound technical and domain expertise and good knowledge for
team management)
• Programmer – Rohit (experienced developer)
So from the above set of peoples we require to choose one scrum master and one back up for the scrum
master. Everyone have their own analysis choosing the scrum master. I will choose Amit S as Scrum
master and Rohan as back up scrum master.
The Scrum Team :
The scrum team is responsible to execute the sprints and clear the backlogs. The team must be the
balanced team of multiple skilled developers,database administrators,testers and technical architects.
The Scrum team size will be member of 4 to 9 people who can complete the sprint. Scrum master is
responsible to recruit the people in team if any skills-sets are required to complete the sprint.
• Business analyst – Rohan (Has good business expertise in Postal domain)
• Project Manager – Ricardo(Respected by people)
• Technical Architect – Pradnya(Sound technical and domain expertise)
• Programmer – Rohit(experienced developer in C CPP JAVA and SQL)
• Programmer – Shelly (Fresher)
• Programmer – Gordon (experienced developer in Designing the javascript)
• Tester – Renuka(experienced tester)
• Tester – Piku(Fresher)
• Content / technical Writer – Ruskan
• User interface designer – Thomas
• Architect – Mmartin(Strong technical expertise)

What is Scrum? The example of Scrum

Object 11

In my previous article i have given you the detailed level idea about the Agile Framework with multiple
real life examples. In this article i would like you to give the exact idea about What is Scrum? and will
try to explain different phases of scrum. I would like to give the difference between what is scrum? and
what is waterfall model.

Difference Between Waterfall model and Agile :

In this section i would like to give difference between the waterfall model and agile model. I will try to
give the difference in tabular format so that it will be easy for user to understand. Before that let us see
the multiple drawbacks of traditional waterfall model :
Drawback 1 :Late Product Delivery :
The first and important drawback of waterfall model is Late product delivery as compare to Agile
model. The product needs to go through all the phases and it will take months or quarters to deliver the
product.
Drawback 2 : Cost of Rework
The SDLC cycle for waterfall model is quite high so the cost of rework with waterfall model is very
high.
Drawback 3 : Big phase of requirement gathering
In waterfall model the requirement gathering phase is always high and client cant change requirement
after its freezing is done.
Difference chart :

Agile Software Development Model Waterfall Model

Deployment cycle time for agile development Deployment cycle for waterfall model is quite high.
model is Weeks It is in months or quarters.
The deployment is done in agile model The deployment needs to be done with all features
requirement wise or feature wise. or product
You can change the requirement with less rework Difficulty is changing requirement and cost of
cost rework is quite high
Response to change is very quick Response to change is very slow
Let us understand the scrum concepts in detail. There is always question in mind that what exactly the
scrum is?The scrum is nothing but the framework where all teams works together to achieve a specific
task. We need to understand about scrum cycle.Scrum Cycle is the iteration in Scrum popularly referred
to as ‘Sprint’. A sprint consists of Plan-Produce-Inspect-Adapt. Application development, is achieved
by sprints in a sequence with no gaps in between them.

1. Plan : The planning is first phase of sprint where we require to complete the planning about
what kind of work needs to be done and how much of the work can be achievable. We require to
include team as well as customer to complete planning.Planning is done for the sprint at hand
2. Produce : The second important phase is to produce the work. The production of the work
needs to be taken care by the development team.
3. Inspect : Inspection of work or detailed level testing of work is another phase of sprint.At the
end of the sprint, the customer along with the stakeholders verify the product to see if it meets
the requirements as per agreed conditions called definition of done.
4. Adapt :The team retrospects on what went well in the current sprint, what can continue and
what can be done better in the next sprint. Improvements in the process are discussed here.
Doing this would help them to continuously improve the way of working across sprints
Terms used in Scrum :
Sprint : Sprint is nothing but the iteration of multiple small phases in the scrum to deliver the specified
functionality or to deliver the specific product.

Object 12

Cross functional: We require to have multiple skill-sets in the present development teams. In
development team we require to include multiple teams like development team which may include
development team, ranging from developers,architects,testers,analysts.
Self Organized : This concept is used for the development team about ability to handle the each and
every sprint work.
1. The ability to take the decision and commit to sprint deliveries.
2. Team does have ability to resolve any conflicts coming internally in the sprint deliveries.
3. Team needs to take direct ownership for all the tasks given as well as other than task given.
Definition of Done : Definition on done is very important term in scrum which allows the agreement
between customer and teams about the sprint work needs to be done.
Example for DOD :
• Code complete
• Code reviewed
• Unit Tested
• Integration Tested
• Acceptance Tested
• System Docs and User Docs updated
• No Priority 1 or Priority 2 defects remaining

Important Roles in Sprint :

The following are important roles which may help us to understand what is scrum? The following 3
important roles and its description in sprint .
 1. Product Owner : The product owner is the person who is responsible for vision and goals of
release, Return On Investment, date and scope of release.
2. Scrum Master: The scrum master is a person who is responsible for scrum process, problem
solving and protection of development team.
3. Development Team : The development team is set of multiple roles team who is responsible for
the work done as per sprint goal.

Types of Meetings in Scrum :

1. Sprint Planning Meeting : The most important meeting is sprint planning meeting where all
the team members and client needs to decide the plan and the actual deliverable for sprints.
2. Daily Scrum Meeting :The scrum master is responsible to schedule the daily scrum meeting
where team needs to discuss the daily work status and issues and concerns with scrum master.
3. Sprint Review :The meeting needs to be schedule at the end of the sprint where product owner
needs to review all work done for next release process.
4. Sprint Retrospection : This is internal meeting of development team where team needs to plan
for the improvement of process.
5. Product Backlog Refinement:The scrum master and product owner along with customer needs
to schedule this meeting on regular intervals where we require do discuss the product backlog
refinement.

Deliverable Produced :
1. Product Backlog : Product backlog is Pending list of items to be developed.
2. Sprint Backlog : Sprint backlog is list of tasks planned for the current sprint with their effort
estimate
3. Increment : Increment is nothing but the working version of the software produced in the
sprint.

What is Agile Framework?

Object 13

In my previous articles i have given the basic idea about SQL and SQL related questions. I would like
to start with Software engineering practices so that user will get idea about how to execute the specific
project.In this article i would like to explain more about the Agile Framework and the Agile practices.I
would like to give you some basic tasks of development team member and scrum master team member
with Agile Framework.
Agile Principles :
There are so many types of traditional Software engineering approaches like
Spiral,Waterfall,prototyping approach.With these traditional approaches the return of investment will
get after the project deliveries.There is need to design the approach where investors will quickly ensure
the return of investment.The approach is called as Agile approach and designed framework is called as
agile framework.
Agile is a time boxed, iterative approach to software delivery that builds software
incrementally from the start of the project, instead of trying to deliver it all at once at
the end.

I would like to give the basic principles of Agile Framework :

1.Customer Satisfaction through continuous delivery :
The most important goal of Agile framework is Customer satisfaction through the continuous
delivery.It is teams responsibility to deliver the quality software functionality.
2.Handle changes in requirements :
The agile framework is different than any other frameworks where we are focusing on continuous
development of software.It is not too late for customer to do the changes in requirements.In agile
approach developers can handle the changes in requirements quite easily.
3.Frequent Delivery of working Software :
In agile framework user can deliver the working software on an frequent basis with using shorter
timescale.
4.Business users and developers work together :
In agile approach the business users and developers works together to complete the requirements of
project.
5.Daily meetings and face to face conversation :
The efficient and effective way of communication is daily meetings and face to face conversation.The
agile approach allows you to communicate face to face on daily basis of in intervals.
6.Motivate individuals to complete project :
The agile approach will give us the all kind of support to build the healthy and motivating environment.
7.Working Software is primary measure of progress :
The working software is primary measure of progress.
8. Sustainable pace Management :
The Agile approach always used to develop the constant and sustainable pace.The sponsors,
developers, and users should be able to maintain a constant pace indefinitely.
9.Good Design and Technical intelligence :
The Agile approach always gives Continuous attention to technical excellence and good design
enhances agility.
10.Identify the work not done :

Object 14

We require to identify the work not done with using the Simplicity means the art of maximizing the
amount of work not done is essential.
11.Self Organizing teams :
The best architectures, requirements, and designs emerge from self-organizing teams.
12.Calculating the effectiveness of team :
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its
behavior accordingly.

Basic Roles in Agile Framework :

Now a days in most of multinational companies 70% projects approximately follows the agile approach
for continuous development and delivery of the project. In this section i would like to give you the
basic idea about basic roles in Agile framework.
Developer Role in Agile :
The key role in agile is developer team member in Agile team. There are following roles and
responsibilities for developer team member :
• User Stories writing : The key role for developer is to write good user stories, prioritize, and
estimate them using story points
• Sprint Participation : The another thing developer needs to do is to Participate in the
ceremonies of a sprint like sprint planning, stand-up, grooming, review and retrospection.
• Software Development : The vital role of developer is to focus on creating working software.
• Customer Communication : The another important role software developer needs to complete
is to work collaboratively with customers, teams and stakeholders.
• Technical Excellence :The last important role software developer needs to do is to adopt
technical practices to sustain and accelerate sprints.
Scrum Master Role in Agile Framework :
The second most important role in agile framework is scrum-master role.The scrum master is
responsible for :
• Team Building : The scrum master is responsible for team building activities to onboard team
with right composition
• Conduct release planning activities : The second vital task scrun master needs to complete is
to build user story writing, prioritization, estimation and arrival at release date.
• Meetings : The another task of scrum master is to conduct Scrum ceremonies and update Scrum
artifacts
• Leadership : Scrum master needs to play the role of a servant leader and guide the team to
execute the project and adoption of technical practices.