AgileTaipei.2021.03月聚會:從無到有建立一個敏捷開發團隊的經驗甘苦談
建立一個 Agile development team 這件事本身就充滿了敏捷挑戰性,而在一個並非 born to be agile 的公司內要做這事更是充滿坑洞與挑戰,這次我想分享的是近一年半來的實際經驗,中間融合了 Scrum 的儀式及 DevOps 的實戰導入,如果你也先相信了敏捷的價值,想著如果沒有現成環境何不自己打造一個?我想可以分享一些經驗給你/妳。
AgileTaipei.2021.03月聚會:從無到有建立一個敏捷開發團隊的經驗甘苦談
建立一個 Agile development team 這件事本身就充滿了敏捷挑戰性,而在一個並非 born to be agile 的公司內要做這事更是充滿坑洞與挑戰,這次我想分享的是近一年半來的實際經驗,中間融合了 Scrum 的儀式及 DevOps 的實戰導入,如果你也先相信了敏捷的價值,想著如果沒有現成環境何不自己打造一個?我想可以分享一些經驗給你/妳。
Kanban vs Scrum: What's the difference, and which should you use?Arun Kumar
Originally presented at the 207 Lean Transformation Conference, this presentation provides a practical introduction to Scrum, particularly for public sector employees, and guides you to deciding whether Kanban or Scrum will work best for your teams and projects.
Agile Transformation at scale is challenging that requires deep understanding and expertise of agility, discipline and hunger to change. In order to guide you for success in your transformation efforts, we created the Agile Transformation Governance Model. The governance model focuses on 5 key areas together with its 19 sub areas and creates high level of visibility for your transformation efforts.
Product Owner in Agile/Scrum is the single person responsible for maximizing the return on investment (ROI) of the development effort
Responsible for product vision
Constantly re-prioritizes the Product Backlog, adjusting any long-term expectations such as release plans
Final arbiter of requirements questions
Decides whether to release
Decides whether to continue the development
Considers stakeholder interests
May contribute as a team member
Has a leadership role
Must be available to the Team at any time
Agile Alliance maintains a guide on the practice areas of Agile software development. They include: extreme programming, teams, lean, scrum, product management, devops, design, testing and fundamentals. Each practice area is know as an Agile Tribe with its own definitions and best practices. Many of these practices overlap or are complementary. This file is an overview of the Agile Tribes displayed as a subway map.
Training materials for Agile Scrum. Starts with an overview of Agile and Lean. Followed with the Agile Scrum key concepts like Product Owner, Scrum Master, Scrum Team and Product Backlog. Theory is complemented with learnings and best practices from real life software development.
Scrum is certainly not a foolproof framework as it does have its own set
of limitations; which is the reason why it may not be the best fit for
every team or product. There are other Agile and Lean approaches too,
like Kanban or XP.
Therefore, what is crucial is for us to comprehend that these current
shifts call for a dynamic and progressive outlook from developers and managers. The need of the hour is to utilize the benefits that a Scrum Master brings to the table, in terms of opening up team communication and problem solving techniques.
Kanban vs Scrum: What's the difference, and which should you use?Arun Kumar
Originally presented at the 207 Lean Transformation Conference, this presentation provides a practical introduction to Scrum, particularly for public sector employees, and guides you to deciding whether Kanban or Scrum will work best for your teams and projects.
Agile Transformation at scale is challenging that requires deep understanding and expertise of agility, discipline and hunger to change. In order to guide you for success in your transformation efforts, we created the Agile Transformation Governance Model. The governance model focuses on 5 key areas together with its 19 sub areas and creates high level of visibility for your transformation efforts.
Product Owner in Agile/Scrum is the single person responsible for maximizing the return on investment (ROI) of the development effort
Responsible for product vision
Constantly re-prioritizes the Product Backlog, adjusting any long-term expectations such as release plans
Final arbiter of requirements questions
Decides whether to release
Decides whether to continue the development
Considers stakeholder interests
May contribute as a team member
Has a leadership role
Must be available to the Team at any time
Agile Alliance maintains a guide on the practice areas of Agile software development. They include: extreme programming, teams, lean, scrum, product management, devops, design, testing and fundamentals. Each practice area is know as an Agile Tribe with its own definitions and best practices. Many of these practices overlap or are complementary. This file is an overview of the Agile Tribes displayed as a subway map.
Training materials for Agile Scrum. Starts with an overview of Agile and Lean. Followed with the Agile Scrum key concepts like Product Owner, Scrum Master, Scrum Team and Product Backlog. Theory is complemented with learnings and best practices from real life software development.
Scrum is certainly not a foolproof framework as it does have its own set
of limitations; which is the reason why it may not be the best fit for
every team or product. There are other Agile and Lean approaches too,
like Kanban or XP.
Therefore, what is crucial is for us to comprehend that these current
shifts call for a dynamic and progressive outlook from developers and managers. The need of the hour is to utilize the benefits that a Scrum Master brings to the table, in terms of opening up team communication and problem solving techniques.