Clever Geek Handbook

Is a new development methodology needed?

If you are planning to create your own software company, then you are thinking about how to organize the work of people, how to choose a methodology for work. But if you look closely at the well-known methodologies, then there is some mistrust of them, especially if you spend your own money on the company ...





I took the liberty and tried to combine useful things from well-known methodologies, and also added my own experience and advice from friends. Anyway, I'll leave it here, maybe someone will benefit from it.





Prerequisites for the creation of the methodology

Reasoning about modern methodologies and human nature

Modern methodologies, in the order of their origin, have many disadvantages:





  • The functional structure seeks to create more departments, since each potential leader needs to give people subordinate and additional responsibilities. This leads to a more complex management structure, which leads to an increase in the importance of these new leaders and a drop in overall efficiency.





  • The project structure leads to the dependence of a group of people on one project manager, who in 95% of cases out of 100% is incompetent. Focusing on short "projects", leads to higher prices for products over time





  • The matrix structure (all three types), by definition, contains a conflict, which is initially ineffective





  • There is also a great underestimation of testing in the design and matrix structure





  • In SCRUM (agile) methodology, there is often a Product Owner who aspires to become a project manager, for which he can be subordinated to an analyst in order to increase his significance. Exactly also, if there is an ambitious or conflicting team member, then this destroys everything.





  • The low role of analytics and testing in agile also does not benefit the company's products.





  • agile





. , :









  • , ,





  • ,





  • ,





  • ,





  • ,





  • , , ,





  • ,





“” , . Agile . , ?





:





  1. , , . , . ,





  2. , . ,





  3. ,





  4. , , , , -





  5. ,





  6. , , ,





  7. , , , DevOps, ..





  8. , , agile ,





  9. , “” , ,









  11. , , soft skills ,, ,





  12. , , ,





  13. ,





?

, .





, . , .





, :





  1. - ? , , , - ?





  2. , , ? , ? ?





  3. 2 , , , ?





  4. , ?





  5. , , ?





  6. , , , ?





  7. ? , ? , , , ?





?

  1. Unit ( )





- . “”, ( , ). , , , , .





, .





  1. ( )





- API , ( ) / , . , , backend . routing, IoC- .. ,





, .





  1. ( )





- , . , , , , .





, . , :





  • (Equivalence Classes)





  • (test cases)





  • ( ) ,





, .





  1. ( )





- , ,   . , , .





, .





, , . , , .





, . , , .





, , , , .





. , . 10% 90% , ( 0%/100%). , .





:

















  4. ,





  5. . , .





  6. ,





  7. :









:





  1. ,  





  2. ,





  3. , ,





  4. , . , ,





  5. , . , . ,





  6. agile , :

















  • demo









  • story points





  1. agile (SCRUM):





  • product owner , ,





  • times & materials





  • team leader





  1. . , .  ,





  2. - , ,





  3. user story «»,





  4. infrastructure as code





:





  1. ,





  2. . ,





  3. , ,









– , .





– , / . . , . , : , , .





– . . . , ,





– «», . - , . , ,





– , , . , . .





– , , . , ( , ..). .





– , . .





- , user story .





: , user stories. user story ,





  • ( )





:





  • , (feature)





:





  • , , . , : ; ; .. ,





  • , . , .





  • . . , ,





  • ,





:





  • « », :





    • ,

















  • , .









  • ,





  • , . , ,













  • , (, C#, Go , )





  • , .





  • , ,





  • ,





  • , . ,





:









  • ( )





:





  • «», :





    • ,





    • API , , ,





    • single responsibility principle





    • /





    • , ,





    • , ,









  • , (NuGet ) , . ,









  • . , ,





  • " ", , ,





:













:





  • «code review»













  • unit





  • ,





  • user stories user stories





( )





:













  • ,





  • ,





  • ( )





:









  • ,









  • ( , )













  • user stroy required, desired, optional





  •  





  • ( )





:









  • ( )





:





  • ,









  • ( )





:









  • enterprise





  • ,





  • ,













:













  • ( )





:













  • ,





  • , , ,





  • . statements DISC. HR





  • , ,





  • “” , , ,





  • , , “”





  • , .













:





  • ,





  • DevOps









  • ( , , )

















, . , ( , )





.

  1. . :





  • ,





















  2. , user stories





  3. , .









  5. , . user story user story . . 1.





  6. user stories





  7. , . ,





  8. User stories   SP, 2,





  9. , milestone 3. , user stories





  10. , :





  • , , ..





  • , .





  • , .





  1. , .





  2. user story





  3. user story . , user story. , , user story. user story - . , . user story .





  4. user stories, 2.





  5. user story user story, 40 story points, story ,





  6. user stories . , , , , DevOps, , , ,





  7. , 3.





  8. , , , ,





  9. 4 ,





  10. user story





  11. , , ( , user story ).





  12. , 4.





  13. , . user story, user story 3.





  14. , user stories, , , user stories , . ( 2 ),





SCRUM

















1.





:





: , , . user stories.









“< >”





: . API. , , , , . , , , , , . . , .









…









: , . , API . - , , . Statefull stateless , . ?









: . , , , ..





“ ”





< >





“ ”





< >









…













…









…









: . , , , , .









: ( API, , , , ..)









: . , . , .





Continuous integration





: . , , .









: , , :









  • Eptda









  • .





  • ( )





1.0





1.1

“ ”

2. SP

Story point (SP)

Hours (4*n + n), ..

1

4

3

15

5

25

8

40

13

65

21

105

34

170

55

275

- story point, . , - , . , ( ).





SP , , .





user story , 4 . . story points, .





3.

:





  1. feature story point, 2.





  2. user story ,





  3. ( , )





  4. (15%) (10%). , , ,





  5. ,





  6. user story , story point . user story. ,





  7. , ( , )





  8. , , .





  9. User story . , .









  11. ,





  12. , ,





4. milestones

:





  1. user stories story point, 2.





  2. . ,









  4. story point





  5. ,





  6. , ,





  7. , user story











More articles:


All Articles