Part 2 of the Module.

Slides:



Advertisements
Similar presentations
Software development process improvement Ville Wettenhovi Master thesis presentation Supervisor:Professor Jukka Manner Instructor:M.Sc. Markus Aalto Date:23th.
Advertisements

DiscoverDefineDesignDevelopDeliver PROCESS TM. Intelligaia Technology confidential & proprietary Discover Overview: Gather information, brainstorm, competitive.
SCRUM © University of LiverpoolCOMP 319slide 1. SCRUM history In 1986, Hirotaka Takeuchi and Ikujiro Nonaka More an observation of good practise in manufacturing.
Concepts of Version Control A Technology-Independent View.
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.
Trusted IT Group. The challenge: 40 active, concurrent IT projects  Unsatisfactory Project Delivery.
CryptKeeper Project Plan 1 CryptKeeper Project Plan.
Whistle Stop Tour of The Module. Stop and think!
Resource Systems.  The need for agility  History of Product Development  Delivery of EPCOT  Future Challenges & Recommendations  Reflection  Questions?
1 - Agile in a nutshell. 2 - Basic principles ●Relies on an iterative, incremental development mechanism with continuous adaptation to customer requirements.
(Building the Presentation Layer - KISS). Figuring out what to do! Every was not learnt over night and certainly not without proper help and support.
Team Assignment 3 Team 4 – K15T2 Present. Introduce to project Goal of project Profitable for Honda Vietnam Company. Improved working process. Increases.
Case Study: Overcoming Challenges in Game Capstone Course IS4600 – Software Project Management Nelson Man.
Theories of Agile, Fails of Security Daniel Liber CyberArk.
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
Team Assignment 3 Team 4 – K15T2 Present. Introduce to project Goal of project Profitable for Honda Vietnam Company. Improved working process. Increases.
Version Control and SVN ECE 297. Why Do We Need Version Control?
Learning to Craft Code is Challenging Every skill we have acquired was trick at first We need to take baby steps We need proper support.
SCRUM © University of LiverpoolCOMP 319slide 1. SCRUM history In 1986, Hirotaka Takeuchi and Ikujiro Nonaka More an observation of good practise in manufacturing.
Created By:-
Copyright © 2009 Intel Corporation. All rights reserved. Intel, the Intel logo, Intel Education Initiative, and the Intel Teach Program are trademarks.
Software Design CSSE 374 Srum & Trello Intro Chandan R. Rupakheti & Steve Chenoweth Week 1, Day 4.
Utilize Agile Project Management for GIS Projects Jennifer Prather and Lana Tylka.
Embedded Systems Software Engineering
Software Development - Methodologies
Agile Methods SENG 301.
Software Development.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum.
Scrum and TargetProcess
Why Software Estimation is so Painful and How It Doesn’t Have To Be
Getting Started on The Project Bank in Visual Studio
Managing the Project Lifecycle
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Sample Wiki Comments?.
Distributed software development
Product Sprint Backlog Backlog Up to 1 Month The Scrum Framework
Not your average bacon and eggs
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
School of Arts, Languages and Cultures
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Branching Strategy.
T Project Review Group: pdm I2 Iteration
Agile Software Development Brian Moseley.
Maintaining software solutions
Chapter 3: The Project Management Process Groups: A Case Study
CSCE 741 Software Process Lecture 04 Availability
School of EE and Computer Science
Smoke and Mirrors Prototype
Object Oriented Analysis and Design
Teaching slides Chapter 1.
Summarizing Our Models to Date
Johanna Rothman Know What “Done” Means Chapter 11
IMAT2204 Project Management and Development
IMAT2204 Project Management and Development
© University of Liverpool
Tools and Techniques for Agile Project Management
CSCE 741 Software Process Lecture 04 Availability
Agile practices for documentation teams
Quality Assurance in an Agile Development Team Michelle Wu 2018 PNSQC
Part 2 of the Module.
IMAT2204 Project Management and Development
Smoke and Mirrors Prototype
Real World Scrum with TFS & VSTS / Azure DevOps
Part 2 of the Module.
IMAT2204 Project Management and Development
Hadleigh Castle Project
Scrum in Action.
Scrum: Daily Stand Up Meeting
Executive Project Kickoff
Presentation transcript:

Part 2 of the Module

Learning to Craft Code is Challenging Every skill we have acquired was trick at first We need to take baby steps We need proper support

Scrum Development Scrum Master Sprint Pair Programming Product Backlog SPRINT Backlog

Next Year May of you will take on a systems development project Team development Individual development (Or you will decide never to write code ever again!) The second half of this module is your play pen

Baby Steps Test Driven Development (Programming Pathways) Pair programming SCRUM Master SCRUM Teams 14 day SPRINT – 3 x SPRINT Logs (assessed) Product backlog SPRINT backlog These are the tools that will help you build skill and confidence

The system design Class diagram describes your code

Test Driven Development Provides the scaffolding that supports the structure

Interface Design Describes what the interface will do

Version Control

Avoiding Loss of Work Jane opens clsDataConnection in Visual Studio Bob adds a new method to clsDataConnection Bob saves his work on the class Jane completes her work modifying the code for clsAddressBook In the process Jane also saves clsDataConnection This reverts clsDataConnection back to its original version overwriting the new code created by Bob

Wider Implications for Customers Bob and Jane work on the system to produce version 1.0 of the product Version 1 is released to customers More work is carried out and version 1.1 is released which is chargeable Some customers report that with version 1.0 there is a bug Customers refuse to upgrade to version 1.1 due to the cost and want a fix for version 1.0 (This will create version 1.01) The question then arises how to manage the code not just to handle multiple versions of the code in use by developers but also multiple versions of the code over the history of the system. These problems are not trivial!

Communication and Organisation SCRUM Master co-ordinates procedures Team members must talk to each other Clear idea of who is doing what

This Week and Next Finish off claims for the first deliverable You may not make changes on that work 10 min per person Schedule A teams wk 16 Schedule B teams wk 17 Clear the deck so that we may focus on the development of the system