Read Anywhere and on Any Device!

Subscribe to Read | $0.00

Join today and start reading your favorite books for Free!

Read Anywhere and on Any Device!

  • Download on iOS
  • Download on Android
  • Download on iOS

Adaptive Agile Scaling: Strategies for aligning agile development process to teams of varying size.

Adaptive Agile Scaling: Strategies for aligning agile development process to teams of varying size.

Charles Walstad
5/5 ( ratings)
The eleven purposes and goals of this book are listed below. Please note that our last goal is where we ask for your feedback on what you think of the book and how it can be improved. If there were any omissions that you think are important, please let us know what they are.

To address the size of project teams at organizations when it is not possible to have the ideal five to nine development team size, Scrum recommends.
To show how to keep management practices used by development teams as lean as possible.
To provide guidelines for the entrepreneur that intends to grow a small company into a large one and needs a development system that works well as it grows.
To provide guidance for the experienced IT manager who is structuring or is thinking about adjusting the amount of process surrounding teams of different sizes.
To describe what worked or did not work for us to shorten the trial and error period when scaling up and down.
To provide answers to teams that have been using Agile but it is either too much or too little for what they were doing.
To provide guidance to mid and large size companies on how to scale up for a given project and then down, or for companies in growth, how to scale up and hold at that level.
To show how to utilize internal SMEs better when external consultants are contracted to work on a project.
To provide information of what ideal Scrum consists of to aid those individuals who do not have a good understanding of it.
To provide an excellent glossary that contains in-depth explanations and is not just limited to items found in this book.
Our final goal is to keep the book lean but to receive feedback from readers essentially to fill in any omissions. We would like the final version of this book to meet as many of the reader’s needs as possible.




One of the main goals of this book is to address the size of project teams at organizations. Yes, Ken and Jeff specify that the ideal Scrum team size is 7+ or - 2 , but teams of that size are not always possible. Frequently due to funding issues teams are smaller than 5, or due to the large size of a project, teams will exceed 9 people. We are not in any way suggesting that teams of 5-9 are not the ideal size, but when that is not possible, we need to continue to move forward.

A problem that I have seen at companies is that they will utilize more of the agile practices than they need. The reason that this is a problem is because the more management practices that a team incorporates, the more overhead and work effort that it needs to contend with. If a small team of two can get away with just a kanban backlog why not?
Language
English
Format
Kindle Edition
Publisher
Agilest LLC
Release
January 03, 2016

Adaptive Agile Scaling: Strategies for aligning agile development process to teams of varying size.

Charles Walstad
5/5 ( ratings)
The eleven purposes and goals of this book are listed below. Please note that our last goal is where we ask for your feedback on what you think of the book and how it can be improved. If there were any omissions that you think are important, please let us know what they are.

To address the size of project teams at organizations when it is not possible to have the ideal five to nine development team size, Scrum recommends.
To show how to keep management practices used by development teams as lean as possible.
To provide guidelines for the entrepreneur that intends to grow a small company into a large one and needs a development system that works well as it grows.
To provide guidance for the experienced IT manager who is structuring or is thinking about adjusting the amount of process surrounding teams of different sizes.
To describe what worked or did not work for us to shorten the trial and error period when scaling up and down.
To provide answers to teams that have been using Agile but it is either too much or too little for what they were doing.
To provide guidance to mid and large size companies on how to scale up for a given project and then down, or for companies in growth, how to scale up and hold at that level.
To show how to utilize internal SMEs better when external consultants are contracted to work on a project.
To provide information of what ideal Scrum consists of to aid those individuals who do not have a good understanding of it.
To provide an excellent glossary that contains in-depth explanations and is not just limited to items found in this book.
Our final goal is to keep the book lean but to receive feedback from readers essentially to fill in any omissions. We would like the final version of this book to meet as many of the reader’s needs as possible.




One of the main goals of this book is to address the size of project teams at organizations. Yes, Ken and Jeff specify that the ideal Scrum team size is 7+ or - 2 , but teams of that size are not always possible. Frequently due to funding issues teams are smaller than 5, or due to the large size of a project, teams will exceed 9 people. We are not in any way suggesting that teams of 5-9 are not the ideal size, but when that is not possible, we need to continue to move forward.

A problem that I have seen at companies is that they will utilize more of the agile practices than they need. The reason that this is a problem is because the more management practices that a team incorporates, the more overhead and work effort that it needs to contend with. If a small team of two can get away with just a kanban backlog why not?
Language
English
Format
Kindle Edition
Publisher
Agilest LLC
Release
January 03, 2016

More books from Charles Walstad

Rate this book!

Write a review?

loader