Scrum is an agile framework for managing product development that focuses on iterative delivery of value through collaboration between self-organizing cross-functional teams. Key aspects of Scrum include short "sprints" where work is defined and tracked on a sprint backlog, daily stand-up meetings, sprint planning and review sessions, and emphasizing working software over documentation. The framework defines three roles - Product Owner who prioritizes features, Scrum Master who facilitates the process, and a self-organizing Development Team.
Agile Software Development Workshop at Sote HubSote ICT
Presentation on agile project management by Maros Korinek, developer at Funding Circle, from his 4-day training in December 2016 at Sote Hub in Voi, Kenya.
The aim of agile methods is to reduce overheads in the software process (e.g. by limiting documentation) and to be able to respond quickly to changing requirements without excessive rework.
This presentation is about Scrum methodology. First it reviewed traditional SDM and then talk about Agile and Scrum
Agile Software Development Workshop at Sote HubSote ICT
Presentation on agile project management by Maros Korinek, developer at Funding Circle, from his 4-day training in December 2016 at Sote Hub in Voi, Kenya.
The aim of agile methods is to reduce overheads in the software process (e.g. by limiting documentation) and to be able to respond quickly to changing requirements without excessive rework.
This presentation is about Scrum methodology. First it reviewed traditional SDM and then talk about Agile and Scrum
Check out this brief introduction of Scrum, the Agile Software Development Framework. This is just a high level introduction that is why there are only 10 slides. Please like and share if you find it useful.
Scrum is an iterative and incremental agile software development methodology for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal" as illustrated by Teradata Consultant Prasanna Yaddanapudi in Feb Session
I had to explain Scrum in just 5 slides to the executives. Think of it as an elevator pitch to get them interested and buy the idea. Feel free to use it. Send me any feedback about your experience.
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
EHS Conducted SCRUM Overview Session for a Corporate Company in Lahore covering Basics i.e. What is Agile & Scrum, Why to use Scrum, Benefits, Values, Artifacts, Events, Scrum Teams & Roles...
The Power and Illusion of Self-Organizing TeamsDr. Thomas Juli
Teams and teamwork are the heart and soul of every project. This is especially true for agile teams. It is not the individual performance or accomplishment that counts but that of the team. Just like in team sports the team succeeds and fails together. The Agile Manifesto puts the team at the center of interaction. It states, “The best architectures, requirements, and designs emerge from self-organizing teams.” But what does “self-organizing” mean? Does “self-organizing” mean that team building is no longer necessary and that instead the teams do this by themselves? And, if teams are self-organizing why do so many teams and projects still fail?
NOTE: This is the official handout of my presentation at the PMI Global Congress North America 2012 in Vancouver, BC, Canada (Session AGL14 on October 21, 2012). Please mail your feedback to tj@thomasjuli.com
Check out this brief introduction of Scrum, the Agile Software Development Framework. This is just a high level introduction that is why there are only 10 slides. Please like and share if you find it useful.
Scrum is an iterative and incremental agile software development methodology for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal" as illustrated by Teradata Consultant Prasanna Yaddanapudi in Feb Session
I had to explain Scrum in just 5 slides to the executives. Think of it as an elevator pitch to get them interested and buy the idea. Feel free to use it. Send me any feedback about your experience.
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
EHS Conducted SCRUM Overview Session for a Corporate Company in Lahore covering Basics i.e. What is Agile & Scrum, Why to use Scrum, Benefits, Values, Artifacts, Events, Scrum Teams & Roles...
The Power and Illusion of Self-Organizing TeamsDr. Thomas Juli
Teams and teamwork are the heart and soul of every project. This is especially true for agile teams. It is not the individual performance or accomplishment that counts but that of the team. Just like in team sports the team succeeds and fails together. The Agile Manifesto puts the team at the center of interaction. It states, “The best architectures, requirements, and designs emerge from self-organizing teams.” But what does “self-organizing” mean? Does “self-organizing” mean that team building is no longer necessary and that instead the teams do this by themselves? And, if teams are self-organizing why do so many teams and projects still fail?
NOTE: This is the official handout of my presentation at the PMI Global Congress North America 2012 in Vancouver, BC, Canada (Session AGL14 on October 21, 2012). Please mail your feedback to tj@thomasjuli.com
- Agile values and manifesto
- Scrum in details
- Themes, epics, and user stories
- Combining and splitting user stories.
- What could go wrong in Scrum and why?
- Overview in Other Agile methodologies:
- XP Agile Methodology
- KanBan Agile Methodology.
Agile and Scrum Overview for PMs, Designers and Developers Aaron Roy
This is an overview of the flavor of agile/scrum I had my team use at Bond in Q2 2017. We heavily emphasized the importance of having a shared language between cross-functional teams and this deck was meant as a primer that could be shared between product managers, designers, and developers.
This simple and crisp quick reference card is for Agile and Scrum basics. It is a simple way to glance through all the concepts and use it as a tool for revision, even before an interview.
Detail Information about Agile Process Frameworks such as SCRUM and CMMI along with agile manifesto. Comparison between scrum and capability maturity model integration
Managing a team and project are quite synonymous. Especially, teams require effective distribution of responsibility / roles. Once that is setup, a proper process guides people to make progress. All this fits into a product lifecycle, which is essential to develop the right product, in the right way, and deliver it at the right time.
1. Introduction to Scrum
About Scrum
Key Values
Scrum Framework
Roles
Processes
Artifacts
2. Agile Manifesto
• Individuals and interactions over processes
and tools
• Working software over comprehensive
documentation
• Customer collaboration over contract
negotiation
• Responding to change over following a plan
3. 12 principles
1. Our highest priority is to satisfy the customer
through early and continuous delivery of
valuable software.
2. Welcome changing requirements, even late
in development. Agile processes harness
change for the customer's competitive
advantage.
3. Deliver working software frequently, from a
couple of weeks to a couple of months, with
a preference to the shorter timescale.
4. Business people and developers must work
together daily throughout the project.
4. 12 Princilpes
1. Build projects around motivated individuals. Give
them the environment and support they need, and
trust them to get the job done.
2. The most efficient and effective method of conveying
information to and within a development team is
face-to-face conversation.
3. Working software is the primary measure of progress.
4. Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
5. 12 Principles
• 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.
6. What is Scrum?
o Agile way of Project Management
o A team based- collaborative approach
o Iterative & Incremental development
o Focus to deliver “business value”
7. More about Scrum
• Scrum is an agile process that allows to focus on
delivering the highest business value in the shortest
time.
• It allows to rapidly and repeatedly inspect actual
working software (every two weeks to one month).
• The business sets the priorities. Teams self-organize
to determine the best way to deliver the highest
priority features.
• Every two weeks to a month anyone can see real
working software and decide to release it as is or
continue to enhance it for another sprint.
8. Key Values
oSimplicity is Essential (the power
of less)
oSelf-organizing teams
oCommunication is the key
oDeliver Frequently
11. Product Owner
o Define the features of the product
o Decide on release date and content
o Be responsible for the profitability of the
product (ROI)
o Prioritize features according to market value
o Adjust features and priority every iteration, as
needed
o Accept or reject work results
12. Project Manager ( Scrum Master)
o Represents management to the project
o Responsible for enacting Scrum values and
practices
o Removes impediments
o Ensure that the team is fully functional and
productive
o Enable close cooperation across all roles and
functions
o Shield the team from external interferences
13. The Team
• Typically 3-9 people
• Cross-functional:
• Programmers, testers, user experience
designers, etc.
• Members should be full-time
• May be exceptions (e.g., database administrator)
15. Sprint planning
o Team selects items from the product
backlog they can commit to completing
o Sprint backlog is created
o Tasks are identified and each is
estimated (1-16 hours)
o Collaboratively, not done alone by the
PM
o High-level design is considered
16. Print Retrospectives
o Periodically take a look at what is and is not
working
o Typically 15–30 minutes
o Done after every sprint
o Whole team participates
o Project Manager
o Product owner
o Team
o Possibly customers and others
17. The Daily Scrum
o Parameters
o Daily
o 15-minutes
o Stand-up
o Not for problem solving
o Whole world is invited
o Only team members, project manager, product
owner, can talk
o Helps avoid other unnecessary meetings
18. The Sprint Review
o Team presents what it accomplished during the
sprint
o Typically takes the form of a demo of new
features or underlying architecture
o Informal
o 2-hour prep time rule
o No slides
o Whole team participates
o Invite the world
20. Product Backlog
o The requirements
o A list of all desired work on the project
o Ideally expressed such that each item has
value to the users or customers of the
product
o Prioritized by the product owner
o Reprioritized at the start of each sprint