Difference between revisions of "Agile Foundation Training"
Jump to navigation
Jump to search
m (→2015–11–24 & 2015–11–25: usage -> u) |
(Added learning options and covered/pending.) |
||
Line 14: | Line 14: | ||
*{{u|you must be present to win}}. | *{{u|you must be present to win}}. | ||
*{{u|stable team}}. | *{{u|stable team}}. | ||
===Covered=== | |||
*{{u|learning whishlist}}. | |||
*{{u|agile manifesto}}. | |||
*{{u|protocols & interfaces}}. | |||
*{{u|agile ground rules}}. | |||
*{{u|emag tiurf}}. | |||
*{{u|flow game}}. | |||
*{{u|kanban}}. | |||
*{{u|scrum}}. | |||
*{{u|magic balls factory}}. | |||
*{{u|daily standup}}. | |||
*{{u|planning}}. | |||
*{{u|story map}}. | |||
*{{u|a3 solver}}. | |||
*{{u|retrospective meeting}}. | |||
*{{u|improvement board}}. | |||
*{{u|drive}}. | |||
===Pending=== | |||
*{{u|stable team}}. | |||
*{{u|feature team}}. | |||
*{{u|persona team}}. | |||
*{{u|user story}}. | |||
*{{u|test-driven development}}. | |||
*{{u|specification by example}}. | |||
*{{u|behavior-driven development}}. | |||
*{{u|review meeting}}. | |||
*{{u|product review meeting}}. | |||
*{{u|relative estimation}}. | |||
*{{u|goldilocks sizing}}. | |||
*{{u|operations review}}. | |||
*{{u|culture}}. | |||
*{{u|planguage}}. | |||
*{{u|cynefin}}. | |||
*{{u|agile prince 2}}. | |||
*{{u|capability matrix}}. | |||
*{{u|objective & key results}}. | |||
*{{u|staff liquidity}}. | |||
*{{u|deep dive}}. | |||
*{{u|agendashift}}. |
Latest revision as of 17:06, 26 November 2015
2015–11–24 & 2015–11–25
- timebox the unknown to .
- fix the process, not the people to .
- start what you finish and finish what you start to get things done.
- stop starting, start finishing to .
- question everything to .
- on-site customer to .
- manage the work, not the people to .
- focus on quality, speed will follow to .
- work in progress limit to improve flow and liquidity of a system.
- slow down to speed up to .
- visual management to .
- visual workflow to quickly grasp the overview of progress and discover opportunities to speed up.
- you must be present to win to .
- stable team to sustain maximum results of human assets.
Covered
- learning whishlist to .
- agile manifesto to .
- protocols & interfaces to .
- agile ground rules to .
- emag tiurf to .
- flow game to .
- kanban to evolve into a nimble, flexible, innovative and powerful learning organization.
- scrum to jumpstart hyper-performing teams.
- magic balls factory to .
- daily standup to keep track of work in progress, and move it towards the finish quickly.
- planning to .
- story map to .
- a3 solver to solve the root cause of a tough and expensive problem.
- retrospective meeting to .
- improvement board to accelerate learning and become ever more effective and efficient in order to gain an unfair sustainable advantage.
- drive to .
Pending
- stable team to sustain maximum results of human assets.
- feature team to .
- persona team to .
- user story to be crystal clear on what who wants and why so it can be build.
- test-driven development to .
- specification by example to .
- behavior-driven development to .
- review meeting to .
- product review meeting to proudly present the new value just created and collect feedback to inform future development.
- relative estimation to harvest low hanging fruit for maximum return on investment.
- goldilocks sizing to .
- operations review to .
- culture to .
- planguage to .
- cynefin to approach the issue at hand appropriately and effectively.
- agile prince 2 to .
- capability matrix to .
- objective & key results to keep everyone moving forward as a team—aligned autonomy.
- staff liquidity to .
- deep dive to .
- agendashift to .