AGILE PROCESS

  1. TASKS - Tasks are simply the actions performed to complete the steps as mentioned in epics and stories.
  2. PRODUCT OWNER-Main man who gathers the requirements from Customers/Stakeholders in a proper way and provides this requirements(in the form of EPICS and Stories) as a input to the team.They actually don’t know about the implementation of the project.But supervises the overall status of the project. Every release should satisfy the product owner. Team should again start working from the scratch to build the product once again if it is being rejected by the product owner.
  3. SCRUM MASTER- They are the ones who work closely among all the teams .But does not gets involved in the actual process.
  4. SCRUM TEAM- Developers and Testers are collectively referred as scrum team.
  1. There is no need for the customer to wait for the entire software.After receiving the sprint there will be a chance to include the changes felt by the customer in the upcoming sprints.
  2. Frequent release of software.
  3. It is considered to be very useful in customer point of view.
  4. Saves lots of quality time and less cost.

--

--

--

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

My Contribution to implement the CI-CD in my current organization.

Technical Guide, Part 1: Compiling Hermes for Apple Platforms

Technical Guide, Part 1: Compiling Hermes for Apple Platforms

An Apple a Day

Mist NFT — Gameplay Footage and Weekly Recap #7

http://ift.tt/2oiyyiI…

C++ Basics: Understanding Object Model

Crust Project Development

139. Word Break

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Kavinaya M

Kavinaya M

More from Medium

What you need to know about Scrum — Part II Scrum Theory

Agile SDLC — Software Development Life Cycle #2

Reasons Why Agile Fails and How to Fix It

Good Scrum Master vs. Great Scrum Master