At the end, each final branch was represented by a Jira ticket and a Kanban board with all the to-do actions. Our mindmap was separated into 3 main branches: Build, Promote and Deploy. What did we accomplish since the last week ? A demo meeting every Friday morning to show our progressĪcting as a project manager, I made the choice of using mind mapping (e.g ) to share ideas and a to-do list.What’s keeping you from doing your tasks ? A follow-up every Thursday to identify the pain points that keeps us from doing our job.What needs to be done this week ? A follow-up every Monday for the weekly “menu”.The project organization was simple and we’ve been continuously asking and replying to these questions: In order to be fully dedicated to the project, we organized a virtual team of 3 engineers (also called vteam): One PM/Lead, one SRE and one QA engineer. We collaborated on the migration to Git (one of the biggest parts of this project). We got the go-ahead from our fellow stakeholders during the kickoff meeting then we began working on the technical part. We also sent it to the R&D team for a review. Once we had our first clean draft, we chose a name for the project, in our case it was Jaune Doe ( John Doe is everywhere). The project adds or modifies cookies, or modifies URLs,.The project will be hosted on machines with a new kind of configuration,.The project requires additional hardwares or resources,.The project involves the creation of a new service, application or tool,.The project adds a new item to the company stack,.The rollout or rollback of the project does not follow the usual process,.The project has an impact on shared resources or on the performance of a web application,.3+ developers are going to work on the project for at least 2 sprints,.A formal kick-off meeting must be set up if at least one of the following conditions is met: We have begun by a “kickoff” page under confluence to initiate the project.
We organize the project by the Agile methodology. In order to avoid defect deployment, ease releases and post-tests and be more close to the market, we have decided to turn our current pipeline to a CI/CDs
0 kommentar(er)
