SW project management

Highly based on 'Scrum' methodology, but a bit modified.

Epic: A unit of job
  • Epic should be committed within a single PSI(Potentially Shippable Increments)
    • PSI(Potentially Shippable Increments): A time box that a team uses for the achieve a certain business goal or goals.
  • Length of PSI can vary, but it's usually 6~8 weeks.
  • A PRD(Product Requirements Documents) should be created for each epic in Confluence
  • Epic Ticket should be also created in Jira
  • it appears as a single branch: e.g. feature/add_search
Story: A sub-job of an Epic
  • Story should be done within less than a sprint
    • a few Stories would be done in a single sprint
    • if some task is too big to be done in a single sprint, you can horizontally divide the story
      • usually happens if the story has a lot of acceptance criteria
      • horizontally dividing means that each story should be applicable independently
      • e.g. you want to make the map app to show restaurants near the user in order of ratings
        • you can it divide into 'view nearby restaurants' and 'order by ratings'
  • Length of sprint can vary, but it's usually 1~4 weeks.
  • Story Ticket should be created under the Epic in Jira
  • A User Story / Acceptance criteria should be allocated for each Stories
    • should be written in the ticket
    • User Story should be written in a format of "As (user), I want __, so that __"
    • Acceptance Criteria should be written in a format of "Given/When __,  that __"
  • It would be also great if UX Flow diagram or Design is allocated for each Stories.
    • should be linked in the ticket
  • it appears as a single sub-branch of the Epic's branch: e.g. feature/add_search/search_db

Sub-Task: A sub-job of a Story
  • Sub-Task Ticket should be created under the Story in Jira
  • Sub-Task is created and allocated by developers not a Product Manager.
  • It is primarily for the developers' communication and collaboration
  • But it still has to be moderately small, so that PM can notice the stories' progress
  • it appears as a single sub-branch of the Story's sub-branch: e.g. feature/add_search/search_db/db_creation

  • As a developer, 'a ticker per a commit' is very reasonable


Above is a great example for the Story ticket.
  • Some teams include User Stories, Acceptance Criteria, and design docs in PRDs, not a Story ticket
  • It is not a good practice because developers mostly sees only the Design and barely sees PRDs. So they might not keep up with the requirements change.

댓글

댓글 쓰기

이 블로그의 인기 게시물

Interface of Java

 You can define(declare + initialize) variable like interface_name variable_name = new class_name() In such cases, the variable can only use method overriding the interfaces methods. Also, the language does not recognized it as the class; the language recognizes it as interface. Still, it does have member variables of the class and there are some libraries that enables the programmer to tell what class it is constructed(i.e. Reflection) Interface can be used as parameter of functions or return types of functions. When interface is a parameter, the class that implements the interface should be given to the function. When interface is a return type, it can be used for polymorphism. Also, variable of java(in case its not primitive type like int, float), it is rather closer to pointer of C++; it refers to the value, not contains value itself. The important point is that, when the class implements the interface, all of its public methods should be the interface's methods. If not, client...
자세한 내용 보기

Data Analytics Overview(OLTP vs OLAP)

You’ve likely heard about the lucrative careers of high-level Data Analysts, but have you ever wondered how they actually handle "Big Data"? Of course, they aren’t just using Microsoft Excel. To understand the technology behind it, we must first distinguish between the two primary ways we process information:  OLTP  and  OLAP . 1. OLTP OLTP (Online Transactional Processing)  is the DB used for company’s daily operations. Whenever you post on Reddit or place an order on Amazon, you are interacting with an OLTP database. It is triggered by the business's customer and handled by the backend server so that it can provide the business. Fast:  It handles millions of requests with millisecond response times. Small&Frequent:  It focuses on small, frequent transactions—usually just a few rows at a time. Write-intensive:  Its primary job is to record or update new data as it happens. 2. OLAP OLAP (Online Analytical Processing)  is the very technology we...
자세한 내용 보기

Leetcode

이미지
1. Two Sum: find a pair with specific sum   class Solution : def twoSum ( self , nums : List [ int ] , target : int ) - > List [ int ] : numMap = { } n = len ( nums ) # Build the hash table for i in range ( n ) : numMap [ nums [ i ] ] = i # Find the complement for i in range ( n ) : complement = target - nums [ i ] if complement in numMap and numMap [ complement ] != i : return [ i , numMap [ complement ] ] return [ ] # No solution found You might wonder how does the code deals with duplicates. As you can see, in the iteration of building the hash table, always the latter(with bigger index) will be saved in the hash table. In the latter iteration finding the complement, the former one(with smaller index) always goes through the iteration earlier, so the [i, numMap[complement]] can return two different indexes, carrying duplicate...
자세한 내용 보기