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.

Slides:



Advertisements
Similar presentations
Renato Pinto López TUM18 - UPM. Sprint Planning Meeting ATTENDED BY PRODUCT OWNER (PO), SCRUM MASTER AND SCRUM TEAM PO DESCRIBES THE HIGHEST PRIORITY.
Advertisements

Software development process improvement Ville Wettenhovi Master thesis presentation Supervisor:Professor Jukka Manner Instructor:M.Sc. Markus Aalto Date:23th.
Ni.com Introduction to Agile and Scrum Speaker/Author: Paul Packebush Section Manager, Corporate Metrology Author:Logan Kunitz Staff Calibration Engineer.
C O N F I D E N T I A L 4-May-15 1 Attendee Management - Being Agile Attendee Management.
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.
NAUG NAUG Knowledge Evening – th February 2007.
Concepts of Version Control A Technology-Independent View.
Software Development Methods And Some Other Stuff.
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.
AgileCamp Presents: Agile Software Development. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons.
CryptKeeper Project Plan 1 CryptKeeper Project Plan.
Whistle Stop Tour of The Module. Stop and think!
Dr. Tom WayCSC Software Processes CSC 4700 Software Engineering.
CSE G674/2009 Project Project Management Section Presented by: Amir Aref Adib.
Resource Systems.  The need for agility  History of Product Development  Delivery of EPCOT  Future Challenges & Recommendations  Reflection  Questions?
Hurdles The sprint with impediments on the way to automation Agile India 2014 報告者:李佩臻.
SCRUM Not your average bacon and eggs. The Basics Product Backlog Sprint Backlogs Sprints – The Daily Scrum – Burn-down chart Sprint Retrospective.
When is Agile the Best Project Management Method? Lana Tylka.
SCRUM for Startups Innosquared – Providing expertise on demand.
Scrum Practices Sprint-2. Agenda Scrum Master Product Backlog Scrum Teams Daily Scrum Meeting Sprint Planning Meeting Sprint Sprint Review.
COMP 208/214/215/216 Lecture 3 Planning. Planning is the key to a successful project It is doubly important when multiple people are involved Plans are.
Dr. Jana Jagodick Polytechnic of Namibia, 2012 Project Management Chapter 7 Some Factors to Think About in Time Management.
TEACHER FEEDBACK WEBSITE HTVN TEAM. AGENDA 1.TEAM INTRDUCTION 2.PROJECT OVERVIEW 3.PLAN 4.PRODUCT ARCHITECTURE 5.DATABASE DESIGN 6.TEST PLAN & TEST REPORT.
Webster Visualize Webster Financial Team Visual Scrumware Joe Andrusyszyn Mark Bryant Brian Hannan Robert Songer.
1 - Agile in a nutshell. 2 - Basic principles ●Relies on an iterative, incremental development mechanism with continuous adaptation to customer requirements.
Computer Science and Engineering The Ohio State University  Widely used, especially in the opensource community, to track all changes to a project and.
(Building the Presentation Layer - KISS). Figuring out what to do! Every was not learnt over night and certainly not without proper help and support.
Computer Science and Software Engineering© 2014 Project Lead The Way, Inc. Software Design Process.
Whistle Stop Tour of The Module. This is a new module!
University of Southern California Center for Systems and Software Engineering Agile Project Management Tools Supannika Koolmanojwong CSCI 577a.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
Time to Support PGES. Think and Share Let’s say a new teacher’s management skills result in a loss of instructional time. To solve the problem you ask.
With a hint of HP Quality Center Agile development and functional testing: friend or foe? Tom Vercauteren, June 26th, 2009.
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.
T Sprint Demo Team Tarantino Iteration 1 / Sprint
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.
Communication: what, when and why? Isabel Costello, Student Voice Coordinator (Course Reps & Quality)
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?
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
T Iteration Demo Tikkaajat [PP] Iteration
SCRUM © University of LiverpoolCOMP 319slide 1. SCRUM history In 1986, Hirotaka Takeuchi and Ikujiro Nonaka More an observation of good practise in manufacturing.
Whistle Stop Tour of The Module. Stop and think!
Strategy Mapping Clear path to a successful Agile strategy Dave Neuman Sep 24, 2015 LinkedIn:
Created By:-
#msdevcon Community Track IMPLEMENTATION OF SCRUM Bernardin Katić Insa Investment Software AG.
Scrum.
Why Software Estimation is so Painful and How It Doesn’t Have To Be
Agile Software Development II
Getting Started on The Project Bank in Visual Studio
Not your average bacon and eggs
Agile Software Development Brian Moseley.
CSCE 741 Software Process Lecture 04 Availability
School of EE and Computer Science
Smoke and Mirrors Prototype
Scrum MODULE 3 – Part 3.
Teaching slides Chapter 1.
Summarizing Our Models to Date
Tools and Techniques for Agile Project Management
Part 2 of the Module.
CSCE 741 Software Process Lecture 04 Availability
Part 2 of the Module.
Smoke and Mirrors Prototype
Part 2 of the Module.
Scrum in Action.
Scrum: Daily Stand Up Meeting
Presentation transcript:

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 – 4 x SPRINT Logs 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!

The Desire Path

Communication and Organisation SCRUM Master co-ordinates procedures Team members must talk to each other Clear idea of who is doing what At all times the customer is always right

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