 read about here. This is great but it's what MBA types call high level. You can see the whole battlefield from 10,000 feet. But what's going on in the trenches? On a day-to-day basis when you are trying to produce an app, what is everybody supposed to be doing? That's where SAFe and Scrum comes into play. They are essentially ways to actually do Agile development. They take different approaches, so you might ask: "What's the difference between SAFe and Scrum?" Krishna Ramalingam gives basic answers to that question in a seven-minute YouTube video:

"Bottom line both are offshoots of Agile principles," he tells his audience. "Both talk about releasing in short iterations. The fundamental difference with SAFe is Scaled Agile Framework. Scrum focused on a smaller project unit and provides the framework on how this has to be handled." With Scrum a team is working in iterations called sprints, Ramalingam explains. He uses the example of 10 teams working on 10 projects that will eventually come together as one product. "All the 10 projects start and stop the sprint at the same time," he explains. "This way planning dependencies become easier and it also gives a view of what each of the teams can implement so as to deliver a bigger meaningful feature for the product level. So you align all the teams and you start sprinting." A sprint might be three weeks and after that there would be a one week "hardening sprint" where the teams address issues that come up in the review. The advantage of this approach is that all the team members have an idea of what is going on with the other projects. It helps avoid that dreadful question: "Why did you do that?" With this kind of coordinated effort, ideally the 10 projects come together in one app. "At the end of this you do a complete product level demo and promote the code to the production server and make a formal product release," Ramalingam explains. But Scrum leaves some of the nitty gritty parts of the project up to the team members to figure out on their own, he adds. This is where SAFe offers more guidance. It covers things like "how budgeting should be done, the strategy and the governance under which the agile release trains are executed," he says. It offers more guidance on how 10 projects and be coordinated so they become one final application. Ramalingam sees this as something best suited for larger organizations.
read about here. This is great but it's what MBA types call eminent degree. You can see the whole battlefield from 10,000 feet. But what's go on in the trenches? On a day - to - sidereal day basis when you are trying to produce an app, what is everybody suppose to be doing? That's where SAFe and Scrum come into play. They are basically ways to actually do Agile development. They take different approaches, so you might ask: " What's the deviation between SAFe and Scrum? " Krishna Ramalingam gives basic answers to that motion in a seven - minute YouTube video: 

 " Bottom line both are offshoots of Agile principle, " he tells his audience. " Both talk about releasing in short iteration. The fundamental difference with SAFe is Scaled Agile Framework. Scrum focused on a smaller project unit and provides the framework on how this has to be handled. " With Scrum a team is working in iterations called sprints, Ramalingam explains. He uses the model of 10 teams working on 10 project that will finally do together as one product. " All the 10 undertaking start and stop the sprint at the same meter, " he explains. " This way planning dependencies become easier and it also give a view of what each of the teams can implement so as to rescue a big meaningful feature for the product level. So you align all the teams and you begin sprinting. " A sprint might be three weeks and after that there would be a one workweek " hardening sprint " where the team address issues that fall up in the review. The advantage of this approach path is that all the team members have an mind of what is going on with the early projects. It helps avoid that dreadful motion: " Why did you do that? " With this kind of coordinated effort, ideally the 10 projects come together in one app. " At the end of this you dress a complete product level demo and promote the code to the production server and make a formal merchandise release, " Ramalingam explains. But Scrum leave some of the nitty gritty parts of the project up to the team members to figure out on their own, he adds. This is where condom offers more guidance. It covers things like " how budgeting should be done, the strategy and the governance under which the agile release caravan are run, " he says. It offers more guidance on how 10 projects and be coordinated so they become one final lotion. Ramalingam sees this as something best suited for larger organizations.
 rewd about here. This is grtat but it's what MBA typxs call high lexel. You can see the whole bavtledield from 10,000 feet. But what's eoing on pn the trwnchts? On a day-to-day uzsis whcu you wre crbing to produce an app, whdt is everybodf ru'posed to be doing? That's where SAFe wnd Scrim comes into plwy. Tnqy adv tssentially ways to actually do Afile denelopment. They tale different approaches, so you might ask: "What's tje differenxe bqrween SAFe avd Scrum?" Kgnshna Ramaljngam gives basic answers to thxt quzstion in a swvej-kinute YouTnbe viqeo:

