Agile Software Development


Agile is a better way of building products which is time-bound and iterative approach to deliver software that is built incrementally from the commencement of the project, instead of trying to deliver all at once.

Why Agile?

Technology in this current era is progressing at a rate where things are changing very fast, if traditional software development methods like waterfall model are used then time to deliver software in market is slow and the market will be somewhere else after that time which will inculcate to incorporate changes but that's not possible in this model. Continuous delivery is not possible in this model.

Agile delivers modern software in iterations of waterfall, it accepts client changes and inculcates them and take feedback from the client as well as the users.

There are various frameworks of agile that implement this methodology-

  • Scrum
  • Kanban
  • Extreme Programming (XP)
These frameworks follow all principles of agile methodology. 

Scrum


A sprint is a short and fixed period generally of 1 or 2 week when a scrum team works to complete a set amount of work. Scrum goes with sprint. Sprint period is decided upon speed and skills of development team.

Scrum believes in delivering something to client after every sprint, which is potentially shippable product. This framework guarantees incremental delivery of product which can be deployed according  to client's wish.

Client doesn't know what exactly he wants initially and his requirements keep changing according to his needs and better understanding of problem, so MVP (Minimum Viable Product) is delivered, which is a version of a product with just enough features to be usable by early customers who can then provide feedback for future product development.

Product backlog will have all requirements from starting to the end.

Few requirements are collected from entire product requirements each week which go in current sprint backlog. These requirements are selected after sprint meeting.

Scrum team will work on the product, after first sprint first increment of the product is obtained. If everything planned is not completed, those tasks are set in next sprint

Sprint Retrospective comments which methods were better and involves sprint review.

Daily scrum everyday for 15 mins team will come together and discuss doing sprint review and retrospective

Development team is a cross functional and self organizing team, each member can do everything like designing, coding, testing, etc.

To know more about scrum, click here.


Comments

Post a Comment

Popular posts from this blog

JavaScript Engine

Image
JavaScript can run everywhere because of JavaScript Runtime Environment. It is like a container which has everything inside it required to run a JavaScript code. JavaScript engine is the most significant part of JSRE. All browsers have their own JSRE which helps them in executing the JS code. JavaScript Engine It is neither a software or a hardware, it is a program written in low level language. Some of the popular JS engines are -  V8 from  Google . SpiderMonkey  is developed by  Mozilla  for use in Firefox and its forks. JavaScriptCore  is  Apple's engine for its Safari browser. Chakra  is the engine of the  Internet Explorer  browser. It was also forked by Microsoft for the original Edge browser, but Edge was later rebuilt as a Chromium-based browser and thus now uses V8. JavaScript can behave like both interpreted and compiled language. It simply depends on JavaScript Engine. In case of interpreter, we have speed and in case of compiler, we have efficiency. Initially, JS wa
Read more

Make Your First Pull Request!

Image
  🤝 First time contributing? Will help you out. 👍 Refer to the following articles on the basics of Git and GitHub, in case you are stuck: Getting started with Git and GitHub Forking a Repo Cloning a Repo How to create a Pull Request If you don't have git on your machine,  install it . 💥  How to Contribute Take a look at the Existing Issues or create your own Issues! Wait for the Issue to be assigned to you after which you can start working on it. Fork the Repo and create a Branch for any Issue that you are working upon. Read the Code of Conduct Create a Pull Request which will be promptly reviewed and suggestions would be added to improve it. Add Screenshots to help knowing what this Script is all about. How to make a Pull Request If you think that you can add a new feature or want to fix a bug. You can start contributing by following the below instructions: Create a folder at your desire location (usually at your desktop). Open Git Bash Here Create a Git repository. Run command
Read more