Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
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 Mini Book of Agile

You're reading from   The Mini Book of Agile Everything you really need to know about Agile, Agile Project Management and Agile Delivery

Arrow left icon
Product type Paperback
Published in Mar 2022
Publisher Packt
ISBN-13 9781803238715
Length 50 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
YESI EDUCATION YESI EDUCATION
Author Profile Icon YESI EDUCATION
YESI EDUCATION
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

1. Chaper 1: Introduction
2. Chapter 2: What is Agile? FREE CHAPTER
3. Chapter 3: Why go Agile?
4. Chapter 4: How it all began
5. Chapter 5: The Different Agile Methodologies
6. Chapter 6: Agile Principles
7. Chapter 7: The Agile Culture
8. Chapter 8: Agile Roles
9. Chapter 9: Agile Concepts
10. Chapter 10: Agile Artifacts
11. Chapter 11: Agile Rituals
12. Chapter 12: Agile Tools
13. Chapter 13: Agile vs. Waterfall
14. Chapter 14: Agile FAQs
15. Chapter 15: Agile Myths
16. Chapter 16: The Agile Knowledge Base | AgileKB.com

Chapter 8: Agile Roles

In Agile there are a few distinct roles which are different to traditional roles. But traditional roles still exist, and people in those roles can step into Agile roles (even if that isn't their official role title in the organizational chart).

So yes, in Agile you still have Project Managers, Business Analysts, Architects, Developers, Designers, etc. It's just that they are not bound by their official role and can actually take responsibility over tasks other roles traditionally perform. So for example, in Agile testing isn't necessarily the responsibility only of a tester or a test lead, and the whole team might actually participate in testing activities or tasks. 

Similarly, the team as a whole might participate in the design process or actively contribute with ideas or mockups instead of relying solely on the Designer to do the work. So in Agile roles blur. Not always of course, but they can when necessary and valuable.

Yet there are a...

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