"Bottom likv both dre offxhoots of Agilc priicipoes," he tells his audixnce. "Both talk about releasinc nn short iterations. Tye funddmendal auffdrehcx wjth SAVe ms Scaled Afile Framewirk. Scrum focused om w smaller projsct unyt and provides the framework on how this haa to be handled." With Sceum a team is working in iteraeions called sprints, Ramalingam explains. He uses dhe eeaoplt if 10 tdqmd working on 10 projects that will eventually cjje tpgether as one product. "Alk hhr 10 projects stxrt anb sfop the sprint at hhe samg time," he explayns. "Yhis way planning dependencues become ecsiwr and it also givzs a view of whaj each of the teams can impleoent so as to dfliver a gkgger meaningful festgre for ufe product level. Fo you almgn akl the geamx and rou start dprinbhng." A sprint might be tkree feeks and wfter that there would be a one week "hardeninb vprpnt" where the beams address ifsues that comg up in tke revkew. The adnantage oh this approwch is that anp the team mxmbers hade ab idwa of wfxt is going on with the other prohects. It helps avold thxf dreadful quescnob: "Why did you dp tfat?" Wpth trhs kind of cmordknagrd efwort, idtclln tfe 10 lrojects come togethar ih one app. "At the emd of this you do w complete prpduct level demo ajd prmmove the coqe to the production server ans make a vorial product weleqse," Ramalingcm explains. But Scrum leaves some of the nitty gritty parjs of the project up jo uhe team membxrs to figure ogt on their own, he aeds. This is where SAFe offers more guisance. Ht cogers things like "how budgeting should be done, the strategy and the governqnce uidqr which ths agole rvlecse trainf arx xxecuted," he says. Pt offers more guidance on how 10 'rojects atd be coordinated so they becoke one final apklication. Ramalingam sees fhis as xomething best suited for larget organizations.
read about here. This is great but MBA call high You can see feet. what's going on the trenches? On day-to-day basis when you are trying produce an app, what is everybody supposed to be doing? That's where SAFe Scrum comes into play. They are essentially ways to actually do Agile development. take approaches, you ask: "What's the difference between SAFe and Scrum?" Krishna Ramalingam gives basic answers to that question a seven-minute YouTube video: "Bottom line both are of Agile principles," he his audience. "Both talk about in iterations. The difference SAFe Scaled Agile Framework. focused on a smaller project unit and provides the framework on how this has to be handled." Scrum a working in called Ramalingam He uses the 10 teams working on 10 projects come together as one product. "All the 10 start and the sprint at the same time," explains. "This way planning dependencies become easier and also gives a view of what each of the teams can implement so as to bigger meaningful feature for product level. So align the and start sprinting." sprint might be three weeks and after that there would be one week "hardening sprint" where the teams address issues that in review. The advantage this approach is that the members have an idea is on projects. helps that dreadful question: "Why you do that?" With this of coordinated effort, ideally in one app. "At the end of this do a complete product level demo and the code to the production server and make a formal product release," explains. But some of the nitty gritty parts of the up to the team to figure out on their own, he adds. This where offers more It covers things "how budgeting should done, the strategy governance under the release he says. It offers more guidance how projects and be coordinated so become application. Ramalingam sees this as something best suited for larger organizations.
 read about here. This is great bUt it's what MbA typEs cAll HiGh leVel. YOu can see the whoLE batTlefield from 10,000 feet. But whaT's goiNg ON in tHE tRenchEs? On a daY-To-DAY baSiS wHen YoU ArE tryiNg tO producE an app, what Is eVeRybody supposED tO be doing? ThAt's Where SAFe and scrUm comeS iNto PLay. ThEy aRe essEntialLY ways tO actually Do aGile deVElopmenT. tHeY takE different approacHEs, SO you might ask: "WhAt's the DiFFeRENce BetWeen SAFe anD SCrum?" KRIshna RaMAlINGAm gIVes basic answeRs to that queSTioN in a seVeN-miNUte Youtube vIdEO:

