2016년 3월 28일 월요일

[Links] Scrum of scrum

Definition
http://guide.agilealliance.org/guide/scrumofscrums.html

A technique to scale Scrum up to large groups (over a dozen people), consisting of dividing the groups into Agile teams of 5-10. Each daily scrum within a sub-team ends by designating one member as "ambassador" to participate in a daily meeting with ambassadors from other teams, called the Scrum of Scrums. - See more at: http://guide.agilealliance.org/guide/scrumofscrums.html#sthash.XvWPKlh8.dpuf


Large scaled scrum team structure
https://www.mountaingoatsoftware.com/agile/scrum/team
The illustration below shows how a Scrum of Scrums approach allows Scrum to scale up (in this case to 243 people). Each cell represents one person on a Scrum team. The bottom of this illustration shows teams with nine developers on them. One person from each team (the differently colored cell) also participates in a Scrum of Scrum to coordinate work above that team. Then from those nine-person teams, another person is selected (this time shown with diagonal lines) to participate in what is called a Scrum of Scrums of Scrums.
scrum of scrums 
Read more about conducting the Scrum of Scrums meeting.

Using Scrum of Scrums with Agile Teams to Coordinate and Collaborate
http://www.infoq.com/news/2014/03/scrum-of-scrums
: 사실 대규모 조직에 대한 scrum 조직에 관련된 내용이 많지 않아서 그런지 scrum of scrum 관련 article이 별로 없다.


(참고) 제품책임자(Product Owner)
 <우선순위 미팅>
 PO는 2주에 한번 C레벨들과 함께 적절한 우선순위 맞춰 과제를 진행하고 있는 지 공유하는 
 우선순위 미팅를 가졌으며, 돋보이기 위한 경쟁의식때문에 우선순위 미팅은 우선순위를 고려하는 미팅이 아닌 과제 PT자리로 퇴색되고 말았으며, 해당 미팅을 통해 자율적으로 과제를 선정 진행한다는 초기의 스크럼 계획과는 달라 C레벨들의 입김에 따라 과제의 우선순위가 바뀌고, 진행중인과제가 홀딩되는 웃지 못할 해프닝도 있었다.
제품 소유자(Product Owner)에 대한 오해

Spotify 조직문화
https://selfothercontext.com/2013/02/27/spotify/

[Link] 상속된 class들을 위한 DB model 방법들.


Refactoring 중 data modeling을 다시 하다보니 db table을 변경해야할 필요가 생겼음.
기존 table들이 single table inheritance형태로 되어 있던데 적당히 정규화 해서 분리해야할 듯함.

http://stackoverflow.com/a/1568007

Martin Fowler discusses this extensively in his book Patterns of Enterprise Application Architecture book. Get this book and look into:
  1. Single Table Inheritance
  2. Class Table Inheritance
  3. Concrete Table Inheritance
The Website should give you some idea. You might also want to read the section on inheritance mappers. Each of the different approaches have their pros and cons so choose wisely.
shareimprove this answer

Single Table Inheritance
http://martinfowler.com/eaaCatalog/singleTableInheritance.html

Class Table Inheritance
http://martinfowler.com/eaaCatalog/classTableInheritance.html

Concrete Table Inheritance
http://martinfowler.com/eaaCatalog/concreteTableInheritance.html


How to Model Inheritance in a Relational Database
http://www.vertabelo.com/blog/technical-articles/inheritance-in-a-relational-database
: 관련 article, view를 사용해서 적절한 data structure를 제공해 주는 방법