Agile Project Management Office (APMO) will focus on value streams (development initiatives) and agile implementation of products, solutions and services based on prioritized development requests
A secondary key role is to optimize the throughput and number of initiatives
APMO will manage agreed unified development channel (product backlog) and staffing/resource allocation of Agile multi-talent Advisor development squads
Agile squads produce development proposals for Customers Product and Business Owners challenges; based on their visions, Product Backlogs and Epics; and utilizing the most appropriate development methods
Transparent project / development backlog can be establisehed eg in the Azure DevOps where status of development is monitored using eg Kanban boards:
Project ideas from the business are fed into the portfolio Kanban, where the project is moved forward as it progresses
In Reviewing phase, the idea (epic) is described in a level needed for making a go/no-go decision on it
In Analyzing phase, the features of the selected idea are defined
In Starting phase these features are transformed into user storiesIn Implementing phase, the Agile team dismantles the user stories into specific tasks and prioritizes them into a backlog list of items to be implemented by the implementation project
The implementation project carries out and monitors the progress of the tasks using its own Kanban boards Product Owner participates the prioritization of the programs and tasks, as well as validates the results of the development work
Agile team consists of wide range of expertise and it may contain also members from the Customer/3rd PartiesFujitsus Scrum Master coordinates the work of the Agile squad
Agile methods which mutually deemed suitable are used
Eg, Kanban, Scrum, Large-Scale Scrum, eSAFE
Tooling used in Agile methods is not fixed, restrictive
Fujitsu requirement for tooling is that tools are available and usable for all parties of the Squad with proper access and editing rights
Preferably tools should be integrated to other required tools, eg, ServiceNow or Backlog to avoid manual operations like Copy-Paste
As a rule of thumb, tools are owned by the Customer or Customers subscriptions or tenants of cloud based tools
Backlog Preferable one backlog updated cross Service Areas in a tool mutually deemed suitable for the purpose