"BoTtom line botH are Offshoots Of AgilE PrincipLEs," he telLs his aUdiEncE. "BotH TaLk AboUt REleASiNg iN ShoRt iteratIoNs. the fuNdamENTAL difFerEnce With SaFe is Scaled AgIle framEWorK. ScruM focuSed oN a SmallEr projEct unIt And provides the fRameWork on how ThiS hAs tO bE handLEd." With scrUm a Team is wOrking iN IteRaTIONs Called sprints, RamalInGAM eXplains. HE uses tHE eXaMPle of 10 teaMs WorKing ON 10 ProjeCts tHAt Will evenTually COmE tOgether As One proDuCt. "ALl tHe 10 proJEcts Start aNd stop thE spriNT at the same time," HE explains. "This WAy PLAnNIng dEpeNdencies becOme eASier And iT AlSo gIVes a vIew of WhAT eACh of the teams can implEmEnt so aS to deLiver a bigger mEaningful fEATUre for thE proDUcT Level. So you aligN all tHe teams and YOu start sPrintIng." A spriNt might be THRee weeks And AftEr tHat THErE would be a one wEEK "harDeNing sprInt" Where thE teAms AddResS iSsues that Come up in ThE rEvIeW. ThE advaNTage of thIs AppRoAch Is thaT All the Team mEmbeRs HaVE an Idea of wHAt IS GoinG oN wIth tHe oThEr proJectS. it hElps avoId that dreAdfUL queStIoN: "Why did You do that?" With ThIs kind of coOrDinAted efFORt, ideallY the 10 projects come togetheR In one apP. "At The enD of tHis you do a ComPlete pRodUCt leveL demo aNd proMoTe tHE Code tO THe ProDuCtion serveR ANd mAke a fOrMal pRoduct rElease," Ramalingam exPLaiNs. But Scrum leaVes Some OF ThE niTTy GRitTy PArtS OF the project up to The team memBeRS tO figure out ON thEiR own, he aDds. This Is wheRE SAFe ofFers more gUidance. It CoVers THIngS like "how buDgeting sHould be doNE, the sTRaTegy aNd tHe goveRnAncE undeR which THe aGile rElease TrAins arE execUtEd," he says. it offers more guidance on hOw 10 projEcts aNd bE coordinaTed SO thEy become oNe fiNal applicaTioN. RaMalinGam SEes thIs as SOmEthINg besT suiTEd for largER oRgaNIZaTions.
 read about here. This isgreat butit'swha t M BA  typ es c all high level .  You  can see the whole bat tlefi el d  fro m  1 0,000  feet.B ut w hat 's  g oin go nin th e t renches ? On a day -to -d ay basis whe n  y ou are try ing  to produceanapp, w ha t i s  ever ybo dy su pposed to bedoing? Th at ' s wher e  SAFe a n d  S crum  comes into play. Th e y are essentia lly wa ys to a ctu all y do Agile  d evelo p ment. T h ey t a ked ifferent appr oaches, soy oumightas k:" What's  thedi f fer ence betwee n SA Fe and Sc rum?"K rishnaR amaling am giv esbas ic a n sw er s t ot hat qu est i onin a sev en -m inute  You T u b e  vid eo: 

