 |
| Add caption |
What
exactly is Safe? Explaining the Optimized Agile Process
Larger organizations tend to
move quicker than smaller, more flexible rivals, and they're more resistant to
change. Many of that can be chalked up to the more deep-rooted structural
problems of becoming a larger incumbent, both to policy-and process-based barriers,
as bureaucracy continues to thrive in larger business environments.
Nevertheless, several larger
organizations are trying to reap the advantages of rapid growth, for which they
may not be inherently suitable. The Scalable Agile System (Safe) is a powerful
tool that can be used to support large organizations to solve problems that
negatively affect the performance of the project.
Safe gives large organizations
a framework for becoming more agile because their deliverables can reach the
market faster.
Agile software development
methodologies have been nothing for industries that use tight controls. A
Secure team could be 8 to 10 members, with all they need to produce apps,
end-to-end: specifications, scripting, reviewing, and deploy. Several groups
are building what Safe called a release rail, collaborating around a plan (more
about this below). It has a separate line item in a budget-the organization
spends a particular thing.
A portfolio is a list of those
projects, the total amount of IT spending dollars going into the production of
apps. Safe calls this "Project Allocation Management" which suggests
that the responsibility for program and mission procurement, decision
management and preparation lie in one area.
The "Release Train"
in Safewords are the team-of-teams, usually of 50–125 men. The release train
runs on time like a regular train, though that timetable can be as versatile as
the company wants it to be. This Increment System (PI) is listed in more detail
below. Safe indicates that people engaging in a release train should be
dedicated to that release train full-time, irrespective of the reporting
framework. The release train follows a long-term plan and will have several
departments and programs inside it. The teams synchronize, line up sprints and
releases, so the technology for each increment can be implemented
simultaneously.
Iterations of Safe proposed a
"hardening sprint" (or two), not for system training as well as for
user interaction coordination. Considering the hardening sprint as an
intermediate phase could be better – anything new system teams need to render
the release train a success. Safe often encompasses traditional, intense
programming techniques such as pair function, not only for programmers but for
many purposes, as well as refactoring (improving existing application design)
and collective ownership. Joint ownership of code is becoming more complicated
for multiple teams, but it also ensures that teams will make corrections for
another group instead of having a "bus," or "make-work." It
stops the first team from being blocked and also does not cause preference issues
for Team Two-as the target of Team One and attacker would presumably be the
"good to have" of Team Two.
