Repository navigation
Home
- Zack Nathan : Game Developer/Master
- Surya Pandiaraju : Idea Generator, Wiki Manager
- Michael McGovern : Website Designer/Master
Agile (SDLC): The development of software using Agile development practices and Agile project management. Features of Agile software development include a heavy emphasis on collaboration, responsiveness to change, and the reduction of waste throughout the development cycle, all through the use of iterative programming. Agile software development (ASD) focuses on keeping code simple, testing often, and delivering functional bits of the application as soon as they’re ready, making it superior to several other SDLC models.
Backlog: A collection of stories and tasks the Sprint team will work on at some point in the future.
Burndown Chart: A publicly displayed chart that depicts the total task hours remaining per day. It shows where the team stands regarding completing the tasks that comprise the backlog items that achieve the goals of the sprint. The X-axis represents days in the sprint, while the Y-axis is effort remaining (usually in ideal engineering hours). To motivate the team, the sprint burndown chart should be displayed prominently.
Daily Scrum: The periods in which we do work in. In our class, we do one Scrum a day.
Daily Standup: A daily team meeting held to provide a status update to the team members. The ‘semi-real-time’ status allows participants to know about potential challenges as well as coordinate efforts to resolve difficult and/or time-consuming issues… 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.
ScrumMaster: The ScrumMaster is responsible for maintaining the Scrum process and the overall health of the team. The ScrumMaster assures that the team is fully functional and productive. The ScrumMaster performs this role by administering the Scrum ceremonies, facilitating the organic self-organization of the team, and removing any obstacles that may be impeding the team’s progress.
Sprint: The Scrum term for an iteration. The sprint starts with a sprint planning meeting. At the end of the sprint there is a sprint review meeting, followed by a sprint retrospective meeting. In our case, it's composed of 3 Scrums, and at the end, we have a shippable product!
User Story: describe work that must be done to create and deliver a feature for a product. Stories are the basic unit of communication, planning, and negotiation between the Scrum Team, Business Owners, and the Product Owner.
Wiki: An editable internet site where details of stories and tracking information may be recorded during development. You are currently reading our Wiki!
Four ceremonies:
-Daily Standup Meeting
-Sprint Planning Meeting
-Sprint Review
-Retrospective
Three artifacts:
-Burndown charts
-Product backlog
-Sprint backlog