Your SlideShare is downloading. ×
Agile Methodology and Tools
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile Methodology and Tools

269
views

Published on

This is my first presentation in the slide share about overview of Agile Methodology and Tools.

This is my first presentation in the slide share about overview of Agile Methodology and Tools.

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
269
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. AGILE METHODOLOGY Prepared by Naresh Gajuveni
  • 2. WHAT IS AGILE? Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.
  • 3. WHEN TO USE AGILE MODEL: you want to benefit from fast feedback and burning visibility of objective data you don't completely understand the value and definition of what you are building have a team passionate about it or a coach who will help them have complicated project without all the experts you need or a complex project
  • 4. AGILE METHODOLOGIES Scrum Extreme Programming(XP) Feature-Driven Development (FDD) Dynamic Systems Development Method (DSDM) Crystal
  • 5. SCRUM Scrum is an iterative and incremental agile software development framework for managing software projects and product or application development.
  • 6. CHARACTERISTICS OF SCRUM Scrum is one of the “agile process” Teams are self organizing in Scrum Scrum teams do a little of everything all the time rather than doing all of one thing at a time. Scrum are a series of two- to four-week “sprints” “Product backlog” is used to capture the requirements in Scrum No changes during the sprint are allowed
  • 7. ROLES AND RESPONSIBILITIES Scrum Master: Scrum Master is the keeper of the process. He is responsible for making the process run smoothly, for removing obstacles that impact productivity, and for organizing and facilitating the critical meetings. Product Owner: The Product Owner is the keeper of the requirements. He provides the “single source of truth” for the Team regarding requirements and their planned order of implementation. He is the representative of the Customer/Stakeholders.
  • 8. Team: The Team is a self-organizing and cross-functional group of people who do the hands-on work of developing and testing the product. Since the Team is responsible for producing the product, it must also have the authority to make decisions about how to perform the work.
  • 9. WHAT IS A “SPRINT“? Scrum is a series of “sprints” Every sprint lasts for 30 days or at least 2-3 weeks Sprint is more like an iteration not in characteristics but from the timing perspective All sprints in a scrum always have a constant duration During the sprint a little of everything is done all the time rather than doing all of one thing at a time. The phases like planning, design, code, and testing are all done at a same time.
  • 10. SCRUM MEETING The meetings are usually timeboxed to 5–15 minutes. The stand-up meeting is sometimes also referred to as the "stand- up", "morning roll call" or "daily scrum". The goal is to stick as closely as possible to these questions:  What did I accomplish yesterday?  What will I do today?  What obstacles are impeding my progress?
  • 11. ADVANTAGES OF AGILE:  Customer satisfaction by rapid, continuous delivery of useful software.  Working software is delivered frequently (weeks rather than months).  Close, daily cooperation between business people and developers.  Continuous attention to technical excellence and good design.  Regular adaptation to changing circumstances.  Even late changes in requirements are welcomed
  • 12. DISADVANTAGES OF AGILE:  There is lack of emphasis on necessary designing and documentation.  The project can easily get taken off track if the customer representative is not clear what final outcome that they want.  Only senior programmers are capable of taking the kind of decisions required during the development process.
  • 13. NECESSITY OF TOOLS IN AGILE PROCESS  Requirements management (product/release backlogs).  Planning (release/iteration planning).  Tracking (project/release/iteration progress tracking).  Quality Assurance (testing, bugs management).  Feedback Gathering (feedback from customers, ideas, issues).
  • 14.  User Stories and Epics management.  Backlogs prioritization.  High level release planning and low level iteration planning.  Progress tracking via virtual burn down charts, Task Board and Daily Progress.  Tests management via Test Cases support and integration with automated testing tools.  Bugs management via Bug Tracking support and integration with external bug tracking tools.  Customers’ requests management via Help Desk functionality or integration with third-party tools like Salesforce.
  • 15. SELECTING AGILE TOOLS Iterative, Feature-driven Development Integrated Life Cycle Management within One Agile Tool Cross-Functional Teams Flexible Configuration of Agile Tools Simplicity Enterprise Scale
  • 16. AGILE PROJECT MANAGEMENT TOOLS Easy Backlog Ice Scrum Agilefant Agilo RACI Flying Donut Pivotal Tracker
  • 17. ADVANTAGES OF USING AGILE TOOLS  Stakeholder Engagement  Transparency  Early and Predictable Delivery  Predictable Costs and Schedule  Allows for Change  Focusing on Business Value  Focusing on Customers  Improving Quality
  • 18. THANK YOU

×