Scrum is an agile methodology to manage and control software development where change occurs rapidly (changing requirements, changing technology). Here focus area is on improved communication and maximizing cooperation. Scrum Roles – Product Owner -A Product manager who actually knows what needs to be built and in what sequence this should be done. Scrum Master – This role is played by a project manager or team leader who is responsible for enacting scrum values and practices. Scrum Team – A small team of 4-5 team members (contains programmers, UI designers, testers etc.) Scrum Activities – Project Kick off Meeting – A collaborative meeting in the beginning of the project Participants: Product Owner, Scrum Master Purpose: Create the Product Backlog. Sprint Planning Meeting – A collaborative meeting in the beginning of each Sprint Participants: Product Owner, Scrum Master and Scrum Team Purpose: Create the Sprint Backlog. Sprint – An iteration… Read more“Scrum – Agile Methodology”
Category: Software Development
Difference between Scrum and XP (Extreme Programming)
There are small but important differences between Scrum and XP (Extreme Programming). These methodologies are definitely much aligned. In fact, if you have to choose between these two then it’s very difficult? Below are some important differences between these two, Scrum teams typically work in iterations (called sprints) that are from two weeks to one month long. XP teams typically work in iterations that are one or two weeks long. Scrum does not define how to do development, but many Scrum teams implement many of the XP practices. Scrum focuses on structured sprints, and prioritizes back log items. Moreover focuses of XP are more on paired programming, prioritizing the tasks, and more test driven development. Scrum teams do not allow changes into their sprints. Once the sprint planning meeting is completed and a commitment made to deliver a set of product backlog items, that set of items… Read more“Difference between Scrum and XP (Extreme Programming)”
Test Driven Development
TDD is just about writing the test before the program. In other words, first think about “how to use” any component, why do we need this component or what’s it for? And only then think “how to implement”. Hence we can say, it’s a testing techniques as well as design techniques. Below are the advantages of it, It results into components that are easy to test. It results into components that are easy to enhance and adapt. In the end, there is no code without a test. We can tell at any time, whether everything still works as it should, or what exactly does no longer work as it once did. Complex things won’t fear us, execute the test and get positive feedback. You can re-use the unit test in accessing the performance of your system early stage of software lifecycles. Why test first? The test is the executable specification…. Read more“Test Driven Development”