You should negociate Key indicators performance. For project, you should consider scrum instead a kanban, to measure velocity and bandwith firstable in storypo

You should negociate Key indicators performance. For project, you should consider scrum instead a kanban, to measure velocity and bandwith firstable in storypoint and convert it into mandays. Second, you must choise kpi according the business value. Except sales, what automation will breed, cost savings in men days . Next you must priorize business needs . For the project, you need a roadmap and takes commitments for the quarter. For projects from scratch first sprints consists in delivering server, database. Others springs small evolutions. According the mean score of velocity, you should consider a Support epic for bug fixing for a third of sprint. In parallel you should consider a kanban. So for each sprint planning , you must communicate to the users and the team all chosen user stories. During the review you could present the delivered function to the business . The retro is useful to improve organization . So the main report is defined by the burndown chart, list of epic , the time in the roadmap, the budget . For support, you must analyze the kind of question, the kind of bug. For blocking and critical bugs, you must propose the rootcause, a bug fixing and then a solution. For functional question, you must build a Qna and a document for change management and the needs of complement of knowledge transfer.