I am NOT a "reads dead book" Project Leader

 You employ me for my exceptional composition of Reality Solutions


in a project management environment

Below Are My Project Management Theoretical Foundation - For PMO Work Reference
SCRUM Simple Rules - 3 Roles + 5 Events + 3 Artifacts
SCRUM 353.png
Social Media.jpg
SCRUM Model in AGILE Software Development
Only an overly intellectual project manager
is capable of
remembering ALL the below
and vomit them out during interview 

This is to tell my employer that I always succeed by taking a different approach to any given role to play in project management.


Because most of the time, "The Big Picture" is always blur to every team members

... which means sketchy outline of the actual requirements and ultimate business goal.



What is SCRUM Model? 

Scrum is an iterative and Incremental model for application or product development. The improvement of the venture is accomplished through an iterative cycle called sprints. Toward the beginning of each sprint, a cross-functional group chooses things from Product Backlog and resolves to finish the things before the finish of that specific sprints. Ordinary the group assembles for a shorter gathering to review its progress. Toward the finish of the Sprint, the group reviews the work item with partners and exhibits what has been developed.

The criticism or feedback is then Incorporated in consequent sprints. Toward the finish of each sprint, scrum underscores that the working programming is completely tested and conceivably made shippable. The sprints are firmly time-boxed (Time Box is authored as a fixed time is assigned for action. Certain expectations are committed for getting finished at this time.) and happen successively. The end it of a sprint doesn’t get expanded. Independent of the planned work at the first meeting.


These days, Scrum is a person of the most preferred frameworks and it is commonly used by IT businesses all in excess of the entire world. Talking about “Agile” persons normally mean Scrum, but what is Scrum in observe?

Scrum is broadly utilized by software program enhancement teams and in accordance with “The 9th Once-a-year Condition of Agile Report”, 72% of software program groups use Scrum or Scrum’ hybrid. Conversing about hybrids companies frequently mix it with Kanban or Lean procedures.

How can Scrum be distinguished from Agile? – Scrum is a subgroup of Agile and when Agile Enhancement is an established of guiding principles, 12 ideas, and values ​​for implementation of agile jobs, Scrum runs these values ​​and rules of Agile and furthermore it is probable to utilize numerous techniques and procedures inside this framework.

The sizeable factors of Scrum Progress: roles, occasions, artifacts, and principles.

Scrum roles

Scrum consists of three primary roles.

  • Product owner

  • Team

  • Scrum master

Other contributors are-

  • Managers

  • SMEs(subject matter experts)

  • Architects

  • Customers

  • Vendors

Product Owner

Product Owner is in charge of the followings:-

  • Giving the situation of the project(Vision) to the group.

  • Amplifying the estimation of the project and craft the tasks for the scrum group.

  • Dealing with Product Backlog.

  • Obviously and clearly communicating item build-up things on the Product backlog.

  • Organizing the things in the Product Backlog to best accomplish objectives and Mission of the project.

  • Guaranteeing that the Product Backlog is unmistakable, straightforward and clear to about what the group will chip away at straightaway. On the off chance that a colleague is prescribing a few changes to an item accumulation things need, it must be talked about with the Product Owner.

  • Product Owner is just one human being, who is accountable for taking care of the Solution Backlog, raising the price of products and function of the Advancement Crew.

READ  What is Extreme Programming(XP) Practice?


The Scrum Team

The group transforms product Backlog into augmentations of conceivably shippable working programming at each sprint. The group is organized, self sorted out and deals with its own work. The group has the accompanying qualities-

  • Group size preferably ought to associate with 7 people.

  • The group is prescribed to be cross-functional with abilities in the investigation, development, testing, interface structure, database plan, engineering, documentation.

  • It is self sorted out and chooses what to submit and how best to achieve that commitment dedicatedly.

  • The responsibility of the work product belongs to the group in general.

The Scrum Master

The scrum master is in charge of guaranteeing that the scrum group adheres to scrum esteems, practices and standards. Duties of the Scrum Master-

  • Helps the scrum group to adopt Scrum.

  • Helps the group to learn and apply scrum to accomplish the ideal goal of the project.

  • Does not guide individuals on dole out errands, yet encourages the procedure by supporting the group to sort out and oversee yourself.

  • Serves the group, shields them from outside impedance, teaches and guides Product Owner and group being used of the scrum.

  • Facilitate scrum occasions and coaches the group to be cross-functional.

  • Removes hindrances for the group’s progress.

