C O N F I D E N T I A L 4-May-15 1 Attendee Management - Being Agile Attendee Management.

Slides:



Advertisements
Similar presentations
Iteration Planning.
Advertisements

Walter Bodwell Planigle. An Introduction – Walter Bodwell First did agile at a startup in 1999 Got acquired by BMC in 2000 and spent the next 8 years.
> Sprint Planning Presentation API Release: Date: Presented by:
A little Software Engineering: Agile Software Development C Sc 335 Rick Mercer.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Agenda −Scrum with TFS 2010 using MSF for Agile 5.0 −Planning the Project −How do you plan the project? −Project planning in TFS 2010 −Planning a Sprint.
<<replace with Customer Logo>>
Release Planning – Test Role and Responsibilities Emergence Tech Training / emergencetechtraining.com.
IAgile – iNetFrame’s framework for agile development Features Get to see a working product early Development shadows evolving requirements Pair programming.
BTS530: Major Project Planning and Design Iterative Development References: Agile & Iterative Development, by Craig Larman, 2004, Addison Wesley. Agile.
Agile-Scrum in QA – Case study at TraderTools Amitay Itskovitch TraderTools LLC QA Manager Phone: ,
1 Pramerica Systems Ireland Lean Principles for Systems Development Pramerica’s Journey to eliminate waste Mary Howick 8 th October 09.
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Agile Development.
NAUG NAUG Knowledge Evening – th February 2007.
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..
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Remedy, a BMC Software company Storyboarding the User Interface: Blueprint for an Application Shanaz Kanga | Michele Sarko Sr. UI Design Engineer | Manager,
Agile Methodologies for Project Management By – Komal Mehta.
Agile/Scrum Case study Code name: ninja.  2 scrum teams  One product backlog  8 months so far  Long term project  External integrations  R&D and.
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
Trusted IT Group. The challenge: 40 active, concurrent IT projects  Unsatisfactory Project Delivery.
Sprint – Weekly cadence
How to run an effective (and fun) standup. Notes from session at Agile Open NW By Ed Kraay.
Gaining Support for a Sustainable Agile Transformation Dennis Stevens, VP Enterprise Engagements LeadingAgile November 12, 2013.
Copyright BSPIN Agile Practices Benchmarking Case Study by Cosmonet Solutions Pvt. Ltd.
Copyright 2008 Scott W. Ambler Agile Practices and Principles Survey 2008 Scott W. Ambler Michael.
Agile Software Development Brian Link
What is Scrum Process? Where is it used? How is it better?
Copyright David Churchville - XP and Agile Planning David Churchville ExtremePlanner Software XP Fishbowl.
Testing Challenges in an Agile Environment Biraj Nakarja Sogeti UK 28 th October 2009.
Release and Iteration Planning September 13, 2008.
5. Planning.
4/23/ :45 PM © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered.
EVS Product Development Life Cycle Charles Griffin 9/19/2007
Agile Concepts - II “Agile” Estimating & Planning Nupul Kukreja 5 th November, 2014.
C O N F I D E N T I A L 22-Oct-15 1 StarCite Engineering Weekly Meeting StarCite Engineering Feb 9, 2009.
Project Tracking Why and How to Do It. The Dilbert View.
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
Process Presentation Kin Wan Li, Ashley Zoch, Mevesh Gopee, Damian Ridgwell, Edwin Lusala,
Extreme Programming Based on and
What Is DevOps? DevOps is "a portmanteau of 'development' and 'operations'" and is "a software development method that stresses communications, collaboration,
Theories of Agile, Fails of Security Daniel Liber CyberArk.
What Is Agile? Agile is a group of software development methodologies Scrum Extreme Programming (XP) Lean Etc. Key Characteristics: Small increments Adaptive.
Quantifying Quality in Agile Uday Kiran Kuramana Asst. Manager – FAI Bangalore Sumanth MR SQA - FAI Bangalore Nitesh Kini QA - FAI Bangalore.
User Group Meeting 2/11/2010 – 6:00 p.m.. Meeting Agenda 1. Group Goal: To create a forum in our local area where we can exchange ideas related to agile.
Planning Extreme programming
WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ CA Agile Vision Product Manager Michael Lester.
#msdevcon Community Track IMPLEMENTATION OF SCRUM Bernardin Katić Insa Investment Software AG.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
Barnes & Noble Alonda Morgan. Agile UX Agile.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Metrics that Matter
Scrum.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
By: By: Agile Scrum Master Online Training.
Chapter 3: The Project Management Process Groups: A Case Study
Burn Down charts for Project Management
Burn Down charts for Project Management
Summarizing Our Models to Date
Scrum - Plan a Sprint Great Video (but added release /sprint layer)
Quality Assurance in an Agile Development Team Michelle Wu 2018 PNSQC
Training 01: Project Lifecycle & Business Technology Analysis
Software Development In Agile
Scrum in Action.
Adapting Agile in Pharmaceutical Industries
Software Development In Agile
Presentation transcript:

C O N F I D E N T I A L 4-May-15 1 Attendee Management - Being Agile Attendee Management

C O N F I D E N T I A L 4-May-15 2 Agenda New steps towards Agile Benefits Challenges Support

C O N F I D E N T I A L 4-May-15 3 New Steps towards Agile Scope management – Single list for everything to-be accomplished – Rank every story (Dev, Support, hot-fix, DR testing) in that iteration – Trade off calls much easier (All dependencies encapsulated in story points) Capacity planning – Focus factor helps depict accurate capacity Unit of measure – DAILY (Check-in DAILY, Write Test Cases DAILY, Build DAILY, Validate DAILY) Daily Standup meeting – Review burn down chart DAILY – High visibility – Call out risks daily No “I” in team – DEV+QA – Requirements, Planning & Estimation – Team decides – Load balance development tasks & QA tasks

C O N F I D E N T I A L 4-May-15 4 New Steps towards Agile – Cont. Communication – Face to face, Pick up the phone & Finally, ! – Every story DEV+QA sync up DAILY Weekly Testing – DEV+QA spend an hour weekly – Regression, Functional (Team decides areas to test) Brain storm meeting before sprint planning

C O N F I D E N T I A L 4-May-15 5 Benefits Improved DEV+QA partnership Communication – Logistics resolved in daily standup call or on phone Sense of ownership – Solution driven team Leaders emerge in Team – Driving Sales Force Project – Event Marketing – Design/IT co-ordination – PCI Compliance – DM effort + Release Management – QA Automation

C O N F I D E N T I A L 4-May-15 6 Benefits (Cont.) Improved Quality (10 day before + after release comparison)

C O N F I D E N T I A L 4-May-15 7 Challenges Product management involvement – Lock down release & scope early – Mockups & details in stories Pursuit of perfection – Need to work on discipline of doing things – DAILY (Ex: Rally update) Environments – Need performance environment – Existing environment upgrade Bug tracking – Rally & Test track have to be kept in sync

C O N F I D E N T I A L 4-May-15 8 Support One Team – Support + Development Load balance support issues within team Encourages ownership Customer usage visibility – Helps correct test cases + better coding practices Challenges – Support load affects committed deliverables for sprint

C O N F I D E N T I A L 4-May-15 9 Q & A