The U.S. federal TechFAR Handbook offers examples of key government and contractor team members needed to effectively support Agile software development.
Tester: Government user to test features and functionality of the system.
Contracting Officer (CO): Authorized to bind the Government contractually and direct contractor action.
Contracting Officer’s Representative (COR): Performs functions specifically delegated to them by the CO in writing for the particular contract/order. This individual may also serve as the Product Owner.
Project Manager: Government manager of the Agile process. Also sometimes called Scrum Master.
Legal: Provides legal review of all documents and actions.
Developers*: Software architects who design the system and write code.
Project Manager: Manages the team’s execution of the project.
Tester: Tests features and functionality of system to uncover software bugs in functional and non-functional areas of the system; ensures system functionality.
Interface: Ensures system can communicate with other systems or people as needed. This is not a required team member; membership depends on project needs.
*Cross functional individuals should occupy these roles (developers and testers are both able to work each position). Automated testing is encouraged where the tester can write and run automated tests that are supplemented with exploratory testing. (Source: The TechFAR Handbook for Procuring Digital Services Using Agile Processes)
Continuous delivery: A design practice used in software development to automate and improve the process of software delivery. (Source: Wikipedia)
Kanban: A visual process management system that tells what to produce, when to produce it, and how much to produce. (Source: Wikipedia)
Retrospective: A meeting held by a project team at the end of a project or process (often after an iteration) to discuss what was successful about the project or time period covered by that retrospective (Source: Wikipedia) See also: Running retrospectives
Scrum: An iterative and incremental agile software development framework for managing product development (Source: Wikipedia)
Sprint cycles: A “timeboxed” effort; that is, it is restricted to a specific duration. The duration is fixed in advance for each sprint and is normally between one week and one month, although two weeks is typical. (Source: Wikipedia) See also: Features of agile
Stand-ups: A meeting with attendees typically standing. The discomfort of standing for long periods helps to keep the meetings short. The meetings are usually timeboxed to 5–15 minutes and are held standing up to remind people to keep the meeting short and to-the-point. There are three questions to ask and answer in the daily stand-up (“What did I accomplish yesterday?” / “What will I do today?” / “What obstacles are impeding my progress?”) (Source: Wikipedia) See also: Features of agile
User stories: One or more sentences in the everyday or business language of the end user or user of a system that captures what a user does or needs to do as part of his or her job function.(Source: Wikipedia)
See also: Writing user stories, 5 ways to help user research work better in agile