Scrum is an efficient framework within which you can develop software with teamwork. It is based on agile principles.
This presentation will help you understand agile development in general and Scrum in specific. You will get familiar with its associated terminology along with appropriate examples.
Join BostonPHP and Michael Bourque as he presents the concept of Scrum and shows why so many people are now deploying scrum to their development projects. Michael will take us through the process and talk about how his company, Parametric Technology Inc. (PTC) , is successfully applying Scrum.
[To download this complete presentation, visit: https://www.oeconsulting.com.sg/training-presentations]
This introduction to Agile and Scrum is a presentation that provides a high-level overview of Agile and Scrum methodologies. The presentation is aimed at individuals who may have heard of Agile and Scrum but are not familiar with the concepts or principles.
The presentation begins with an introduction of the basic principles and values of Agile and Scrum, which includes an explanation of the Agile philosophy and principles, and an overview of the Scrum framework and its origins. It also discusses the benefits and drawbacks of Agile and Scrum and compares them to traditional project management methodologies.
The key roles and responsibilities within a Scrum team are discussed next, including the three key roles of Scrum Master, Product Owner, and Development Team. An explanation on how these roles interact with each other and the wider organization is provided.
The Scrum framework and its key components, including an overview of Sprints, Backlog, and Artifacts are also explained. The Scrum events, including Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective, are also covered.
Lastly, successful examples of how Agile and Scrum are used in various industries, such as software development, marketing, and education are presented. Discussions on how Agile and Scrum can be adapted to fit the needs of different projects and organizations are also provided.
By the end of the Agile and Scrum PPT presentation, attendees would have a solid foundation in Agile and Scrum methodologies, including a basic understanding of the principles and values, the Scrum framework and its key components, and the roles and responsibilities of the Scrum team. They would be equipped with the necessary knowledge to apply Agile and Scrum to their own work.
LEARNING OBJECTIVES
1. Understand the basic principles, values, benefits and drawbacks of Agile and Scrum.
2. Understand the key roles of the Scrum team, and the Scrum framework and its key components.
3. Understand how Agile and Scrum can be applied to various industries and projects and adapted to fit different situations.
Join BostonPHP and Michael Bourque as he presents the concept of Scrum and shows why so many people are now deploying scrum to their development projects. Michael will take us through the process and talk about how his company, Parametric Technology Inc. (PTC) , is successfully applying Scrum.
[To download this complete presentation, visit: https://www.oeconsulting.com.sg/training-presentations]
This introduction to Agile and Scrum is a presentation that provides a high-level overview of Agile and Scrum methodologies. The presentation is aimed at individuals who may have heard of Agile and Scrum but are not familiar with the concepts or principles.
The presentation begins with an introduction of the basic principles and values of Agile and Scrum, which includes an explanation of the Agile philosophy and principles, and an overview of the Scrum framework and its origins. It also discusses the benefits and drawbacks of Agile and Scrum and compares them to traditional project management methodologies.
The key roles and responsibilities within a Scrum team are discussed next, including the three key roles of Scrum Master, Product Owner, and Development Team. An explanation on how these roles interact with each other and the wider organization is provided.
The Scrum framework and its key components, including an overview of Sprints, Backlog, and Artifacts are also explained. The Scrum events, including Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective, are also covered.
Lastly, successful examples of how Agile and Scrum are used in various industries, such as software development, marketing, and education are presented. Discussions on how Agile and Scrum can be adapted to fit the needs of different projects and organizations are also provided.
By the end of the Agile and Scrum PPT presentation, attendees would have a solid foundation in Agile and Scrum methodologies, including a basic understanding of the principles and values, the Scrum framework and its key components, and the roles and responsibilities of the Scrum team. They would be equipped with the necessary knowledge to apply Agile and Scrum to their own work.
LEARNING OBJECTIVES
1. Understand the basic principles, values, benefits and drawbacks of Agile and Scrum.
2. Understand the key roles of the Scrum team, and the Scrum framework and its key components.
3. Understand how Agile and Scrum can be applied to various industries and projects and adapted to fit different situations.
Contains a quick review of the Scrum process, talks about the dangers of trying to map PMBOK to Scrum, and then tries to talk about the concepts behind managing an Agile project using Scrum.
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
This deck gives an overview on the following key areas.
1) Agile Development Principle
2) Scrum Framework
3) User Story Creation
4) Definition of Done
5) Agile – Retrospective
6) Development – Metrics
7) Agile vs Traditional Development Approach
Contains a quick review of the Scrum process, talks about the dangers of trying to map PMBOK to Scrum, and then tries to talk about the concepts behind managing an Agile project using Scrum.
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
This deck gives an overview on the following key areas.
1) Agile Development Principle
2) Scrum Framework
3) User Story Creation
4) Definition of Done
5) Agile – Retrospective
6) Development – Metrics
7) Agile vs Traditional Development Approach
Agile , SCRUM
Introduction
What is Agile Methodology?
What is Scrum?
History of Scrum
Functionality of Scrum
Components of Scrum
Scrum Roles
The Process
Scrum Artifacts
Scaling Scrum
Q & A Session
Agile is a software development methodology in which the development is carried out iteratively and the requirements evolve through continuous inspection and adaptation. Some of the most commonly used agile software development methods/frameworks are: Adaptive Software Development (ASD), Extreme Programming (XP), Scrum and Kanban.
Engineering Talent Development Thru ProjectsRoy Mark
A method of ientifying and developing senior and/or junior engineers and managers through the completion of compressed projects using the SCRUM methodology
Scrum Overview for Agile Software Development. ... Scrum is a project management framework that is applicable to any project with aggressive deadlines, complex requirements and a degree of uniqueness. In Scrum, projects move forward via a series of iterations called sprints. Each sprint is typically two to four weeks long.
Lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems, Scrum Theory, Scrum Pillars, Scrum values, Scrum teams, Scrum Master, Scrum Events, the Sprint, Sprint planning, daily Scrum
Product Owner in Agile/Scrum is the single person responsible for maximizing the return on investment (ROI) of the development effort
Responsible for product vision
Constantly re-prioritizes the Product Backlog, adjusting any long-term expectations such as release plans
Final arbiter of requirements questions
Decides whether to release
Decides whether to continue the development
Considers stakeholder interests
May contribute as a team member
Has a leadership role
Must be available to the Team at any time
What Is Servant Leadership?
Characteristics of Servant Leadership
Myths Of Servant Leadership
Best Servant Leaders
Benefits of Servant Leadership
Do's and Don'ts of Being a Servant Leader
Servant Leadership at the Workplace
The servant-leader is servant first and then conscious choice brings one to aspire to lead.
Servant leaders involve others in decision-making that enhances the growth of people while improving the quality of organizational life.
Servant leaders ensure that their team’s needs are met while they focus on helping individuals make better decisions and be more innovative.
Servant leadership is not about gaining–it is about giving and serving.
Characteristics of Servant Leadership
Valuing People
Humility: People First
Listening
Empathy
Stewardship
Trust & Caring
Persuasion
Building Community
Myths Of Servant Leadership
1) Servant leadership means giving up power to employees.
Servant leadership is about sharing power and decision-making with employees to enable the business to be successful.
Servant leadership doesn’t mean that employees can do whatever they want, or that every decision within the organization is made by consensus.
2) A servant leader is abdicating responsibility for success.
Servant leader understands that they are ultimately responsible for the success of their employees and the success of their business.
Sometimes decisions need to be made that only the leader can make; the tough calls that might be unpopular.
#Leadership
#ServantLeadership
#ServantLeaders
#Agile
#Scrum
#DecisionMaking
#Empathy
#Persuasion
#projectmanagement
#OrganizationalLife
#Innovation
#Growth
#ManoharPrasad
#AgileCoaching
#ServantLeader
#organization
#ResponsibilityForSuccess
#BusinessSuccess
#PopularDecision
Agile Retrospective by Manohar Prasad
Topics which are covered -
Agile Manifesto
Agile Principles
Scrum Values
What is Retrospective
Why Retrospectives
How to perform Retrospectives
Best Retrospective Practices
Best Retrospective Methods
“Scrum Master” & “Agile Project Manager”: A Tale of Two Different Roles by Manohar Prasad, CSP®-SM, CSP®-PO, CSM®, CSPO®, PSM I®, Agile Coach
“The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules.”
“The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren’t. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.”
Agile in sales takes sales management strategies from the Agile world. One such framework is called the Scrum. The Scrum components include sprints, sprint planning, daily stand-ups, sprint review, sprint retrospective and constant iteration and applies all of them to selling. This methodology helps sales teams be more flexible, cross-functional, and effective which ultimately increases the sales.
SDLC is the acronym of Software Development Life Cycle. It is also called as Software development process. The software development life cycle (SDLC) is a framework defining tasks performed at each step in the software development process.
What do you mean by Requirements?
A requirement is:
A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract , standard, specification, or other formally imposed documents.
A documented representation of a condition or capability as mentioned above.
Identify the key components of e-commerce business models.
A successful business model effectively addresses eight key elements:
●Value proposition - how a company's product or service fulfills the needs of customers. Typical e-commerce value propositions include personalization, customization, convenience, and reduction of product search and price delivery costs.
●Revenue model -- how the company plans to make money from its operations. Major e-commerce revenue models include the advertising model, subscription model, transaction fee model, sales model, and affiliate model.
●Market opportunity -- the revenue potential within a company's intended marketspace.
●Competitive environment-the direct and indirect competitors doing business in the same marketspace, including how many there are and how profitable they are.
●Competitive advantage - the factors that differentiate the business from its competition, enabling it to provide a superior product at a lower cost.
●Market strategy -- the plan a company develops that outlines how it will enter a market and attract customers.
●Organizational development - the process of defining all the functions within a business and the skills necessary to perform each job, as well as the process of recruiting and hiring strong employees.
●Management team - the group of individuals retained to guide the company's growth and expansion.
Training & development evaluation is a continual and systematic process of assessing the value or potential value of a training program, course, activity or event. Results of the evaluation are used to guide decision-making around various components of the training (e.g. delivery, results) and its overall continuation, modification, or elimination.
Search engine optimization is a methodology of strategies, techniques and tactics used to increase the visitors to a website by obtaining a high-ranking placement in the search results page of a search engine -- including Google, Bing, Yahoo and other search engines. SEO helps to ensure that a site is accessible to a search engine and improves the chances that the site will be found by the search engine.
Digital Marketing is an alternative terms for online marketing or e-marketing. There is no difference between online marketing and digital marketing but a few experts also make a few difference between both type marketing as they have said that digital marketing bears of virtual products but online marketing carries virtual and physical products. Business and marketing has been redirected to online presence either physical or digital products because World Wide Web has become common household name around the globe. Normally customers and clients check their needs online either physical products or digital products.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
3. Manifesto for Agile Software Development
Individuals and interactions over processes
and tools
Working software over comprehensive
documentation
Customer collaboration over contract
negotiation
Responding to change over following a plan
4. Principles of Agile Manifesto
Our highest priority is to satisfy the customer
through early and continuous delivery of valuable
software.
Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
Deliver working software frequently, from a couple
of weeks to a couple of months, with a preference
to the shorter timescale.
Business people and developers must work together
daily throughout the project.
5. Principles of Agile Manifesto
Build projects around motivated individuals. Give them the
environment and support they need, and trust them to get the
job done.
The most efficient and effective method of conveying
information to and within a development team is face-to-face
conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
6. Principles of Agile Manifesto
Continuous attention to technical excellence
and good design enhances agility.
Simplicity-the art of maximizing the amount
of work not done-is essential.
The best architectures, requirements, and designs
emerge from self-organizing teams.
At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts its
behavior accordingly.
8. What is Scrum?Scrum
Scrum:
Is an agile, lightweight process
Can manage and control software and product
development
Uses iterative, incremental practices
Has a simple implementation
Increases productivity
Reduces time to benefits
Embraces adaptive, empirical systems development
Is not restricted to software development projects.
13. Product Backlog
Ever changing
Prioritized list
Owned by product owner
Spread sheet example
14. Sprint Backlog
Consists of selected PBIs negotiated between the
team and the Product Owner during the Sprint
Planning Meeting.
No changes are made during the Sprint that would
endanger the Sprint Goal.
Initial tasks are identified by the team during Sprint
Planning Meeting.
Team will discover additional tasks needed to meet
the Sprint Goal during Sprint execution
Visible to the team.
Referenced during the Daily Scrum Meeting
16. Product Increment
The Increment is the sum of all the Product Backlog
items completed during a Sprint and the value of the
increments of all previous Sprints. At the end of a
Sprint, the new Increment must be "Done," which
means it must be in useable condition and meet the
Scrum Team's definition of "Done".
The product capabilities completed during the
Sprints.
Brought to a usable, releasable state by the end of
each Sprint.
Released as often as the Product Owner wishes.
Inspected during every Sprint Review Meeting.
20. Sprint Planning Meeting
Stake-holders to refine and re-prioritize the Product
Backlog and Release Backlog and to choose the
goals for the next iteration, usually droved by the
highest business value and risk
Scrum team and Product Owner meet to consider
how to achieve the requests, and to create a sprint
backlog of tasks to meet the goals
21. Daily Standup Meeting
Three things to talk in 15 minutes
What did I accomplish yesterday?
What will I do today?
What obstacles are impeding my progress?
Why standup meeting?
Promote individual’s commitment to the team
Promote close working relationship
Identify issues in timely fashion
22. Sprint Review Meeting
During the sprint review, the project is assessed
against the sprint goal determined during the sprint
planning meeting. Ideally, the team has completed
each product backlog item brought into the sprint,
but it's more important that they achieve the overall
goal of the sprint.
Sprint review typically include the product owner,
the ScrumMaster, development team, and the
product sponsors or stakeholders.
23. Sprint Retrospective Meeting
The sprint retrospective is usually the last thing
done in a sprint.
The entire team, including both the ScrumMaster
and the product owner should participate.
The sprint retrospective is of 3 hours duration for a
four week sprint.
The sprint retrospective is a meeting facilitated by
the ScrumMaster at which the team discusses the
just-concluded sprint and determines what could be
changed that might make the next sprint more
productive.
24. Roles of Scrum Master
Works with the organization to make Scrum possible
Ensures Scrum is understood and enacted
Creates an environment conducive to team self-
organization
Shields the team from external interference and
distractions to keep it in group flow
Promotes improved engineering practices
Helps resolve impediments
Has a leadership role
Has no management authority over the team
26. Roles of Product Owner
Single person responsible for maximizing the return
on investment (ROI) of the development effort
Responsible for product vision
Constantly re-prioritizes the Product Backlog,
adjusting any long-term expectations such as release
plans
Final arbiter of requirements questions
Decides whether to release
Decides whether to continue development
Considers stakeholder interests
May contribute as a team member
Has a leadership role
27. Roles of Development Team
Cross-functional (e.g., includes members with testing skills, and
others not traditionally called developers: business analysts, designers,
domain experts, etc.)
Self-organizing / self-managing, without externally assigned roles
Plans one Sprint at a time with the Product Owner
Has autonomy regarding how to develop the increment
Intensely collaborative
Most successful when located in one team room, particularly for the
first few Sprints
Most successful with long-term, full-time membership. Scrum moves
work to a flexible learning team and avoids moving people or splitting
them between teams.
6 ± 3 members
Has a leadership role
28. Sprint Burndown Chart
Summation of total team work remaining within one Sprint.
It is updated daily.
May go up before going down.
Intended to facilitate team self-organization.
Fancy variations, such as itemizing by point person or adding
trend lines, tend to reduce effectiveness at encouraging
collaboration.
Seemed like a good idea in the early days of Scrum, but in
practice has often been misused as a management report,
inviting intervention. The Scrum Master should discontinue use
of this chart if it becomes an impediment to team self-
organization.
30. Scalability
Typical individual team is 7 ± 2 people
Scalability comes from teams of teams
Factors in scaling
Type of application
Team size
Team dispersion
Project duration
Scrum has been used on multiple 500+ person
projects
31. User Stories
Instead of Use Cases, Agile project owners do "user stories"
Who (user role) – Is this a customer, employee, admin,
etc.?
What (goal) – What functionality must be
achieved/developed?
Why (reason) – Why does user want to accomplish this
goal?
As a [user role], I want to [goal], so I can [reason].
Example:
"As a user, I want to log in, so I can access subscriber
content.”