This document discusses the role of an architect in agile development. It compares waterfall and agile architecture approaches. The architect's responsibilities in agile include incrementally documenting designs, communicating with the team, embracing change, and removing impediments. Best practices for agile architecture include inviting peer review, challenging assumptions, and learning from mistakes. The architect must understand coding and know how to work with people as technology alone is not enough.
This document discusses the role of an architect in agile development. It compares waterfall and agile architecture approaches. The architect's responsibilities in agile include incrementally documenting designs, communicating with the team, embracing change, and removing impediments. Best practices for agile architecture include inviting peer review, challenging assumptions, and learning from mistakes. The architect must understand coding and know how to work with people as technology alone is not enough.
This document discusses refactoring, which involves restructuring existing code without changing its external behavior or functionality. It provides definitions of refactoring and describes best practices for refactoring code, such as taking small, incremental steps and verifying that automated tests still pass after each change. Specific refactoring techniques are also explained, like extracting duplicate code into methods, removing unnecessary complexity or duplication, and consolidating conditional expressions for clarity. The document cautions against fixing bugs during refactoring and emphasizes making changes in a way that simplifies the code and removes code smells.
This document outlines an Agile planning and estimating workshop presented by Joshua Partogi. The workshop covers Scrum concepts like timeboxing, product backlog creation and ordering, estimating work in story points, sprint planning, and monitoring progress via burn down charts and velocity. Participants work through exercises to practice these techniques in planning and estimating the work for a mobile tourism app project over multiple sprints and releases.
The document introduces Scrum and its roles, artifacts, and activities. It discusses the Scrum process including sprint planning, daily standups, sprint demos, and retrospectives. It emphasizes that teams should strictly follow Scrum practices like having a product backlog, sprint backlog, and definition of done to achieve the benefits of an agile framework. Failing to properly implement Scrum can undermine its effectiveness.
2. 覲語襭
Agile Team Meeting & Workshop Opening / Energizing / Closing
Practical Facilitation Tool & Technique 螳蠍 Handout.
れ 谿語讌 螻, 襭襷 谿瑚 蟆曙 る 給.
2011.11.26 , Agile Korea 2011 Conference @ Seoul
誤狩 貉ろ 豈覩碁 , chaehongmi@inpeople.co.kr
Copyright 息 2010 by Inpeople Consulting. ALL RIGHTS RESERVED
3. What we will see & practice
4. Life Line
5. Random Word Talk
6. Visual Card Story
7. 豺覓旧 襷碁 襷
1. 覈 襷り鍵 8. Organizational Persona 9. ToP ORID
2. Cross Fertilization 10. 郁鍵
3. 螻牛旧螻 谿伎 11. 譟郁
12. Exit Survey
3
Copyright 息 2010 by Inpeople Consulting. ALL RIGHTS RESERVED
4. 覈 襷り鍵
覲 貉朱一れ
蠍磯? Delights
焔
&
殊? Difficulties
4
Copyright 息 2010 by Inpeople Consulting. ALL RIGHTS RESERVED