Software Development Project Management

Clients and Stakeholders define projects. To deliver projects we try to adopt agile methodologies. The is delivered through 2-weekly sprints, coordinated by sprint planning meetings.

See “learn-scrum” for a quick intro into the broad principles.

Projects

• Development projects are defined on the Wiki: https://wiki.maxfordham.com/Main/ProjectTopic
• Projects must have pre-agreed Clients, Stakeholders and Budgets
  • When a project becomes active (“Running”) it must have an associated code in Timesheets
  • See NonFeeEarningTimesheetWorkTypesExplained
• A project should have an equivalent maxfordham Github Project for task management.
• A project will be delivered through the completion of many sprints (and milestones).

Sprints

• 2-weekly meetings are used for sprint-planning where tasks are defined and assigned
• ideally the end of a sprint achieves a GH milestone, in GH tasks (issues) can be added to milestones
• uncompleted tasks are put back into the backlog

Key People

• “Scrum Master”: this will typically be Dan or John overseeing the technical progress of a project.
• “Product Owner”: this is the client that we are producing for. Outcomes must be presented to them.
• “Scrum Developers”: the people delivering the work.

Tasks to Complete in the Sprint Meeting

• review what was achieved in the last sprint. Discuss uncompleted items and move to backlog.
  • close Milestone or update date.
• define the outcomes that you would like to achieve in the upcoming sprint
  • create a GH Milestone in relevant repo
• define the tasks to do to achieve those outcomes
  • add tasks to milestone
  • assign people to tasks
  • review whether the tasks are achievable