agileways
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
agileways [2021/11/10 02:45] – 218.212.182.200 | agileways [2021/11/18 06:14] (current) – 218.212.182.200 | ||
---|---|---|---|
Line 2: | Line 2: | ||
+ | ===== Wednesday 18 November 2021 ===== | ||
- | ===== Wedmesday | + | ==== e-learning |
+ | |||
+ | === Scrum certification === | ||
+ | |||
+ | https:// | ||
+ | |||
+ | Just enough, just in time | ||
+ | |||
+ | |||
+ | ===== Wednesday 17 November 2021 ===== | ||
+ | |||
+ | ==== Diego Villaneuva ==== | ||
+ | |||
+ | === Masterclass === | ||
+ | |||
+ | Instead of Project budgeting at the start of a waterfall project, some agile team adopt team-funded approach: every 3 months, show MVPs which justify the team's continued existence | ||
+ | |||
+ | |||
+ | ===== Tuesday 16 November 2021 ===== | ||
+ | |||
+ | ==== Sandeep Shouche ==== | ||
+ | |||
+ | === Case study === | ||
+ | |||
+ | |||
+ | Epic/Story format: As a **< | ||
+ | |||
+ | |||
+ | Epic looks at the transaction to be improved, while Stories looks at the different aspects needed to deliver the Epic | ||
+ | |||
+ | |||
+ | |||
+ | ===== Monday 15 November 2021 ===== | ||
+ | |||
+ | ==== Sandeep Shouche ==== | ||
+ | |||
+ | === Scrum ceremonies from PO perspective === | ||
+ | |||
+ | * Planning | ||
+ | * Standup | ||
+ | * Backlog Review | ||
+ | * Review/ | ||
+ | * Retro | ||
+ | |||
+ | Sprint Planning: https:// | ||
+ | * Sprint Goal | ||
+ | * Definition of Ready | ||
+ | * User stories relation with other stories | ||
+ | * Prioritised | ||
+ | |||
+ | |||
+ | Daily Stand-up | ||
+ | * 10 mins: Extended discussions can be taken offline in Meet-After | ||
+ | * What was accomplished yesterday, Plans for today and Impediments | ||
+ | * | ||
+ | |||
+ | Backlog Refinement | ||
+ | * Backlog includes stories further down the list | ||
+ | * Make each story Definition of Ready | ||
+ | * Assign Level of Complexity (No. of Story Points) | ||
+ | * Optional timing: sometimes neglected. Sandeep: sometime in latter half of sprint, before demo. Helps PO get prioritisation ready for next Sprint Planning | ||
+ | |||
+ | Sprint demos/ | ||
+ | * Conclusion of sprint | ||
+ | * Key to Feedback iterations | ||
+ | * liaison between team and stakeholders | ||
+ | * prepare team for demo, expected questions, points to highlight | ||
+ | |||
+ | Sprint retrospective | ||
+ | * PO is optional. | ||
+ | * What went well last sprint | ||
+ | * What improvements | ||
+ | * Define, Discover, Determine, Diagnose, Drive | ||
+ | |||
+ | Alignment vs Autonomy | ||
+ | * Leaders need to provide vision | ||
+ | * Transparent | ||
+ | * | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== Wednesday | ||
==== Sandeep Shouche ==== | ==== Sandeep Shouche ==== | ||
Line 14: | Line 97: | ||
How to conduct retrospective meetings: https:// | How to conduct retrospective meetings: https:// | ||
Agile Retrospectives - Making good teams great: Esther Derby and Diana Larsen | Agile Retrospectives - Making good teams great: Esther Derby and Diana Larsen | ||
+ | |||
+ | |||
+ | === Other Agile frameworks === | ||
+ | |||
+ | XP is the discipline that Scrum forgot: Scrum states the What that needs to be done. But XP the How developers/ | ||
+ | |||
+ | Continuous Integration: | ||
agileways.1636512329.txt.gz · Last modified: 2021/11/10 02:45 by 218.212.182.200