Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
The Professional Scrum Master Guide

You're reading from   The Professional Scrum Master Guide The unofficial guide to Scrum with real-world projects

Arrow left icon
Product type Paperback
Published in Jul 2021
Publisher Packt
ISBN-13 9781800205567
Length 174 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Fred Heath Fred Heath
Author Profile Icon Fred Heath
Fred Heath
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Section 1:The Scrum Framework
2. Chapter 1: Introduction to Scrum FREE CHAPTER 3. Chapter 2: Scrum Theory and Principles 4. Chapter 3: The Scrum Team 5. Chapter 4: Scrum Events 6. Chapter 5: Scrum Artifacts 7. Section 2:Scrum in Action
8. Chapter 6: Planning and Estimating with Scrum 9. Chapter 7: The Sprint Journey 10. Chapter 8: Facets of Scrum 11. Section 3:The PSM Certification
12. Chapter 9: Preparing for the PSM I Assessment 13. Assessments 14. Other Books You May Enjoy 15. Index

Identifying a Scrum Team

The Scrum Team is a small group of people who work together to deliver a software solution or product to a client. The Scrum Team consists of three specific roles, a Product Owner, a Scrum Master, and Developers. The Scrum Team is a cohesive unit of professionals focused on delivering a product. The team is responsible for performing any and all product-related activities needed in order to achieve the Product Goal. They are empowered by the organization to manage their own work.

Scrum Teams differ from traditional software teams. Before Agile became a thing, software project teams would consist of a number of software developers working within well-defined boundaries and within a strict hierarchy of duties and responsibilities. Traditionally, business analysts would communicate with the stakeholder and capture requirements. These would then be passed to the developers. The software system's architecture and high-level design would be established in...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime