SCRUM VS EXTREME PROGRAMMING - WE TRIED THEM BOTH

agile software development is all about incrementally delivering quality software to businesses today we are reviewing two agile methodologies scrum and extreme programming both of them build on top of certain principles and provide clear guidelines to product development so what is the scrum methodology scrum has a simple and circular process with two constant elements of inspection and adaptation the first is creating and maintaining ruthlessly order to-do lists known as product backlogs the second element refers to prioritizing items dedicated to different steps in short time periods a scrum team consists of a product owner scrum master and development team the role of the product owner is to translate the customer's goals back to the team a scrum master is the facilitator for a team clearing obstacles and ensuring good working relationships the team works on the development and testing of every high priority item through seven steps requirements formulation ui ux design development full testing integration documentation and final approval projects are tangibly built increment by increment these tangible increments are then showcased to stakeholders for feedback the new requirements generated by their feedback are placed in the product backlog and prioritized according to existing tasks this is called the scrum cycle to ensure ongoing communication there are daily scrums which is a 15 minute daily internal meeting don't you just hate those meetings share what you think in the comments next sprint planning meeting is used to plan the work that needs to be performed during the sprint a sprint review meeting is done at the end of the sprint to assess the achievements during the sprint and what should be done in the next sprint scrum can be used on any complex project it specifically benefits the projects with cross-functional teams without constant interruptions from everyday business activities that require a quick feedback loop that use stakeholders feedback to prioritize tasks for the next sprint now let's move on to extreme programming extreme programming xp is a lightweight efficient flexible way to develop software it derives its name from taking elements of traditional software engineering practices to extreme levels xp is based on specific planning approach on-site customer and continuous testing extreme programming takes traditional principles to extreme levels through a number of practices the xp practices include simple design pair programming constant testing ongoing integration refactoring coding standards and small releases let's clear up some of the terms pair programming is the practice of having two people simultaneously working together on all production code continuous integration is the practice of integrating the system several times per day every time a task is completed by a developer pair integration in xp is supported by tests like unit testing and functional testing refactoring in xp is the practice of restructuring a program or implementing a feature without changing the behavior of the system xp projects have three phases namely the release planning phase iteration phase and the release phase in the release planning phase the customer writes stories based on requirements the programmers estimate them and the customer chooses the order in which stories will be developed in the iteration phase the customer writes tests and answers questions while the developers develop software according to the stories the iteration phase provides ready to go software thirdly in the release phase the programmers install the software and the customer approves the result xp works best for small to mid-sized teams developing software working in the midst of vague or fast-changing requirements would you like to learn more about the product development process check out the link in the description box so what do xp and scrum have in common both scrum and extreme programming divide the development process into sprints have a planning meeting before the development starts and pinpoint user stories during such meetings they also both imply having a planning meeting before each sprint as well their goals are similar what is the difference between scrum and xp the main difference is their primary focus scrum is heavily focused on management itself it deals with the activity done besides coding as it does not give much technical and engineering emphasis on how work is actually done or how a product is actually built on the other hand extreme programming concentrates programming and coding and the test driven approach sprints are a bit different too scrum sprints last for two to four weeks and their length is quite flexible under xp however there are shorter iterations of one sometimes two weeks to develop a working system the aim of an xp sprint is not focused on product release but on creating a working bug-free system in turn scrum sprints are supposed to result in a working product xp is more flexible when it comes to changes unlike in scrum changes can be made by the customer during the sprint itself when it comes to prioritizing tasks in scrum developers determine the order of their actions themselves in xp teams follow strict orders according to priority and requirement the two frameworks discussed scrum and xp both focus on delivering a high quality product to the customer as fast as possible there is no universally best framework suitable for all cases each of them has its pros cons and use cases if you don't know how to settle on just one framework what you can do is combine scrum and xp if you don't know from where to start contact jelvix and we will help you implement your idea into life we provide consulting software development and design service to top businesses and enterprises thank you for watching our video subscribe to our channel hit the bell button and don't forget to like this video you

Channel: Jelvix | TECH IN 5 MINUTES

Views: 70,000

Keywords: scrum, agile, extreme programming, extreme development, scrum vs extreme programmming, extreme programming vs scrum, agile vs scrum, scrum vs xp, xp vs scrum, agile vs xp, xp vs agile, agile scrum, agile extreme programming, agile project management, agile software development, scrum software development, pm, sprints, sprint cycle, agile frameworks, best agile frameworks, agile or scrum, scrum or xp, scrum rules, agile projects, techtips, scrum master, scrum agile

Id: PRYmsmMdlko

Length: 6min 38sec (398 seconds)

Published: Thu Sep 17 2020