Scrum agile development methodology, or how to be in the flow of all project participants

image



,  ?  ,  , . ,  100% .  —  ,   , ,  , ,   .



  IT   , ,   ,   -   ,    .   , :). ,  , , ,  ,  , , , , , ,    , .



Scrum , ,   ,    .    , ,     .   , .



  ,   ,  . ,    — .  ,  ,  ,  ,     , , .



  ,    —   , . 12 , , 9 ,    7 , ,     4- , . , , ,     , . ,   , . ,   .  , ,      ,     Scrum-.



?





Flexibility in IT is now everywhere and the Agile philosophy with a set of values ​​formulated in a manifesto of 4 key ideas and 12 principles is also on everyone's lips, in plain sight, and possibly in the clip of your project in which you participate. We fully support Agile in terms of the interaction of people within teams, we work for a working product together with the customer, who, as indicated earlier, is part of the team, and of course, we are 24/7 ready for any changes, absolutely any.



We decided on the philosophy, but we didn't have to go far for the methodology, or as the books are correctly called - the framework. Scrum fit almost perfectly into our project. Why almost, but because we are talking about flexibility and it turned out that you can also implement flexible methodology flexibly. For example, we sin by taking tasks into an already running sprint, yes, we can also transfer unclosed tasks to the next sprint. But this does not prevent working according to the Scrum methodology and successfully delivering the product.



I'll tell you about the adaptation of the methodology to the reality of the product being developed. Yes, perhaps adherents and adherents of Scrum to the very roots will be a little surprised by the approach described below, but guys, we are IT, which means we need to try options, adapt to our processes and achieve success! After all, the ultimate goal is a high-quality and on-time, working product! What we are doing with the team.



So, Scrum methodology / framework, what we took and how we have



1. Product owner (PO) - Customer



In our case, this is an external customer, IT-technologists (there are 1-2 technologists in each team) who are fully involved in our development processes by exposing and broadcasting the requirements / tasks of their business customer. A business customer, by the way, from time to time participates in shows and grooming of teams, which is very useful at the stage of collecting the primary requirements of global tasks, fixing intermediate and final results.



2. Scrum master (SM) - Lead in the team + facilitator



One of the team members with a managerial streak. Either a self-nominated candidate is selected by the team, and the candidate is considered by voting. Scrum has several roles:

 
  • SM - acts according to the methodology, conducts meetings, organizes communication within the team, monitors the implementation of tasks, corrects the vector, if the situation requires it
  •  —     ,   /   .
  • , , . ., ,  .  Scrum   . ,   2 (   ),   ,    . .



3.



5-9 .  6  12 .      6 ,   - ,    12 ,  .



  .     7 , 50+  : , (Front, Back, Integration), , ,  .



  100% , .    Scrum . ,     , ,  ,   - .  . ,   ,   , , ,   . SM ,   ,  , ,   .   , . .     , , . ,  ,  , /,   .   , «»  .     , ,   , ,   ,   , -   , . ?



 , , . ,  .







1. Boards —

-   .  , ,      , ,    Kanban . Kanban , ,  .   ()   - ,  .    , , ,  . ,  ,  .   ,  Jira.



Scrum- ,     ,   , , . ,    ,  .   .   . , , , ,    ( Story Pointʼ) .



  :

 



,    Jira, , , ,     ,    ,   . - , , , - . ,    Jira, Scrum . ,     .



  ,  .     ,     .



,   ,  45%.    Jira,   SM,  .



2.



, , ,    -, VoIP .  Skype,       ,   . ,  ,   , , , . , . . ,     -.



  , - Zoom . . .    ,   -. ,  , , , .    online,    .



SM ,   ,   .



,   Confluence,   ,   , - ,   . Confluence     , ,  online,   . ,   , . .



3. Backlog —



 . Scrum-  Jira,  .   ,      , , .



«»   ,  , -,  e,   «Backlog».    ,   /  . ,     . , - - ,   ,   ,  ,  ,   .     . ,     .



    SM,     ,  SM. , ,   -  ,    .



Backlog:

 

  •  
  •  
  •  
  •  
  •  



  .    ,  Jira.       . , , epicʼ   ,  .



 Jirʼe :

 

  1. = . 10+  .
  2. = Epic  Jirʼe
  3. Epic    
  4. =





4. ()



,     ( , , : ,  ) ,      ( ). Agile  ,   ,   , ,     Story Point (SP).     ,      ,       3, 6, 9, 12. 3 , 12 . -  2 SP, -   ,      3 SP, .



, , Planning Poker.    SP.   , 2 , . ,   ,       . SM  ,  ,   ,   , (   ,     )      SP. SM    , ,  ,    ,   . , SP . .



= .    ,   Jira, SP   . , SP    SP .  ,  «» .  ,  2-   150 SP,      ,   , 75 SP ±.  ,   ,       .



 Epicʼ   .  ,    SP. ,  ,   .  SP. SM, .



5. Sprint



,   ,    . :

 



, ,  1 — 2 . .   2- ,   :

 

  1. 10 - ,
  2. 40    . / . 40   ( 1 ),   30   .   2 * 2   * -
  3.        , . ,   2 ( , , )



,   7 .    .  - /   ,  -  .    , .   .



  ,   .



       —    , .



  ,  3 :



  • ?
  • ?
  •   /?



,   , .  ,     ( - . , ). ,   ,  :

 

  1. ? .    .  , ,    . SP,   ,  .   .
  2.   .   ,  ,  



,      .      30 . , , ,     (     ).



(Grooming)  , ,     / .     (,  16:00).    :



 

  • /



 30   .



(Demo/) — ,   . Demo   ,       .



Demo ,   , ,   . , , ,   . .   ,   ,   , -  , ,     .   ,   .   — ,     ,  -   « ».     ,   .



 —   ,    .   ,   ,   . ,     ( , ), ,  ,   .



,   . , , ,   , -,    ?  - ,   ,   .   . , ,  , . .       «» , , , . ,    — , ,     ,     .   ,   , ,   .  ,    — , ,       ,   ,     , .



  ,     ,     .



, ,     Agile  Scrum . - ,    3  ,      .



.   .



:






All Articles