7. 6 수
|
프로젝트 관리 기법 #2
|
프로젝트를 관리하기 위한 실제 예제
|
Mr.M
|
- lesson:
- backlog: list up all features (c.f. backlog helps create burndown chart)
- daily meeting: ask members to bring write-ups for what they did, are doing, and current issues for 10-15 minute daily meeting
- mature organization: planning and result are the same (e.g. easy backup when the person in charge is not around, short integration speed)
- what’s important in project management
- purpose needs to be shared: e.g. create backlog and share with all members
- consistency between members’ responsibility and task
- break-down big tasks into small tasks
- teamwork
- communication
- outsourcing: try to avoid outsourcing in software development
- user story: 누가, 무엇을 달성하기 위해, 이런 기능이 필요하다 (i.e. As a …, I want …, so that …)
- personal takeaway:
- user story: A user story is a tool used in Agile software development to capture a description of a software feature from an end-user perspective. The user story describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement. <source: Wikipedia>
No comments:
Post a Comment