Team Assignment 3 Team 4 – K15T2 Present. Introduce to project Goal of project Profitable for Honda Vietnam Company. Improved working process. Increases.

Slides:



Advertisements
Similar presentations
© Copyright 2006 FPT Software 1 © FPT SOFTWARE – TRAINING MATERIAL – Internal use 04e-BM/NS/HDCV/FSOFT v2/3 How to work in Fsoft project Authors: KienNT.
Advertisements

Homework 3 Solution Lecture Packet 16 © John W. Brackett.
Scrum in 10 slides.
Delivering Enterprise Projects Using Agile Methods Brent Barton May 23, 2006.
Steve Collins Richland County IT Manager Agile.  Have Fun  Learn About Agile  Tell Some Stories.
Ni.com Introduction to Agile and Scrum Speaker/Author: Paul Packebush Section Manager, Corporate Metrology Author:Logan Kunitz Staff Calibration Engineer.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
THE EVOLUTIONARY CONTRACT MODEL The Scrum Gathering, London 11 October 2011 Susan Atkinson Legal Director gallenalliance Solicitors.
Agile Project Management with Scrum
Agile-Scrum in QA – Case study at TraderTools Amitay Itskovitch TraderTools LLC QA Manager Phone: ,
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Project Management with TFS 1. What TFS offers for Project Management? Work Item tracking 2 Portfolio backlog Backlog Issue tracking Feature Product Backlog.
© Timothy Korson Page 1 Scrum by Dr. Korson For CPTR 209 Software Engineering Version
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
Rules of the Game  Loosely based upon the TV show, “Who wants to be a millionaire.®”  Once the question is read, you will have 30 seconds to discuss.
Project Closure Report Basker George. Project Closure When does a project end? Does it end when the software has been delivered to customer & acceptance-tested?
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Paweł Słowikowski What can Agility do for YOU. Who am I Have been: Software tester Verification Project Manager Scrum Master Agile Coach Currently: Scrum.
Chapter 14. To understand the process of project audit To recognize the value of an audit to project management To determine when to terminate a project.
Team assignment 13 TEAM 3 – K15T1 Hanh Luong – Leader – T Hao Tran – T Huy Nguyen – T Hieu Le – T Quang Nguyen – T
© 2005 Prentice Hall14-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
CSE G674/2009 Project Project Management Section Presented by: Amir Aref Adib.
What is Scrum Process? Where is it used? How is it better?
Alcatel-Lucent CDC Workshop, Coaching & Knowledge Transfer Project Management.
Applying the Inspection Process. What Software Artifacts Are Candidates for Inspection? Software Requirements Software Designs Code Test Plans.
Software Inspections. Defect Removal Efficiency The number of defects found prior to releasing a product divided by The number of defects found prior.
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
Sri Lanka Institute of Information Technology Software Engineering Project – I Clone of Rally GROUP NO : WD-SEP-002 | PROJECT NO :25 PROJECT : CLONE OF.
When is Agile the Best Project Management Method? Lana Tylka.
Scrum Practices Sprint-2. Agenda Scrum Master Product Backlog Scrum Teams Daily Scrum Meeting Sprint Planning Meeting Sprint Sprint Review.
© 2013 Scrum Inc. Burndown Chart Makes Team’s Velocity and its Implications Visible Sprint/Time Points Sprint/Time Points.
Webster Visualize Webster Financial Team Visual Scrumware Joe Andrusyszyn Mark Bryant Brian Hannan Robert Songer.
Software Project Management Team 04 – K15T2. Content Summarizing your view on “Software development process”. Answer 3 question: ◦ What is Software Development.
Ch 4 - Learning Objectives Scope Management You should be able to: n Discuss the relationship between scope and project failure n Describe how strategic.
Project Tracking Why and How to Do It. The Dilbert View.
Company LOGO Team assignment 03 Team 04 K15T02. Members… 1.Hoàng Thị Kim Dâng 2.Thái Thanh Nhã 3.Trần Thị Mộng Hà 4.Trần Tiễn Hưng 5.Chu Thị Thu Hương.
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.
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.
LOGO FINAL STATUS REPORT ORDER FOOD ONLINE PROJECT Copy right by © Team 3 – K15T1.
PAGE 1 Company Proprietary and Confidential R&D Project Proposal Student Management Information System January 10, 2012.
1. What do you understand by software engineering? Discuss the role of engineering software development. 2. What do you understand by software requirement.
Agile Metrics It’s Not All That Complicated. © 2011 VersionOne 2 Welcome – About your Trainer, Katia Sullivan VersionOne Product Trainer and Agile Coach.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Team Assignment 3 Team 4 – K15T2 Present. Introduce to project Goal of project Profitable for Honda Vietnam Company. Improved working process. Increases.
Software Testing Process
2012 Agile Conference 黃郁哲 Overciming Traditional Project Release Reporting with an Agile Approach Focused on Change.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
Team assignment 13 TEAM 3 – K15T1 Hanh Luong – Leader – T Hao Tran – T Huy Nguyen – T Hieu Le – T Quang Nguyen – T
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
Introduction to Software Engineering Muhammad Nasir Agile Software Development(2)
Industrial Software Development Process Bashar Ahmad RISC Software GmbH.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Project Management with VSTS
Managing the Project Lifecycle
Testing More In CS430.
Agile Software Development Brian Moseley.
Information Technology Project Management – Fifth Edition
AGILE METHODOLOGY MANAGE PROJECT USING AGILE SCRUM.
Summarizing Our Models to Date
Formulation of Abstract Machine for SPM Based on Finite State Machine
Scrum - Plan a Sprint Great Video (but added release /sprint layer)
Sprint Planning April 2018.
Chapter # 4 Development and Quality Plans
Scrum in Action.
Agile, Scrum and CMMI Methodologies
Presentation transcript:

Team Assignment 3 Team 4 – K15T2 Present

Introduce to project Goal of project Profitable for Honda Vietnam Company. Improved working process. Increases the friendly, quality customer service of Honda Vietnam. Uses less than human. reference profile, pricing, reports... fast and accurately, saving work time.

Introduce to project Project deliveries Source code Product backlog Sprint backlog Srs, sds Project plan Test plan

Project organizer Scrum process support to develop the complex products,rapid- prototyping project. There are 3 basic element in scrum: –Clear –Inspectable –Flexible

Change Management

Risk Management No. Risk Product Backlog 1 Missing requirement analysis 2 Classification priority is not reasonable Sprint Backlog 3 Estimated time and costs are unreasonable 4 Division of power not just to members 5 Divide the work for each sprint is not good 6 Done wrong burn – down chart and WBS Sprint 7 Members not in accordance with customer requirements or the provisions of the group 8 Code of regulations 9 Analysis of design errors 10 Failure to comply with working procedures 11 The members are sick 12 Products made have not been thoroughly tested 13 Products do not integrate 14 Members not able to take on multiple roles Release package of software for customer 15 Customer feels dissatisfaction 16 Product doesn’t deliver on time 17 Products are too many errors and have to rework

Roles

Work Packages Account Management Customer’s Information Management Motor’s Information Management Motor Category’s Information Management Period Warranty Management and SMS

Schedule

Thanks for your listening