Konke ucwaningo malunga nenqubo yokukhiqiza isofthiwe esekelwe izindlela eziningana ezivamile zokwakha isofthiwe esidumile. Sinikezela ukulungiselela imikhiqizo nge-frequency esithathwa ngokuvumelana nezidingo zebhizinisi. Isilinganiso se-Iteration kufanele ibonise isivinini esizayo sokushintsha kwe-Backlog yama-product. I-Teams kufanele ibonise kuzo zonke ama-Iteration kanye ne-Backlog items. Futhi ngokuvamile, kufuneka kukhona izinzuzo. Kusukela ku-Priorities Management approach iyona ngokugcwele futhi ungenza ukucacisa ngokubanzi ukuze isetshenziswe ekukhiqizeni isofthiwe yakho. Nokho, ukucubungula inqubo ye-processing kuncike ukuhlaziywa kwezinhlelo zebhizinisi ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende ngamakhasimende. Uma inqubo enkulu futhi unayo abaninzi abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli abalandeli. Njengoba umzekelo, ngithole isibonelo se-custom-made prioritization method kanye ne-problems eyenziwa nge-approximation. Ngemuva kwalokho, thina siphindeza ku-MoSCoW method decomposition ukuze ukuthatha isikhokelo se-priority ngama-examples. Umbhalo ungayisiza kubasebenzisi we-product managers noma wonke umbhali abalandeli inqubo yokuthuthukiswa kwama-product. Ukubuyekeza nge-custom-made approach ku-priority item Ngemva kweminyaka emininzi, kwelinye iqembu le-product, sinikezela ukulungiselela inkinga nge-priority item eminyakeni yethu yokuthuthukiswa. I-process ngokulinganisa kakhulu: izinsuku zokusebenza zithunyelwe ngokuvamile, iqembu kufanele isebenze izinsuku ezingenalutho, futhi imizila ye-product ayikho izinga eliphakeme. Kule isikhathi sikusebenzisa izigaba ezincinane ze-1-2-3-4 futhi akuyosiza ngokuphelele. Ngemuva kwalokho sikusungula ukulungiselela ukuxhumana phakathi kwamakhemikhali kanye nokuvumela i-priority eyengeziwe "5". Lezi zikhokelela ku-priority ephakeme, engaphezu kwe-"1", futhi inikeza "showstopper" - i-ticket noma item eyenziwe ngokushesha, Why is “5” more important than “1”? Because historically we had myriad priority “1” items, and “0” was used for the tasks that had to be prioritised later. Changing the meaning of “0” means a thoughtful review of the entire backlog, implementation of some migration, and nobody wanted to do it. How does it happen that we have so many priority “1” tasks in the iteration that we have to introduce an additional priority? And what is the purpose of 2-3-4? These are the most important questions that show the process immaturity, because team members had no idea what the difference was between 2-3-4. All these tasks were just “optional”. How do we explain these illogical rules to new team members? These rules were impossible to explain, and this improvement didn’t help to make things right. Ngokuvamile, inqubo yokubhalisa kwama-priority akuyona inkinga elikhulu kuleli mkhuba. Kukho imibuzo eziyinhloko emkhakheni yokubhalisa, ukulawula ingozi kanye ne-strateji ngokuvamile. Kodwa uma unemibuzo emininzi embhedeni yakho, ukufundisa inqubo yakho emangalisayo akuyona ingqondo engcono. Ngokuvamile, ngihambe ngokushesha ukusetshenziswa kwezinga lokuphendula umsebenzi yokubhalisa ku-software development. Ukusungula indlela “MoSCoW” Ngezinye izinga zihlanganiswa ngempumelelo kwi-International Best-Practice RFCs evela kumazwe afana ne-IETF noma i-IEEE, lapho ezinye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye zibe. Ukulungiswa kwe-Dai Clegg e-book “ Imininingwane "MoSCoW" ayikho ukuxhumana ne-northern capital futhi yasungulwa njenge-acronym ye-prioritization categories: Uthande Ukulungiselela Ukulungiselela Ont Have. Lezi zihlanganisi kungase zihlanganisa izinzuzo ezimbonini 1-2-3-4 futhi kusiza ukucacisa ngokunambitheka ukuxhumana kwezinqubo noma izigaba ku-i- iteration yokukhiqiza imikhiqizo. Umthombo obucindezela we-catalogue yenza le methode enhle, futhi kule nqaku, ngithanda ukucacisa zonke izinzuzo nge izibonelo yokukhiqiza kwe-Agile. Case Method Fast-Track: A RAD Ukufinyelela M S Co W Okokuqala, kufuneka ukwakha isibonelo scenario ukusetshenziswa indlela. Ungathanda ukuthi sinama-member of a product team that is developing a B2B product. Kulesi imikhiqizo, amakhasimende ethu angakwazi ukugcina futhi ukuguqulwa amafayela yayo amaphrojekthi. Ukuze ukugcina okuhlobene, iqembu lethu uzothola izici ezisemgangathweni, ezifana “User invitation” - umsebenzi ukwandisa umdlali omtsha ku-project. Sitholela amakhasimende ethu ukuthi sinikeze lokhu izici ngexesha elifanayo; sinesibopho. Ngoku, iqembu kufuneka isitholele iteration elilandelayo yokushicilela inguqulo entsha ye-product ngaphambi kwexesha lokugcina ukubukwa kwebhizinisi. The team has the capacity - available time slots that could be used for the development. In this example, we will not segment team members by speciality (Dev, DevOps, QA), and will imagine our squad as a canonical universal Scrum team. I-user invitation scenario has prepared technical requirements, UX / I-UI. I-function iyahlukaniswa ngezinto ezisebenzayo ezingenalutho, futhi zonke lezi zindawo ziye zihlanganiswa. Thina siphinde izindleko eziholile le-function. Kuyinto isikhathi eside ukuba usebenzise indlela yokuqala, futhi ngaphandle kokuthunyelwe okuqhubekayo, sicela usahlanganyele lezi izinto. must have - 1 I-Must Have "1" priority isetshenziselwa izicelo, izici, izindawo ze-product backlog, izivakashi ze-user noma izibuko ezidingekayo zihlanganiswe ku- iteration elandelayo yokuthuthukiswa. Ngokwesibonelo, ngesikhathi sokucubungula, sinamathisane ukuthi izigaba ezithile zihlanganisa ngokusebenzisa izivakashi zebhizinisi noma zihlanganisa ngezinye izizathu zebhizinisi. Isikhathi esiyingqayizivele kuyinto ezidingekayo futhi engathengiswa. I-team kufuneka zihlanganisa kwabo, zihlanganisa izinzuzo futhi zihlanganise. Uma izihlanganisi zihlanganisa ngaphezulu kwexesha lokufinyelela, izindawo kufanele zihlanganiswe kuze kube kunokudala I-Minimal Valuable Product (MVP) ngesikhathi sok Ngokusekelwe umzekelo we-feature entsha ye-product, bheka thina ufake isicelo se- "ukukhuthaza umsebenzisi omusha ku-project". Isigaba se-"Must Have" ibonisa umsebenzi se-MVP futhi ikhiqiza umsebenzi esisodwa. Umphumela we-iteration kufanele inikeze isinyathelo esithakazelisayo kanye nezinsizakalo ezisebenzayo ye-priority ye-"1": Implement the <Invite user> button in the project users list. Develop basic functions of the “Invite user” pop-up. Send a notification to the new user with authentication instructions. Khetha - 2 I-category yesibili iyatholakala ku-"I-Must Have". Kodwa lokhu kungenzeka ukuthi sinikeze noma ukunikezela ngemva. Uma sincoma ne-client malunga ne-invitations ye-username, izici ze-MVP ziye zithunyelwa njengezinketho ezidingekayo ku-priority "1". Nokho, kukhona njalo izinzuzo ezininzi ezidingekayo zokwenza, kodwa ziye zingenakuthunyelwa ku-disclaimed scope. Nge-development stage, iqembu ingathola ezinye izinzuzo nge-tasks "Must Have", futhi izici ze-priority yesibili kufanele ziye zithunyelwe ngenxa yokuba zithunyelwe ku-MVP. Ngokwesibonelo, ku-”User invitation” umsebenzi, imikhiqizo kufanele kusiza ukufinyelela abasebenzisi ezintsha. Ku-”Must Have” priority, iqembu uzobonise isinyathelo esikhulu sokwenza kanye nokufaka. Kodwa-ke kubalulekile ukunikela imibuzo kumadivayisi wokufaka ukuthi umsebenzisi omusha uye basebenzise ngempumelelo. Ungasebenzisa imikhiqizo ngaphandle kwe-feedback, kodwa nge-notification, imikhiqizo kuyoba kakuhle futhi umadivayisi uyazi ukuthi konke kuyoba kahle. Ngakho-ke i-priority yesibili isekelwe - thina siqhathanisa inqubo yokuqala, okuyinto enhle yebhizinisi, ngokuvumelana kuphela ukuthi le feature iyatholakala. I-"Should Have" product bug iyiphi okucubungula i-scenario, kodwa kunezinye izixazululo ezingenalutho, ezokufinyelelwa kubasebenzisi obungapheliyo nezinsizakalo. Kungencono njalo ukuguqulwa kwezi bugs ngesikhathi sokuguqulwa, kodwa angakwazi ukuxhumana phakathi kwexesha elandelayo, ngenxa yokuba kunokwenzeka ukufinyelela nge-imeyili. Ngingathanda - 3 Uhlobo lo mkhuba ama-improvements noma ama-visual defects amancane abavela ngokuvamile futhi angakwazi ukwandisa ukucindezeleka kwebhizinisi ngokuvamile, kodwa akuyona okungenani okungenani noma okungenani okungenani-optional ngenxa ye-scenario. Kuyinto enhle ukuthuthukisa lezi zinto, kuphela uma izimo ze-"Must Have" noma "Should Have" iziqinisekiso zihlukaniswe. Ngesikhathi sokucubungula, iqembu le-product kufanele akufanele izinto ze-"Could Have" njengoba lokhu: izici lokuqala kufanele ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye ziye z Ngokwesimo se-"User Invitation" umsebenzi, lokuqala lokuqala kuyinto izinzuzo ezengeziwe ezivela ku-invitation ye-user. Ngokwesimo se-priority yesithathu, umlawuli angakwazi ukucubungula ama-notifications okuzenzakalelayo uma umsebenzisi awukwazi ukuxhumana phakathi kwezinsuku ezintathu ezilandelayo. Umlawuli we-project angakwazi ukuxhumana okuzenzakalelayo uma akufanele ukuncintisana ukuxhumana kwe-priority yesibili, kodwa kubalulekile ukufaka ama-notifications okuzenzakalelayo ekuqaleni. Ngaphandle kokusebenza okuzenzakalelayo, imikhiqizo isebenza kahle futhi ivumelanisa izimo ze-contract, okwenza ukuthi "Kuya". I-"Could Have" ibhizinisi njengomkhiqizo ibhizinisi kuyinto mayelana nemikhiqizo embi embi noma ibhizinisi ebonakalayo ebonakalayo emkhakheni embi. Lezi ibhizinisi angakwazi ukuguqulwa uma asikho izici ezingenalutho noma ibhizinisi yemikhiqizo eminye izigaba. Ibhizinisi we-Priority ibhizinisi angakwazi ukuguqulwa ku-i-iteration elandelayo ngaphandle kokubambisana eside, ngoba akuyona ukuchithwa kwe-product. Ngokwesibonelo, iningi lamakhasimende ethu isebenzisa i-web browsers ku-engine eyodwa futhi sinezinguquko esincane ku-engine ebonakalayo. Kuyinto enhle ukuguqulwa lokhu ibhizinisi, kodwa uma wonke umkhakha ibhizin Ukukhetha - 4 Isigaba esebenzayo esibonisa izindawo ezivamile ezivumelanayo ngesikhathi sokuguqulwa. Nokho, kubalulekile ukuba zihlole uma kukhona izinga elizayo. Iqela le-product ingathanda izigaba zokuguqulwa kanye nezinsizakalo kanye nemibuzo njengama-priority yokuqala, yesibini kanye ne-third. Futhi kunikeza ukuthi izinsizakalo zihlukile kakhulu kunezimende. Abacwaningi zithole isikhathi esizayo okuyinto ingasetshenziswa ku-priority yesibini. Lezi izigaba zihlukile ngokuvamile zihlukile futhi akufanele ukuba zihlukile ku-iteration esilandelayo, kodwa lokhu kusiza izinto ngezikhathi esilandelayo. Yintoni izigaba zokusebenza zihlukile njenge "Won't Have" backlog? Okokuqala, kukhona izivakashi zobuchwepheshe. Izinzuzo ezibalulekile kakhulu zingase ziye “Must Have” noma “Should Have” isikhokelo kanye, kodwa izinzuzo ezivamile ze-code yokusebenza kwebhasi ye-codebase zihlanganisa kakhulu isikhokelo se-priority ye-fourth. I-developer has a chance to improve the code after the business-crucial tasks and use these improvements in the next iterations. Uma ezinye izinzuzo zihlanganisa futhi zihlanganisa ukusebenza kwe-QA engaphandle, ukwenza izinzuzo ngaphambi kwe-i-iterations ezintsha futhi inikeza amathuba yokuhlanganisa ngokushesha. Ngaphezu kwalokho, kubalulekile ukongeza njengoba “Won’t have” priority ezinye izindawo ezingenalutho “Must Have” priority yokuqala ku iteration elandelayo. Sithanda ukuthi ngemuva kokufaka isebenzisa isisekelo, kufanele ukwandisa izinga lokuzikhethela abasebenzisi esifundeni lokhu, ukuze ukunciphise ukusetshenziswa kwe-administrator. Lesi sici kuyoba MVP ye iteration elandelayo. Uma sinezinguquko, kubalulekile ukuqala ukuthuthukiswa njenge-priority ye-fourth; okuyinto izinga ukunciphisa izimo ezilandelayo. Nge-planning ye-iteration elandelayo, isikhokelo se-must have iyahlaziywa ku-must have. Kuyinto engcono ukuba akufanele ama-bugs yemikhiqizo ye-priority yesibili, ngenxa yokuba le-category ibonisa ukuthi le bug akufanele ukuguqulwa ngexesha lokuguqulwa futhi akufinyelela kuphela ukuguqulwa okwengeziwe ku-backlog board. Nokho, ukuguqulwa kwe-priority ingasetshenziselwa ama-bugs ezidingekayo zokuguqulwa kwe-architectural ezinzima ku-iteration yamanje futhi ukuhlolwa kwabo kufanele ifakwe ku-iteration elandelayo. Nokho, izinga lokuqala le-catalogue kuyinto – wonke umuntu uyazi ukuthi lokhu kokuguqulwa akufanele ifakwe ku-iteration yamanje futhi lokhu kusiza ukuguqulwa kwe-product ngcono kakhulu. Izinzuzo ze-Using Priority Approach I-general one - lokhu kuyinto ukucaciswa okuhlobene kwama-priorities. Ekupheleni le nqaku, ngifake isibonelo se-priority-made nge-catalogue ezine, okuyinto ayikho nomntu wabheka futhi iqembu kufanele uvumela i-priority ye-fifth for the most important tasks. Umgangatho we-MoSCoW ukuguqulwa lokhu ukuxhaswa futhi inikeza izinhlelo ezincinane ukuthi abalandeli be-team akufanele ukwenza elandelayo. Lezi zinsizakalo zihlanganisa njenge-team benchmark futhi inikeza ukubonisa imibuzo emkhakheni yokuhlanganisa i-team. Ngokwesibonelo, uma iqembu asikwazi ukuvelisa zonke izindawo ezivamile ze-priority yokuqala ye-Must Have, ngaphandle kokuzihlanganisa kwezinye izigaba ezivamile, kubonisa imiphumela enhle ekusebenzeni: Imininingwane ze-feature ayikho kakhulu futhi elula. Kuyinto ingxaki ku-function decomposition. I-team ngokufanayo i-underestimated i-complexity ye-tasks. Umntu waqala ukuguqulwa umqondo ngesikhathi sokuguqulwa. I-team kufuneka ukunikezele ukubuyekeza kanye nokufunda isisindo se-problem kanye nokufumana isixazululo yokuguqulwa kwe-development process. Ngemva kweminyaka embalwa embalwa, inqubo kufanele lula. Ngezinye, ukufinyelela okuqhubekayo kwe-priority ye-third kanye ne-fourth ayikho kakhulu. Lokhu kubalulekile ukuba sinamathela kahle nokuhlakazeka nokuhlakazeka, kodwa kunikeza ukuthi iqembu lihlukile kakhulu noma i-underloaded. Mhlawumbi singathola izinto ezengeziwe ze-"Must Have" noma "Should Have" ama-priorities. Inqubo yokuthuthukiswa inikeza isilinganiso futhi izinzuzo ezithile ukugcina bonke abalandeli be-team enhle futhi bakwazi ukucindezeleka. Imibuzo ye-approximation Ngo-example etholakalayo, imisebenzi zihlanganiswa ngokuvumelana ne-priority ye-iteration eyodwa, kodwa akugqoka ku-priority jikelele ngokuvumelana ne-business yebhizinisi. Iziqu ze-Task eyenziwe njenge-"Could Have" ku-iteration elidlulile kungenzeka ukuba zibe yi-"Must Have" ku-iteration elandelayo, futhi lezi zokusebenza zihlanganisa isikhathi esizayo ngosuku lwezinsizakalo. Ngaphezu kwalokho, indlela kunezinto unemibuzo ne-sequence ye-tasks e-catalogue eyodwa. Uma i-iteration iqukethe amayunithi amancane we-"Must Have", elingu-must be-development yokuqala? Lesi-sequence kufanele ikhohlwe nge-planing ye-iteration kanye nokuhlanganiswa nge-software eyodwa. Akukho ibhola eliluhlaza ekuthuthukiseni yonke inqubo yokuthuthukiswa, kodwa ukusetshenziswa kwezindlela efana ne-MoSCoW kusiza ukunciphisa inqubo eziyisisekelo. Ukuphakama Kukho izindlela eziningi kanye izindlela zokufinyelela izinzuzo. Nokho, ndingathanda ukuthi indlela ye-MoSCoW iyinhlangano elula kakhulu ukuqala nge izinzuzo jikelele zokusebenza kwe-software. Le ndlela iyatholakala kakhulu emakethe ye-B2B kanye nokuthuthukiswa kwama-product ngokuvumelana nezinsizakalo nezimo ezivela ngokucacileyo. Kufuneka kube nenkqubo ye-iterations ezilandelayo ukuze isetshenziswe lokhu ngokufanele. Kwesimo se-chaotic ne-changing ngokushesha, le ndlela ingasebenza okungenani futhi zibonisa izinzuzo eziningi zokufinyelela okuphambili, okuhlobisa ukuhlaziywa kwe-release. I-problem efanayo ingatholakala ngaphandle kwe-planning kanye ne-estimation ez