Strikingly, a Scrum Master can’t be the Product owner, director of the group or the task manager.

Scrum Events

Scrum Being time-boxed occasion, scrum occasions guarantees that there is no wastage of time in the execution of the project.

The events are-

  • Release planning meeting

  • Sprint planning

  • Daily scrum

  • Sprint review

  • Sprint retrospective

Release Planning Meeting

The goal of the release planning meeting is to set up an arrangement and objectives which the scrum group and the remainder of the association can comprehend, communicate and deal with. The procedures of Release Planning Meeting are:

  • Turn the vision into a fruitful project in the most ideal manner.

  • Meet or surpass the ideal consumer satisfaction and return on Investment (ROI).

READ  What is Integration Testing?

The release plan builds up the objective of the release, high priority product backlog, and real dangers and overall highlights and functionalities that the release will contain. The plausible delivery date is settled upon. The stakeholders can check the progress and make changes to the release plan on a sprint by sprint manner.

Sprint Planning

Sprint planning keeps tracking the work to be performed in a sprint. This arrangement is made by the collaborative work of the whole scrum group. The sprint planning is having two sections however both are time-boxed.

  • Section 1-group plans what will be delivered as a feature of the sprint.

  • Section 2-group designs how to manufacture or code this functionality.

Daily scrum

The everyday scrum meeting is a time-boxed 15 minutes meeting for the group to synchronize with the updates. During the gathering each colleague clarifies the followings:

  • What the individual has achieved since the last gathering?

  • What the individual will do before the next gathering?

  • What are the issues on the way?

It is generally known as the status update of the project towards accomplishing the objective or goals.

The daily scrum meeting encourages the following:

  • Improve collaboration and communication.

  • Identify and remove the obstructions to development.

  • Highlighting and advancing quick decision making.

  • Improving the scrum groups level of project knowledge.

Sprint Review

A Sprint Review meeting is held toward the end of a Sprint. During the sprint review, the scrum group demos what was created in the sprint to the partners and shareholders. The primary goal of this gathering is to get input on the progress made up until now and choose the next activity things. The sprint review meeting incorporates the followings:

  • The product owner distinguishes what has been done and what should be finished.

  • The team exhibits the work has been done and settle all inquiries.

  • Product Owner talks about the product backlog, the way things are aka status of the backlog items.

  • The whole team talks about what to do next.

The Sprint Review meeting gives important contributions to consequent sprint planning meetings.

Sprint Retrospective

Sprint Retrospective happens after the sprint review and Prior to the next sprint planning meeting. The targets of the sprint retrospective meeting are as per the following-

  • Inspect the last sprint as for individuals, relationship procedures and instruments or tools.

  • Discuss what went well during the sprint, what issues were confronted and how they were settled.

  • Identify and organize the significant items that went well and those could have been done another way. These incorporate the scrum group piece, their incorporation, meeting game plans, devices, the meaning of Done and strategies for Communications.

  • Make a plan for actualizing the upgrades to the manner in which the scrum group works.

Principles of SCRUM

1. Values

Scrum aims to instill certain values in teams:  


  • Courage

  • Focus

  • Commitment

  • Respect

  • Openness 


This framework advocates the inculcating of personal responsibility is each developer and the encouragement of co-operation and a friendly working environment.

Collegial thinking helps to control all the critical points of the complicated software development process and to contemplate lots of blockers. Team synergy leads to a significant increase in efficiency. And mutual responsibility of the Scrum team motivates them to achieve valuable results for business in spite of all difficulties.

2. In Short ...

  • Scrum is used to implement AGILE

  • Fosters a cross-functional self organizing team

  • Innovative and creative design and execution

  • Any issues or challenges are addressed by entire team

  • Philosophy based on Empirical Process Control 

  • Key focus is delivering Maximum business value

  • Working software is NOT considered as a fundamental measure of progress

  • Daily stand up meetings defines the responsibilities of various SCRUM roles

Note: You can also understand Scrum is one of the types of agile methodology. Rather often, software testing company performs sprint checking during agile development. In this case, functional testing, performance checking, unit testing, and other checking types will be fulfilled a little bit differently.

The specialists which execute software testing or web testing should perform all tasks accurately and quickly. Also, it is important to maintain continuous and established communication inside all project team. The testers often interact with the developers during agile development. 

