Software Development In Agile

Slides:



Advertisements
Similar presentations
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Advertisements

Agile Development.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
Agile development By Sam Chamberlain. First a bit of history..
GAI Proprietary Information
Stepan Potiyenko ISS Sr.SW Developer.
Managing a Project Using an Agile Approach and the PMBOK® Guide
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
CBIIT Quality Assurance and Compliance Process August 8, 2012.
Trusted IT Group. The challenge: 40 active, concurrent IT projects  Unsatisfactory Project Delivery.
Adopting Agile for Enterprise Software Joe Bedell, Software Engineer Jason Breen, Software Engineer Peter Melko, Scrum Master June 15 th, 2015.
© 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Deeper Dive Into: User Stories.
What is Scrum Process? Where is it used? How is it better?
Scrum’s Product Owner Role Jeff Patton Agile Product Design
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
© Blackboard, Inc. All rights reserved. Back to the Feature: An Agile, User-centric Software Development Lifecycle Cindy Barry Senior Product Manager Martha.
Software Testing Life Cycle
Alcatel-Lucent CDC Workshop, Coaching & Knowledge Transfer Project Management.
Agile Methodologies: Comparative Study and Future Direction 林佳蓁 資工 4B.
Rapid software development 1. Topics covered Agile methods Extreme programming Rapid application development Software prototyping 2.
Computer Science and Software Engineering© 2014 Project Lead The Way, Inc. Software Design Process.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
Traditional Process Models A quick overview. 2 Waterfall Model (Diagram) Communication Project initiation Requirements gathering Planning Estimating Scheduling.
Agile Metrics It’s Not All That Complicated. © 2011 VersionOne 2 Welcome – About your Trainer, Katia Sullivan VersionOne Product Trainer and Agile Coach.
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
PI2134 Software Engineering IT Telkom.  Layered technology  Software Process  Generic Process (by Pressman)  Fundamental activities (by Sommerville)
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Agile Development Chapter 10 - part 2. Agile Philosophy  A guiding philosophy and set of guidelines for : developing information systems in an unknown,
PDM-Project Delivery Methodology iDeaWORKS Journey from Good to Great Version: 1.0 Date: Feb 27, 2012.
Systems Development Life Cycle
Introduction to Agile. Introduction Who is this guy?
Software Quality Assurance Chip Ene, February 14, 2015.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
Barnes & Noble Alonda Morgan. Agile UX Agile.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Approaches to Systems Development
Agile Metrics that Matter
Scrum.
Appendix B Agile Methodologies
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Wael Ellithy, Ph.D. Arx ICT
Agile Training – Agile Overview
Agile Scrum Management
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Fundamentals of Business Analysis
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Information Technology Project Management – Fifth Edition
By: By: Agile Scrum Master Online Training.
SAFe Workshop - Oct 17 Presenter: Ray Brederode
Project & Program Governance
Product Backlog List of things that needs to be done to make the product come into existence 
Chapter 3: The Project Management Process Groups: A Case Study
Approaches to Systems Development
Software Engineering (CSI 321)
Modernization Effort Same basic functionality
CEN 4010 Intro to Software Engineering Professor Alex Roque
Project Management and the Agile Manifesto
Johanna Rothman Agile Team Measurements Chapter 12
Summarizing Our Models to Date
Agile practices for documentation teams
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Engineering Processes
Extreme Programming.
Software Development In Agile
SDLC (Software Development Life Cycle) Role Play
Presentation transcript:

Software Development In Agile Copyright 2016 © 108 ideaspace inc. All Rights Reserved.

Index What is Agile Team Structure Project Structure Facts about Agile Success Factor in Agile How Cycle Works in Agile Responsibilities against Roles Q&A

What is Agile? Agile SDLC model is a combination of iterative and incremental process models with focus on process adaptability and customer satisfaction by rapid delivery of working software product.  Agile Methods break the product into small incremental builds. These builds are provided in iterations. In agile the tasks are divided to time boxes (small time frames) to deliver specific features for a release.

Team Structure Project Owner (Scrum Master) BA (Business Analyst) Developers QA (Quality Assurance) Customer/ Client

Project Structure Project Sprint 1 Story 1 2-3 weeks Story 2 Sprint 1 Demo/Delivery Story 3 Sprint 2 Story 1 2-3 weeks Story 2 Sprint 2 Demo/Delivery Sprint 3 Story 1 2-3 weeks Story 2 Sprint 3 Demo/Delivery Cont.…..

Facts about Agile

Success Factors in Agile Communication Internal/External Feedback, Suggestions external / internal Planning Abilities Responsibilities Punctuality

How Cycle Works in Agile Week 1 Dev. Team :- Req Analysis (Sprint1), Story creation, allocation, Scheduling, Suggestions, Prepare development base. QA: - Req. Analysis, Review Project scope, Test Planning, Review Sprint stories for plan test. Week 2 Dev. Team - Start development according to stories planning QA - Start Test Cases generation, Test case Review and Rework Week 3 Dev. Team: Finish Development and Work on defects reported by QA QA: Test Execution, Defect Reporting, Retesting & Close all open issues. PM / SM : Internal Demo/ Client Demo

Responsibilities against Roles Business Analyst (BA) First point of contact for client, Scrum Master, QA. Responsibilities: Requirements Elicitation (gathering, understanding, reviewing, and articulating the needs of the stakeholders) Analysis (checking for consistency and completeness) Specification (documenting the requirements) Validation (making sure the specified requirements are correct) Locking (Project sign off)

Responsibilities against Roles Project Owner/ Scrum Master First point of contact for Development team , QA. Responsibilities: Facilitates Sprint Planning, Review & Retrospective Finds and works to remove roadblocks Responsible for keeping release/project information consolidated, organized and up to date Facilitates communication between roles for every aspect of the project Responsible for throughput (team velocity) Drives the execution of sprint items

Responsibilities against Roles Development Team Responsibilities:- Estimates size of story items Translation of story items into engineering design and logical units of work (tasks) Evaluation of technical feasibility Implementation of story items Writes and verifies code which adheres to the acceptance criteria Application of product development best practices

Responsibilities against Roles QA (Quality Analyst) Responsibilities:- Writes test cases which enforce the acceptance criteria of features Keeps all test plans and cases updated to changing requirements Notifies when production is blocked due to errors in development Improving Quality Enforces QA Best Practices

Responsibilities against Roles Customer/ Client Client involvement is vital to the success of an agile project. Regular consultations between development team and clients ensure that their needs are heard regularly and that changes can be implemented earlier. Regular basis feedback from client will ensure that development going in right direction, no need to spend extra time in the end of development to made changes.

Q & A