alignment around agile processes across different building block teams
|
@Simon Eyre
| @Simon Eyre talked about his efforts to make the process more agile and discussed the importance of a product owner role and a system architect as well as single programme backlog, to help priorities actions, without which: - The team is concerned about meeting expectations and objectives. There is a lack of clarity around requirements at the API and sandbox levels, and who the ultimate decision maker is. The need more processes to define how they interact with respective teams. Simon spoke more about the need for these processes, and they need to decide which specific user stories to focus on.
@Mauree, Venkatesen requested added that what is important is to build the payments building block functionality. @Satyajit Suri suggests that the team should not get lost in the details and should stick to some principles. The sandbox should not drive the Govstack, and the focus should be on properly implementing building block candidate implementations as part of specifications. The team should define their own backlog and sprints for implementing the payments building block and align with the sandbox team where necessary. The focus should be on demonstrating the unconditional cash transfer use case. The building block candidates have to be integrated with the sandbox, but they don't have to happen at the same time.
@Mauree, Venkatesen The team will review the backlog and try to resolve any issues directly or with the help of other teams. Vijay mentioned three key focus areas for the unconditional social cash transfer use case are: Populating the account mapper API functionality for the mapper Simulation of bulk payment disbursement with a dummy payments file
|