Visualization and Agile Practices to the Rescue of Traditional Project Balaji.M, Srinath C HCL Technologies, Pvt, Ltd 資工碩一 103522097 林成馨.

Slides:



Advertisements
Similar presentations
SCRUM basics Julie Rudder & Claire Stewart. What is scrum (Claire) Scrum roles (Claire) Scrum rhythms and processes (Claire) How to write stories (Julie)
Advertisements

Agile Development Primer – Using Roundtable TSMS in an Agile Shop Michael G. Solomon Solomon Consulting Inc.
An Approach to Managing Projects Hadeel Elamin Lead Project Manager
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
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.
The Business Analyst Role in Agile Projects
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
A framework for describing IT Project Management Processes and Tool Set Features Enterprise Project Management Framework.
Effective Project Management: Traditional, Agile, Extreme
CSE Senior Design II Staged Delivery Instructor: Mike O’Dell.
Managing a Project Using an Agile Approach and the PMBOK® Guide
Making a Great Company a Great Business BackgroundBackground Our client is a world leader in the Entertainment industry as the premier bulk release and.
The Product Owner prioritizes the requirements or features through feedback from the Stakeholders & interaction with the core team The Team.
Kanban “Signboard”.
Modeling Kanban Scheduling in Systems of Systems Alexey Tregubov, Jo Ann Lane.
Agile Software Development Brian Link
Tuesday, June 8 th, Agile Development-Successful Delivery & Implementing Across the Enterprise.
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
資工 4A 陳怡秀 Microsoft Visual Studio’s Journey to Continuous Delivery.
Chapter 3 – Agile Software Development Pepper modification of Sommerville presentation & Colm O’hEocha – AgileInnovation Ltd presentation 1Chapter 3 Agile.
SYSTEM DYNAMICS MODELING OF AGILE CONTINUOUS DELIVERY PROCESS 資工 4A 鄭鈞輿.
LEAN for Competitive Advantage and Customer Delight – Case study of an Application Development (AD) project Agile India 資工四 黃泓霖 1.
吳仲理 Using Lean in Application Development to achieve competitive advantage and customer delight N. Balaji Ganesh, WIPRO Technologies 20/12/2013.
1 © 2011 Infosys Ltd. Pay Per Test Case Presented At STEP AUTO 2011 – ERP testing Conference – Dec 8, 2011 by Jitendra Atale, Project Manager – Package.
A technical writer’s role in software quality – an experiment Asha Mokashi, SCT Software Solutions, Bangalore.
Advancing Government through Collaboration, Education and Action Harnessing Life Events Information Sharing Team.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
Creative Disruption: A Core Systems Strategy Workshop November 3, 2011.
Basic Approach Development driven by time boxing May sacrifice requirements in order to keep schedule (time boxed) Steer project as you go based on user.
© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v
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.
Agile Metrics It’s Not All That Complicated. © 2011 VersionOne 2 Welcome – About your Trainer, Katia Sullivan VersionOne Product Trainer and Agile Coach.
Padma Satyamurthy. 12/12/20152http://lkin15.leankanban.com.
Agile Adoption G8way Health Project.
PV213 EIS in Practice: 06 – Development process 1 PV213 Enterprise Information Systems in Practice 06 – Development process.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
10 key principles of agile software development
Using Scrum to Improve Teamwork, Communication, Quality and Speed
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
Overview PRINCE Hogeschool Rotterdam. 2 Project definition  A project is a temporary organization that is created for the purpose of delivering.
Info-Tech Research Group1 Manage IT Budgets & Cost World Class Operations - Impact Workshop.
Introduction to Agile. Introduction Who is this guy?
Kanban Advanced Software Engineering Dr Nuha El-Khalili.
 Agile Project Management, Collaboration Tool-Sets & PPM Tool-Sets Presented by Tayo Akingboye PMP, PMI-ACP.
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Using Scrum to Improve Teamwork, Communication, Quality and Speed.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Barnes & Noble Alonda Morgan. Agile UX Agile.
Agile Project Management and the yin & yang of
Scrum.
Agile Training – Agile Overview
“ ” HYPERION APPLICATION OPERATION SUPPORT AOS SERVICE STREAMS
Agile Scrum Management
Testing journey in Scaled Agile Framework®
By: By: Agile Scrum Master Online Training.
Product Backlog List of things that needs to be done to make the product come into existence 
Project Management and the Agile Manifesto
How to Successfully Implement an Agile Project
Teaching slides Chapter 1.
Summarizing Our Models to Date
Introduction to Agile Blue Ocean Workshops.
Scrum Science NGSS: Engineering, Technology, Applications of Science
Scrum in Action.
Adapting Agile in Pharmaceutical Industries
Business Agile 101 Learn the basics of the agile methodology and how you and your team can take steps to apply it to your workflow.
International Institute of Business Analysis
Engaging Senior Executives
Presentation transcript:

