The document discusses Agile software development methodology, specifically Scrum. It defines Scrum as an iterative framework used to develop complex products through short cycles of work called sprints. The Scrum team consists of a product owner, Scrum master, and development team who work collaboratively through daily stand-up meetings, sprint planning, reviews, and retrospectives to deliver working software incrementally in each sprint. The document outlines the Scrum roles and process including product backlogs, sprint backlogs, and burndown charts. It also addresses some common misconceptions and challenges of the Scrum framework.
This presentations answers the question of why your company needs to work agile .
to be able to cope with changing markets and grow through organizational learning to explore new markets
TFS2010: Nuts and Bolts of Visual Studio Scrum v1.0 Template
Visual Studio and Team Foundation Server (TFS) are the cornerstones of development on the Microsoft .NET platform. These tools represent some of the best opportunities for success and to experience a focused and smooth software development process. For TFS 2010 Microsoft heavily invested in Scrum and is moving some internal product teams onto the approach.
This session is not about Scrum in depth, (for that please visit scrum.org) but rather, we will cover the lifecycle of creating work items and how this fits into Scrum using Visual Studio ALM and Team Foundation Server. We will cover in detail:
* How to successfully gather requirements
* How to plan a project using TFS 2010 and Scrum
* How to work with a product backlog in TFS 2010
* The right way to plan a sprint with TFS 2010
* Tracking your progress
* The right way to use work items
* Leveraging built-in reporting and Project portals available on the SharePoint dashboard
* Reports targeted to the Product Owner / Project Manager
You will walk away knowing how to interpret and understand a project health and progress. Visual Studio ALM is designed to address many of the problems faced by teams using traditional approaches. It does
so by providing a set of integrated tools to help teams improve their software development activities and to help management better support the software development processes.
Covers SCRUM Artifacts topic in detail along with necessary linked topics understanding.
Below are SCRUM Artifacts covered in this presentation:
Product Backlog
Sprint Backlog
Increment / Product Increment
This presentations answers the question of why your company needs to work agile .
to be able to cope with changing markets and grow through organizational learning to explore new markets
TFS2010: Nuts and Bolts of Visual Studio Scrum v1.0 Template
Visual Studio and Team Foundation Server (TFS) are the cornerstones of development on the Microsoft .NET platform. These tools represent some of the best opportunities for success and to experience a focused and smooth software development process. For TFS 2010 Microsoft heavily invested in Scrum and is moving some internal product teams onto the approach.
This session is not about Scrum in depth, (for that please visit scrum.org) but rather, we will cover the lifecycle of creating work items and how this fits into Scrum using Visual Studio ALM and Team Foundation Server. We will cover in detail:
* How to successfully gather requirements
* How to plan a project using TFS 2010 and Scrum
* How to work with a product backlog in TFS 2010
* The right way to plan a sprint with TFS 2010
* Tracking your progress
* The right way to use work items
* Leveraging built-in reporting and Project portals available on the SharePoint dashboard
* Reports targeted to the Product Owner / Project Manager
You will walk away knowing how to interpret and understand a project health and progress. Visual Studio ALM is designed to address many of the problems faced by teams using traditional approaches. It does
so by providing a set of integrated tools to help teams improve their software development activities and to help management better support the software development processes.
Covers SCRUM Artifacts topic in detail along with necessary linked topics understanding.
Below are SCRUM Artifacts covered in this presentation:
Product Backlog
Sprint Backlog
Increment / Product Increment
Companies face challenges in usage of Scrum such as geographically distributed teams, different time zones, getting clients on board and we will take a look at some of them in this session.
In this presentation, we summarize the most important content of the Scrum Guide.
The material can be used to share knowledge and have a common understanding among Scrum Team Members.
It is also a great summary for those preparing for the Professional Scrum Master I (PSM I) test
this is my experience in Agile Scrum and materials collected over a period of time from various experts, credits goes to all who has directly and indirectly contributed
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018
This power point presentation is an introduction to Scrum and covers the following topics:
* Problems with a traditional approach
* What is Scrum?
* Why use Scrum?
* How does Scrum work?
* The Product Owner
* The Scrum Master
* The Team
* The Product Backlog
* Benefits of using a Product Backlog
* The Sprint Backlog
* The Scrum Cycle
* The Burn Down Chart
You can copy, distribute, and use the content of the presentation in accordance to Creative Commons Attribution 2.5 License.
Companies face challenges in usage of Scrum such as geographically distributed teams, different time zones, getting clients on board and we will take a look at some of them in this session.
In this presentation, we summarize the most important content of the Scrum Guide.
The material can be used to share knowledge and have a common understanding among Scrum Team Members.
It is also a great summary for those preparing for the Professional Scrum Master I (PSM I) test
this is my experience in Agile Scrum and materials collected over a period of time from various experts, credits goes to all who has directly and indirectly contributed
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018
This power point presentation is an introduction to Scrum and covers the following topics:
* Problems with a traditional approach
* What is Scrum?
* Why use Scrum?
* How does Scrum work?
* The Product Owner
* The Scrum Master
* The Team
* The Product Backlog
* Benefits of using a Product Backlog
* The Sprint Backlog
* The Scrum Cycle
* The Burn Down Chart
You can copy, distribute, and use the content of the presentation in accordance to Creative Commons Attribution 2.5 License.
Pastor Elio Marrocco's "Serving God By Serving Others" sermon at New Life Christian Church in November 2012. You can learn more about New Life Christian Church here: http://www.newlifecc.ca
50 Customer Service Quotes You Need to Hang In Your OfficeDesk
Customer service is tough in any industry. However, companies and organizations that produce incredible service to every customer have a clear competitive advantage. To remind you of the amazing opportunities that powerful customer service holds, here is a compilation of insightful words of wisdom from the best in the business.
Curious about Desk.com? Download this free kit to get started: http://bit.ly/FreeCustomerServiceKit
An introduction to the SCRUM Project Management Methodology. It is text-heavy so that it can be self-contained and serve both as an introduction and reference manual to SCRUM.
Introduction Professional Scrum Developer for JavaJoris De Winne
Introduction to the official PSD for Java training from scrum.org. It doesn't cover all topics from the official curriculum, and serves as a intro and teaser to actually follow the official training.
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
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.
1. Agile Process
In software development, we mean
“Agile Software Development
with scrum methodology”
Connie Dmochowsky
5/20/2013 1
2. Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
• Individuals and interactions over processes and
tools
• Working software over comprehensive
documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
5/20/2013 2
3. The goals of Agile
• Rapid product development
• On time delivery
• Excellent quality end products
• Customer satisfaction
• Team achievement
• Cost effective product development
• Quick adaption to business changes
5/20/2013 3
4. What is Scrum Methodology
• Scrum has been a framework for developing and
sustaining complex products since early 1990s.
• Developed and sustained by Ken Schwaber and
Jeff Sutherland.
• We can address complex adaptive
problems, while productively and creatively
delivering products of the highest possible value.
• Scrum is:
– Lightweight
– Simple to understand
– Extremely difficult to master
5/20/2013 4
5. Scrum process is based on
Iterative processes
Adaption - Empirical process control
Transparency
Inspection - Frequent review processes
Collaboration
Cooperation
Commitment to Team goal
Small team – 3 to 7 team members
Time boxed approach
5/20/2013 5
6. Misconception of Scrum Process
• No requirement documents
• No technical design documents
• No QA testing
• No processes
• No end date
• No management reporting
• No scope management
• No control
5/20/2013 6
10. Scrum Framework
Preparation Phase
Create User Stories – Written from user perspective
“As a sales clerk, I need to be able to enter a sales order”.
Step 1 – 1 day planning session
• 2-4 hour release planning per release
– Team, Scrum master & product owner discuss project requirements
– Assign story points to user story
– Team prioritize user stories identified for the release and group them
into sprints
• 2-4 hours sprint planning per sprint
– Poetize user stories selected for the sprint
– Team defines detailed tasks for each story
– Team selects tasks for each sprint
– Team members assign tasks to themselves
5/20/2013 10
11. Scrum Framework
Step 2 - Team works on the current sprint - 2 Weeks
• Daily 15 min. stand-up meeting – Team, Scrum Master, Product Owner
– What has been completed – competed work per each day
– What to do today
– What prevents each member from completing one’s work
Step 3 - Sprint review at the end of each sprint - 1 to 2 hours
• Provide a review session to discuss what has been completed with
team members, scrum master, product owner & steakholders
• Decide what would be considered completed within the current sprint
• Decide what needs to be moved into next sprint
5/20/2013 11
12. Scrum Framework
Step 4 - Retrospective after Sprint review - 1 hour
• What worked
• What needs to be different
Step 5 - Start on next sprint
** Do this iterative process to complete release
5/20/2013 12
13. Scrum Master –Responsibilities
• Services to Product Owner
– Effective Product Backlog management
– Clearly communicating vision, goals, and Product Backlog
items to the Development Team
– Teaching the Scrum Team to create clear and concise
Product Backlog items
– Understanding long-term product planning in an empirical
environment
– Understanding and practicing agility
– Facilitating Scrum events as requested or needed.
5/20/2013 13
14. Scrum Master –Responsibilities
• Services to Team Members
– Remove any impediments that prevents the team from
achieving the team goals
– Increase teams' productivity by keeping away things that
distract current sprint
– Monitor advancements of the team
– Monitor progress along the Sprint and report to
management (Burn chart)
– Monitor ideas & quality
– Facilitate teams’ discussion – Hold daily meeting
5/20/2013 14
15. Product Owner – Responsibilities
• Provide business knowledge
• Communicate the goals and progress of project to all
stakeholders in a timely manner
• Review sprints results with team members
• Provide feedback for each sprint
• Do not disturb sprint
• Be available for all planning & review meetings
• Promote/advertize project goals
• Plan how to deliver end product to users
5/20/2013 15
16. Team member – Responsibilities
• Self-organizing Scrum Team – Heart of scrum
• Main job - Build product to deliver business value
• Needs to be cross-functional
• All members must be:
– Accountable
– Collaborative
– Trusting
– Committed & reliable
– Creative & innovative
• Be trusting, committed, creative, innovative, responsible, reliable,
business-value
5/20/2013 16
17. Scrum Challenges
• The fact that we are so used to the traditional
project management
• High level of motivation is needed to signing
up for work and reporting daily about
accomplishments
• Daily scrum meetings – Remember small
accomplishments and small goals
• Organizational obstacles become visible
quickly
5/20/2013 17
18. Scrum Challenges
• BAS & QA take part in the project on an going
basis and are really responsible for the
outcome of the project.
• Scrum is empirical.
– The team adapts to new situation
– The team has to adapt the process itself.
• Every team is allowed to change the time of a meeting,
however they are not allowed to skip a meeting
whatsoever.
5/20/2013 18
19. Product backlog and sprint planning
Sprint 1 Sprint 2 Sprint 3
290 190 80
Story 1 30 0
Story 2 50 0
Story 3 20 0
Story 4 10 10
Sprint 1
Story 5 20 20
Story 6 10 10
Story 7 30 30
Story 8 30 30
Story 9 20 20 10
Sprint 2
Story 10 40 40 40
Story 11 30 30 30
Release 1
5/20/2013 19