Agile Project Management is an incremental approach to planning and guiding product development. It is a collaborative approach that delivers frequent business value by utilizing short delivery cycles. It relies on constant communication between the project team members so that issues and changes can be responded to immediately. In an Agile project, reflection on events and activities is intentional and frequent so that improvements to them can be identified and implemented.
Scrum is the most recognized process framework that supports Agile Project Management. Scrum introduces artifacts, ceremonies, and roles that are new from Waterfall project management, and that have very specific purposes on an Agile project. While PlanStreet Agile Project solution utilizes common Scrum terminology it does not force your organization to use Scrum ceremonies or roles in your processes.
- Backlog: List of work to be completed. A project can have only one Backlog. Each entry in the Backlog is represented by a User Story.
- User Story: Item of work to be completed. Each User Story is added to the Backlog before any work can be done on the item. As long as the User Story remains in the Backlog, the assumption is that no one is working on it. PlanStreet Agile Project solution does not set format and content restriction to the User Stories allowing them to be used in a manner that makes the most sense to your project.
- Sprint: Activity period when User Stories are to be completed. For some industries, a Sprint represents a period of time, or phase, in terms of start and end date while for others it represents an actual activity with no specific time period associated with it. PlanStreet Agile Project solution allows you the flexibility of identifying a Sprint in a manner that works for your project.
- Sprint Board: Status of User Stories in the Sprint that is currently being worked on. If your Sprint represents a period of time, or phase, you may have statuses of In Progress, Completed, Flagged (due to issues) to show where each item of work is. If your Sprint represents activities, you can break those activities to additional levels of detail to create closer visibility to the work.