Some software development processes at Indigina are to be run according to the Agile framework, specifically scrum, with story points, sprints and velocity. The sprint will be two weeks at a time.

Currently at Indigina there are multiple requests on developer’s time and so it’s unlikely that any developer will be full time on a project. Therefore there will be a proportion of time assigned to the sprint per developer. This will include likely deviation time plus absence, combined into one.

Project Summaries at Indigina

Product Manager vs Product Owner

This might be helpful for understanding Product Manger vs Product Owner

https://280group.com/wp-content/media/Product-Owner-vs.-Product-Manager-Role-Visualization.png

Open

Product Owner vs Scrum Master

Open

product-owner-vs-scrum-master.png

Scrum Master VS Product Owner | Top 5 Differences you should know (educba.com)

Agile Projects

Agile processes will be applied to the following projects:

• Order Picking and Packing (aka US Retail Compliance, Indigina)

• Voyager (Project Suez, iTransition team)

Processes

Formal Meetings

• Daily standup at 10am (included in weekly planning meeting on Mondays)

• Sprint review (possibly with Brett Thomson?)

• Sprint Retrospective

  • to work out what went right and what needs improvement in the process

  • take at least one of the improvements forward to the next sprint

• sprint planning

  • planning poker for user stories (need packs of cards or phone app, eg. on Google Play Store ESTIMA- Planning poker for remote teams BRICKMAKERS GmbH)

  • user story breakdown / task agreement

  • planning of next sprint

Informal Processes

• User story refinement

• Burndown (sprint duration)

• Burnup (project duration)

Existing Non-Agile Projects

• DCM

• Seko360 (aka SupplyStream)

Project Responsibilities at Indigina

Voyager (Project Suez)

Order Picking and Packing