Visualization and Agile Practices to the Rescue of Traditional Project Balaji.M, Srinath C HCL Technologies, Pvt, Ltd 資工碩一 林成馨

Outline  Abstract  Background  Approach  Feedback  Conclusions 2

Abstract  There are many projects that still follow traditional methodologies for various reasons.  While there could be barriers in adopting all Agile practices within a project, we did realize that some of the good practices can be adopted more easily as compared to others. 3

Background  Our organization partners with clients and helps them to address their IT related requirements.  A project team of 9 members distributed across UK & India locations was working on an application involving enhancements and maintenance for a large investment bank.  Goal : share how visualization and Agile practices rescued the project from depleting customer confidence and quality of service delivery 4

Approach  pain points 1.Unplanned ad-hoc work from customer resulted in team working for long hours and weekends to meet the deadlines. 2.Missing deadlines for their deliverables 3.Customer (IT) would prioritize without knowing when the work items would complete and the existing capacity of the team (Predictability) 4.Team slogged during the weekend and got burned out 5.Management and senior management was not aware of demand and capacity 6.No clarity on who is doing what (Visibility) 5 Visualization

Approach  Focused on 3 areas : Business, Teams, Management  Business  Prioritize features by highest business/end user value  ‘Drive’ the development efforts to incrementally deliver 6

Approach 1.Initial Visualization Board Setup-­To Understand the Process (Input Cadence & Delivery Cadence) 2.Individual Queue columns were created to understand the Work Items on Pipeline 3.Weekly Prioritization calls were driven with the items which are part of Input Cadence 7

Approach 4.Work Items of Complex variability were suggested to broken down to smaller requirements, to bring more clarity on the requirement and integrated in the respective Swim lanes. 8 Development UATReviewIntegration

Approach  Teams  Eliminating waste and reducing context switching  Focused on enhancing knowledge sharing  Improving collaboration  Improving Quality  Deliver Right at First Time 9

Approach 1.Address Context Switching : Team had dedicated one/two members to handle ad-hoc requests and tracked in the delivery cadence. Defining of Acceptance Criteria for each work item Definition of Done were defined in the Visualization Board to improve the quality 10

Approach 2.Daily Huddle : Team discuss blockers, new work items, new learning’s Work Items were broken down to reduce the complexity Swim lanes were created so that the complex work items would go through the stages and the work is been shared between 2 or more team members 11

Approach  Management  Focus on the value stream  ‘Drive’ Continuous Improvement  Manage impediments 12

Approach 1.Blockers with Ageing Concept helped the team to manage escalation proactively 2.Team Meetings were used to collect the status of the work items were stopped 3.Retrospection’s were conducted to decide on the Continuous Improvement areas 13

Approach  Benefit  Better transparency on existing work  Ability to plan better  Improved quality of deliverables  Better team morale  Overall improvement in work environment 14

Feedback  Customer Observations  Team Observations  Management Observations 15

Conclusions 16