In essence, how well do we do in building things?
Achieving planned scope on schedule is not the best metric for success, but Agile projects accomplish this three times as often as Waterfall projects.
The earlier both changes and defects can be identified and corrected, the better. They are far cheaper to fix. This is particularly true if there is some uncertainty in requirements.
PBI = Product Backlog Item, i.e. User Story, Technical Story, or Defect
Summary of Scrum ceremonies – will cover later in the course
Planning for the future never stops and isn't a defined phase, happens in parallel with development work
The team needs to be developed based on roles and functions required for the solution. For example heavy UI and UX solutions require significant participation by UI and UX professionals, while a Data Integration only effort requires significant participation by data base and software engineers. The geography locations and distributed nature of the team needs to be considered as tools and further virtual practices are needed.
The nature of the application being developed needs to be considered in determining the team mi and the critical roles. Many organization develop teams across only one dimension: Architecture or Application Layer or the Component Layer. Most large software development efforts require both teams and organizations. The component teams are general focused on developing reusable or technical backend code while the application team is focused on developing the business code.
Developing teams around features is a practical approach and is generally used for Product Management organization and for the Program Level leaders so Epics and Features can be tracked and aligned to the Release Schedule
Feature are tracked and controlled at a program leadership level while each Scrum team tracks and controls their application or component layer development while periodic collaboration and information is passed between
Feature are tracked and controlled at a program leadership level while each Scrum team tracks and controls their application or component layer development while periodic collaboration and information is passed between
SAP largest implementation of Agile at Scale with 1000s of teams