the Pros and Cons of X2O development rhythm

#x2o#development rhythm


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.


  • Helps measure progress and granularity
    • Help programmer document their codes.
    • Help to blame them Opppss..
    • Standardize commits with tickets.


  • depend on the experience of leader who build the ticket.
    • The ticket can be too large or too small.
« Why I use X2O