the Pros and Cons of X2O development rhythm
#x2o#development rhythmat
X2O
A normal programmer should close 2 ticket and optimize 1 ticket one day. The ticket can be one small and one large, or two large feature. Or just two bug fixes.
Pros
- Helps measure progress and granularity
- Help programmer document their codes.
- Help to blame them… Opppss..
- Standardize commits with tickets.
Cons
- depend on the experience of leader who build the ticket.
- The ticket can be too large or too small.