Modern Tooling and Practices for Scrum Development Teams
The Scrum Framework
Scrum theory includes time-boxing, and specific roles, rules, and artifacts. All elements of Scrum complement each other to form a consistent whole. All work is performed in Sprints. All base rules, events, and roles are described in the Scrum Guide, the acknowledged Scrum body of knowledge. Each part of Scrum ties back to the principles and theory.
This is foundational knowledge for every Scrum Team member and anyone involved with Scrum. A Professional Scrum Developer works effectively on a Development Team within the Scrum framework to deliver value in the form of working software at the end of every Sprint.
Scrum Theory and Principles
Scrum is founded on empirical process theory to deal with the complexity typical to software development. All principles and values of Scrum are based on the fundamental view of software development as creative and complex work.
Scrum Developers recognize and acknowledge this complexity. They can explain and promote the use of concurrency, self-organization and modern, agile software development techniques as an answer to this problem of complexity.
Cross-functional, Self-organizing Development
Development Teams in Scrum are self-organizing. Self-organization requires not only the availability of the right development skills, but also collaboration, team commitment, joint problem ownership, shared goals and creativity. A Development team autonomously makes all decisions on how to do the work that it has forecast it could complete in a Sprint.
Creating great software includes understanding the needs of users, stakeholders and the market place. In today’s highly complex markets with many unpredictable changes, details are added to requirements last minute, and even while programming. A Development Team and the Product Owner collaborate on the software expectations in creating, clarifying, and estimating items in the Product Backlog.
Scrum has an iterative-incremental approach to software development and the focus is on shippable software at the end of every Sprint. In the domains of software design and architecture this leads to a major shift, i.e. from prescriptive and upfront to emergence. Designs and architectures grow and change as applications and products grow and change.
As part of incremental development, Scrum puts quality before scope. Writing high quality code is an art in itself. It requires skills, dedication, mastery, agreed practices, and agreed standards.
Test First Development
It is considered a good agile development practice to think through requirements before writing functional code. It helps to consider work in terms of how it will be tested, but it also creates and improves traceability and eliminates other wasteful activities that are traditionally part of upfront requirements specification processes.
Scrum Development Teams work against company, development and organizational standards. Such standards provide guidance. The Scrum Development Teams decide on the actual implementation, thereby respecting the standards.
The ability to deliver shippable software by the end of every Sprint requires different testing strategies, where testing activities are to be done as part of development.
ALM - Application Lifecycle Management
What a Scrum Development Team must know about ALM (‘Application Lifecycle Management’). Mind the .NET specific background of some of these!