Anda di halaman 1dari 6

1

Scrum is an excellent process but it really only defines a process for a team-level and
sprint-level process. It doesn’t specify any additional layers of management that may be
needed on top of it for larger and more complex projects.

That may be sufficient for small, single team projects but other layers of planning may be
needed to scale a simple single-team project to a larger scope and complexity.

2
In many cases for larger and more complex projects, it is essential to add additional
layers of planning to the project

Most Scrum projects will have at least project-level planning where at least the high-
level goals and objectives of the project are defined; however, project-level planning can
be as “thick” or “thin” as necessary depending on the nature of the project.

The project-level planning forms an “envelope” around the team and sprint-level
planning process defined by Scrum; however, the project-level planning would typically
be at least somewhat dynamic. Rather than defining a rigid upfront plan that might not
change for the entire duration of the project, it would be expected that lessons learned
from the team and sprint-level planning process would be fed back into the project-level
planning process to make adjustments to the project-level plan as necessary.

3
In addition to the project-level planning, for large complex projects you might also need
to break up the project into releases and add an additional level of release planning. The
release planning can also be as “thick” or “thin” as necessary but would typically define
the high-level capabilities to be included in the release and might also estimate the time
required to produce the release.

4
As I’ve mentioned it is very possible to blend a plan-driven approach with an Agile
approach to create different levels of Agility as shown here. It is primarily a matter of
putting the right level of emphasis on different levels of planning in the project.
At one extreme, a highly adaptive approach might be limited to team-level planning only
with little or no release-level planning or project-level planning
At the other extreme, a more plan-driven approach would put a much higher level of
emphasis on project-level planning and release level planning
By adjusting the level of emphasis on planning at each of those levels, it is very possible
to create a broad range of hybrid Agile approaches with different levels of agility and
adaptivity.

5
In the next lecture, we’re going to talk about a couple of examples of applying Agile
principles and practices to real-world projects.
Thanks for taking the time to do this lecture and I’ll look forward to working with you in
the rest of the course.

Anda mungkin juga menyukai