1. Sprint cycle
    1. WireFrame & requirement
      1. WireFrame
        1. What is this button/text?
        2. What happen when user do [something] on this screen?
        3. Where it comes from?
        4. Multiscreen issue
    2. UI & Asset
      1. Cases & details
      2. Multiscreen solutions
      3. Language
      4. Approval process
      5. Match the schedule with development progress
    3. Sprint operation
      1. Sprint Planning Meeting
        1. Context of this sprint
        2. Goal & objectives of this sprint
        3. What will be offered to user in this sprint? (feature)
        4. Q&A
      2. Technical issue meeting
        1. Client - server collaboration
        2. Heavy solutions
          1. Define the level of solution in this sprint
        3. UX trade off
        4. Refine estimation
      3. Estimation
        1. UI stories
        2. Known functions
        3. Strange requirement
          1. Needed research
          2. Can implement or not
          3. Possibly adjust
          4. Solution
          5. Requirement
          6. Product Manager involves
        4. Background task
        5. Stories that depends on server support
          1. Scheduling
      4. Progress
        1. Milestones
        2. Daily check
        3. Builds
          1. First Alpha build
          2. Full feature build
          3. Beta build
          4. Product build
      5. Regular Issues
      6. Priority
        1. Quality
        2. Requirement built
        3. Speed (Deadline)
      7. Ending sprint
        1. Broken deadline
          1. Morale
          2. Have team member work professionally & committed?
          3. Personal working
          4. Collaboration
          5. Workload
          6. Have we estimated exactly? if yes, what happened?
          7. Priority
          8. Do we really need to include those stories into this sprint?
          9. Solution level
          10. How big is the solution they are taking
        2. Leisure time
          1. Performance optimization
          2. Code clearance
          3. Refactoring
          4. Do the stories in BACKLOG
      8. Retrospective meeting
        1. What went well during the sprint cycle?
        2. What went wrong during the sprint cycle?
        3. What could we do differently to improve?
  2. Quality Assurance
    1. Detection
      1. Test list
        1. Feature map
        2. Main flows
      2. Test cases
      3. Monkey Test
      4. Key Experience test
    2. Decision
      1. Product overview
      2. Core value
      3. Priority
  3. People Management
    1. Objectives
      1. Professional
      2. Discipline
      3. Stable team
      4. Reasonable cost
    2. Typical activities
      1. Performance appraisal
      2. Goal setting
        1. Dụng nhân như dụng mộc
          1. Characteristic
          2. Family status
          3. Financial status
          4. Financial tendency
          5. Career objectives
      3. Sprint retro
        1. How is his collaboration mindset?
        2. How is his leadership to co-worker?
        3. How is his involvement the common success?
        4. How accountable he is for issues?
      4. Salary Adjustment
        1. Based on performance & negotiation
        2. Comparing to maket level
          1. Make a reasonable range of the position
          2. If member request higher than his max level, should consider replacement
        3. Balance with other members
      5. Firing & Hiring
      6. Conflict handling
  4. Team building
    1. Culture
      1. Developer & IT guys
        1. Graduate from University with almost guys
        2. Almost time of the day they think about code, not social issue
        3. Almost not excellent at interpersonal skill
      2. Game
      3. Girl
      4. Sport
      5. Snack
      6. Flexitime?
        1. Flexitime?
      7. Startup spirit
        1. Building product that they love
        2. Bring benefit to thousands of users
        3. Success or failure are in each member's hand