The best practices of SCRUM are (i.e. ):

  • Control over the empirical process. Transparency, checking, and adaptation underlie the whole Scrum methodology.

  • Self-organization. This principle increases the level of independence of the whole team and also checking performance. It is an innovative and creative environment which is conducive to growth.

  • Collaboration. Awareness, clarity, and distribution/appropriation are the main factors of the established work, that means a shared value-creation process with teams working together to offer the highest value.

  • Value-based prioritization. Scrum methodology is focused on attaining all business tasks from the very beginning of the development process.

  • Time-boxing. Time is always a limited resource, thus it should be rationally utilized.  An important element of time-boxed elements in the development management process or Scrum methodology, includes sprints, daily meetings, meetings on sprint planning, review meetings and etc.

  • Iterative development. This principle emphasizes how to manage changes better and build products which satisfy customer needs. It also defines the organization's responsibilities regarding iterative development. The process itself is divided into certain steps each of which requires a certain amount of work and, finally, satisfy user needs and conduct all set business tasks.

The Four (4) Values of AGILE 

  1. Individuals and interactions over process and tools : Process and tools by their very nature are less responsive to change and customer needs.

  2. Working software over comprehensive documentation: AGILE is about streamlining, not eliminating documentation.

  3. Customer/stakeholder collaboration over contract negotiation: AGILE includes users/stakeholders throughout life cycle of a project and values their feedback.

  4. Responding to changes over following a plan: AGILE works in short iterations called sprints because their brevity embraces and utilizes change for the good or better.

3. Understand AGILE versus SCRUM

Agile is a development methodology based on iterative and incremental approach.

Agile software development has been widely seen as highly suited to environments which have small but expert project development team

In the Agile process, the leadership plays a vital role.

Compared to Scrum it is a more rigid method. So there is not much room for frequent changes.

Agile involves collaborations and face-to-face interactions between the members of various cross-functional teams.

Agile can require lots of up-front development process and organizational change.

The agile method needs frequent delivery to the end user for their feedback.

In this method, each step of development like requirements, analysis, design, are continually monitored during the life cycle.

Project head takes cares of all the tasks in the agile method.

The Agile method encourages feedback during the process from the end user. In this way, the end product will be more useful.

Deliver and update the software on a regular basis.

Design and execution should be kept simple.

In the Agile method, the priority is always to satisfy the customer by providing continuous delivery of valuable software.

Working software is the most elementary measure of progress.

It is best to have face-to-face communication, and techniques like these should be used to get as close to this goal as possible.

Scrum is one of the application of agile methodology. In which incremental builds are delivered to the customer in every two to three weeks' time.

Scrum is ideally used in the project where the requirement is rapidly changing.

Scrum fosters a self-organizing, cross-functional team.

The biggest advantage of Scrum is its flexibility as it quickly reacts to changes.

In Scrum, collaboration is achieved in daily stand up meeting with a fixed role assigned to scrum master, product owner, and team members.

Not too many changes needed while implementing scrum process.

In the scrum, after each sprint, a build is delivered to the client for their feedback.

A demonstration of the functionality is provided at the end of every sprint. So that regular feedback can be taken before next sprint.

There is no team leader, so the entire team addresses the issues or problems.

Daily sprint meeting is conducted to review and feedback to decide future progress of the project.

When the team is done with the current sprint activities, the next sprint can be planned.

Design and execution can be innovative and experimental.

Empirical Process Control is a core philosophy of Scrum based process.

Working software is not an elementary measure.

Scrum team focus to deliver maximum business value, from beginning early in the project and continuing throughout.

Following are Agile principles:

-Welcome changing requirements, even late in development. Agile processes allow change according to customer's competitive advantage.

-Business people and developers will work daily throughout the project.

-Attention to technical excellence and right design enhances agility


-Agile team, work on to become more effective, for that they adjust its behavior according to the project.

Following are scrum principles:

-Self-organization: This results in healthier shared ownership among the team members. It is also an innovative and creative environment which is conducive to growth.

-Collaboration: Collaboration is another essential principle which focuses collaborative work. 1. awareness 2. articulation, and 3. appropriation. It also considers project management as a shared value-creation process with teams working together to offer the highest value.

-Time-boxing: This principle defines how time is a limiting constraint in Scrum method. An important element of time-boxed elements are Daily Sprint planning and Review Meetings.

-Iterative Development: This principle emphasizes how to manage changes better and build products which satisfy customer needs. It also defines the organization's responsibilities regarding iterative development.