Scrum Practice with Adobe Premiere Pro Team
① Reasons for using agile development: The plan is overdue by 25 %, and the important reason is to fix bugs . Agile transformation starts with Scrum
② There are many people, how is the Scrum team composed? The plan is to include 3 cross-functional teams, the Program manager is the Scrum master of the three teams , and the Senior Product Manager is the CPO , who has the final say, but the PO group includes EngineeringManager , Scrum Master , Quality Engineering manage , User Experience designer .
③ Adobe Premiere Pro team initially cited the three primary obstacles encountered by Scrum : how to collaborate with remote teams, how to split requirements and ensure that the split requirements are still valuable, how to collaborate with other teams using waterfall development
④How to cooperate with remote teams? One of their attempts was to combine the local teams into a Scrum team. This reduced barriers to communication, but such attempts failed because the local teams did not have the skill sets required by cross-functional teams to deliver requirements independently. They made another attempt: Scrum team composition principles, more consideration of skill sets and interpersonal relationships, and less consideration of geography. The obstacle encountered is communication. To solve this problem, all people were asked to use the Adobe Connect tool to simulate "working together".
⑤ How to split requirements and ensure that the split requirements still have value? There is a need to shift from traditional hierarchical development based on architecture to delivering small requirements with business value. The specific method is to split the requirements into small requirements according to the value, and cut the layers of the architecture vertically to ensure that each value can be delivered and complete testing can be carried out. In the traditional approach of layered architecture, a complete test can only be carried out after all layers are completed.
⑥ How to collaborate with other teams using waterfall development? Jointly adhere to important milestones and recommend best practices in agile development to teams using waterfall development to reduce integration risks, such as risk-forward, test-forward, pair programming, continuous integration, etc. It should be said that in this scenario, the team using agile development cannot easily change the overall collaboration plan that has been formulated, that is, it is not easy to respond to changing needs. Waterfall development teams still need to evolve to agile development if they are to be effective.
⑦How to judge that the quality has been greatly improved? The metrics used by the Adobe Premiere Pro team include: 1) Serious bugs in delivery testing ; 2) Convergence rate of regression testing bugs 3) Proportion of actual bug fixes
⑧ Lessons from Adobe Premiere Pro team 's approach to waterfall development: There are a lot of bugs in the testing phase . Due to the pressure of delivery, the practice of "quick resolution but increased long-term cost" is often adopted, such as 1) delaying bug revisions , although these bugs will affect Customer usage; 2) Modifies the symptoms of the bug without considering the root cause 3) Fixing the bug does not refactor the code to keep it clean, increasing the complexity of the code. All of the above add technical debt at the code level. On another level, a large number of overtime bug fixes lead to inefficiencies in the early stage of the next version.
⑨ The requirements with the highest priority are not necessarily functional requirements, but may be technical requirements and non-functional requirements, depending on the stage of the product. The Adobe Premiere Pro team originally referenced Scrum , and the goal of the first release was to ensure the reliability and performance of the product, because that was the biggest problem with the product at the time. " Losses from unsatisfied non-functional requirements are often the greatest value of such requirements "