Agile Benefits
Satisfy Customers Through Early & Continuous Delivery
Welcome Changing Requirements Even Late in the Project
Deliver Value Frequently
Break the Silos of Your Project
Build Projects Around Motivated Individuals
The Most Effective Way of Communication is Face-to-face
Working Software is the Primary Measure of Progress
Maintain a Sustainable Working Pace
Continuous Excellence Enhances Agility
Simplicity is Essential
Self-organizing Teams Generate Most Value
Regularly Reflect and Adjust Your Way of Work to Boost Effectiveness
What does a self organizing team look like?
Should they interview, onboard and employ resources?
Should they manage their own budget and report ROI?
Should they have ultimate control of stories on their own backlog?
Should they own and drive their own risks?
Should they determine their own metrics for measuring value to the ART and their customer or business area? PASX Core has different metrics and OKR's to one of the MES teams as example.)
Should self organizing teams define and grow their own SOP's and Goverenance
Should they define their own work principles and team culture?
What does early and Continuous delivery mean?
Should teams own and control their own release and deployment processes?
Should teams have access to Non-Production Services and Production services in order to do releases and deployments more frequently?
Should the team define their own package, build, release and deploy processes?
What automation tools can be used to make releases and deployments quicker and less people intense?
What potential architecture and Infrastructre changes would have to be made over time to enable Earlier and Continuous Delivery?
Can actual DEMO's be done on sections of recipe's? (or isolated features)
How frequently do requirements in the ART change? Do we have change request history to review for earlier PI's?
Is the frequency of change equal in all scrum teams, or do some teams have more changes than others?
Can change in requirements be taken in small increments, for example do they typically fit into one Sprint, one PI or longer.
Tied to early and Continuous delivery, how effectively or how quick can change be run through the team from receipt to deployment?