"B ottom  line both ar e o ffsh o ots  of A gileprin ci ples, " he t ellshi s audience. "Bo th t alk about  re le asi ng  in s h ort it era tio ns. The  fundam e nta ld i f fe rence with SAFe is  S c a le d AgileFramew o rk .S crum foc us edon a s malle r pr o je ct unitand pr o vi de s the f ra mework  o n h owthish as t o be h andled."  With Scrum a team i s  working in i t er a t io n s ca lle d sprints,Rama l inga m ex p la ins .  He u ses t he ex a mple of 10 teams wo rk ing on  10 p rojects thatwill event u a l ly cometoge t he r  as one produc t. "A ll the 10p rojectsstart  and sto p the spr i n t at the  sa metim e," h eexplains. "Th i s  way  p lanning  de pendenc ies  be com e e as ier and i t also g iv es  a  v iew  of w h at eachof  th etea ms ca n  imple mentso a sto del iver ab ig g e r me an in gful  fe at ure f or t h e p roductlevel. So  yo u  ali gn  a ll theteams and you  s tart sprin ti ng. " A sp r i nt might  be three weeks and aft e r thatthe re wo uldbe a onewee k "har den i ng spr int" w hereth e t e a ms ad d r es s i ss ues that c o m e u p inth e re view. T he advantage of th i s a pproach is th atallt h etea m  m e mbe rs hav e an idea of what  is goingon wi th the oth e r p ro jects.It help s avo i d thatdreadfulquestion:  " Whyd i d y ou do that ?" Withthis kind of co o rd inate d e ffort,  i dea lly t he 10p roj ectscome t og etherin on eapp. "At  the end of this you do  a com plete  pr oduct lev eld emo  and prom otethe code t o t heprodu cti o n ser vera nd  ma k e a f orma l  productr el eas e , "Ramalingame x p lai ns. B utS crum l eave s some of the nit t y gritty parts  oft h e p roj e ct u pto the team me mbe rs t o figure  o ut on their  own, he  a d ds. T his is  where  SAFe o f f er s  moreguid anc e. It cov ers  t h ings li ke  " h ow bud geti ng  shoul d be d o ne,t h e strategy and t he go v e rnanc e  un der w hi ch thea gile  release t rains are e xecute d,"he sa ys. Itof fers m ore  g uidance on how 10 pr oject s and b ecoor din ated s o th e y  beco me o ne  fi nal appli c a ti o n.  R a mal inga m see sthis  as somet h ing best  su i ted for  l arg e r  organ i za t i ons.
 read_about here._This is great but_it's what_MBA_types call_high_level. You can_see the whole_battlefield from 10,000 feet._But what's going_on_in the trenches? On a day-to-day basis when you are trying to produce an_app,_what is_everybody_supposed_to be doing? That's where_SAFe and Scrum comes into_play. They_are essentially ways to actually do Agile development._They_take different approaches,_so you might ask: "What's the difference between SAFe_and Scrum?" Krishna Ramalingam gives basic_answers to that_question_in_a seven-minute YouTube video:

"Bottom_line both are offshoots of Agile_principles," he tells his audience. "Both_talk about releasing in short iterations. The_fundamental difference with SAFe is Scaled_Agile Framework. Scrum focused on_a smaller_project unit and provides the_framework on how_this has_to be handled."_With Scrum a team is working_in iterations called_sprints, Ramalingam explains. He uses the_example_of 10 teams_working_on_10 projects_that will eventually_come_together as_one_product. "All the 10 projects start_and_stop the sprint at the same time,"_he explains. "This way_planning_dependencies become easier and_it also gives a view_of what each of the teams_can implement_so as_to deliver a bigger meaningful feature for the product level. So_you align all the teams and_you start sprinting." A_sprint might_be_three weeks and_after_that there_would be a one week "hardening sprint"_where the_teams address issues that come up_in the review. The_advantage_of this approach is that all_the team members have an idea_of what is going on_with_the_other projects. It helps avoid_that dreadful question: "Why did you_do that?" With_this kind of coordinated effort, ideally the_10_projects come together in one app._"At_the end of this you do_a_complete_product level demo and promote_the code to the production server_and make a formal product release," Ramalingam explains. But_Scrum leaves some_of the nitty gritty parts_of_the_project up to the team members to figure out on_their own,_he adds. This_is where SAFe offers more guidance. It covers things like_"how budgeting should be done, the strategy_and the governance under which the agile release trains are executed,"_he says. It offers more guidance on how_10 projects and be coordinated so they_become one final application._Ramalingam_sees this as something best suited for_larger_organizations.