CSCE 741 Software Process Lecture 04 Availability

Slides:



Advertisements
Similar presentations
A little Software Engineering: Agile Software Development C Sc 335 Rick Mercer.
Advertisements

What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
ECE44x SCRUM Overview slides adapted from Marty Stepp
SCRUM John Drew. SCRUM - overview Scrum is a project management discipline that has evolved since the early 1990s to deliver software that meets business.
NAUG NAUG Knowledge Evening – th February 2007.
Introduction to Agile.
Agile Methodologies for Project Management By – Komal Mehta.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
Trusted IT Group. The challenge: 40 active, concurrent IT projects  Unsatisfactory Project Delivery.
CSE G674/2009 Project Project Management Section Presented by: Amir Aref Adib.
Current Trends in Systems Develpment
Alcatel-Lucent CDC Workshop, Coaching & Knowledge Transfer Project Management.
Dr. Rob Hasker copyright by Mark J. Sebern, Robert W. Hasker.
SCRUM introduction 6 April Scrum Team are known as pigs because they’re committed to delivering Sprint Goal People who are involved but not dedicated.
1 - Agile in a nutshell. 2 - Basic principles ●Relies on an iterative, incremental development mechanism with continuous adaptation to customer requirements.
Copyright © 2015 Curt Hill Software Development Paradigms What do you need to know?
Copyright © by Mark J. Sebern Software Engineering Process I The case for agile processes.
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
Agile Development Chapter 10 - part 2. Agile Philosophy  A guiding philosophy and set of guidelines for : developing information systems in an unknown,
Introduction to Agile. Introduction Who is this guy?
Industrial Software Development Process Bashar Ahmad RISC Software GmbH.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
CMPS 116 Software Design Project. Introduction Instructor: Dr. Huahai Yang IBM Research – Almaden Former SUNY Albany Programming.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
Embedded Systems Software Engineering
Approaches to Systems Development
Agile Project Management
Change your look and feel to how you work! Let’s SCRUM Change your look and feel to how you work!
Scrum.
Agile Training Day 2 November 17, 2015.
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
SCRUM.
Agile Training – Agile Overview
Agile Scrum Management
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Introduction to Eclipse Process Framework: EPF Composer and OpenUP
Information Technology Project Management – Fifth Edition
By: By: Agile Scrum Master Online Training.
Navigating an Agile Transformation
Lecture Software Process Definition and Management Chapter 2: Prescriptive Process Models Dr. Jürgen Münch Fall
Chapter 3: The Project Management Process Groups: A Case Study
CSCE 741 Software Process Lecture 04 Availability
Approaches to Systems Development
Rapid software development
CEN 4010 Intro to Software Engineering Professor Alex Roque
Project Management and the Agile Manifesto
CSCE 741 Software Process Lecture 04 Availability
Scrum MODULE 3 – Part 3.
How to Successfully Implement an Agile Project
Summarizing Our Models to Date
Scrum Overview.
© University of Liverpool
CSCE 741 Software Process Lecture 04 Availability
Agile Process: Overview
CSCE 741 Software Process Lecture 04 Availability
CSCE 741 Software Process Lecture 04 Availability
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
CSCE 741 Software Process Lecture 04 Availability
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
Introduction to Agile Blue Ocean Workshops.
Scrum Science NGSS: Engineering, Technology, Applications of Science
Scrum Science NGSS: Engineering, Technology, Applications of Science
Topic 1: Introduction to the Module and an Overview of Agile
Scrum in Action.
Agile, Scrum and CMMI Methodologies
Presentation transcript:

CSCE 741 Software Process Lecture 04 Availability Topics Chapter 5 – Availability Lecture 2 -- Overview Scrum Agile principles of scrum Readings:ES Ch 2-3 August 30, 2017

Last Time New Overview: Agile Spring Framework Spring Boot – Convention over configuration Configuration increases modifiability Virtual Machines New Syllabus and other course pragmatics -- Website (not shown) Core Agile/Scrum Concepts

Spiral model revisited (B. Boehm) Boehm’s Original Diagram What was in Sommerville

Spring Project Structure

Fall CSCE schedule -- csv file Schedule -- Tab separated values (Comma separated values, csv files) SR 18629 CSCE 740 001 COL 3.000 30 - Columbia Full Term Software Engineering TR 08:30 am-09:45 am 28 18 10 Gregory James Gay (P) 08/24-12/08 SWGN 2A05 SR 25398 CSCE 741 001 COL 3.000 30 - Columbia Full Term Software Process MW 02:20 pm-03:35 pm 40 10 30 Manton M. Matthews (P) 08/24-12/08 WMBB 409 SR 25399 CSCE 741 006 COL 3.000 30 - Columbia Full Term Software Process MW 02:20 pm-03:35 pm 50 1 49 Manton M. Matthews (P) 08/24-12/08 WEB COLUMBIA SR 12841 CSCE 750 001 COL 3.000 30 - Columbia Full Term Analysis of Algorithms TR 11:40 am-12:55 pm 50 46 4 Jason Matthew Okane (P) 08/24-12/08 WMBB 409 …

Spring Tool Suite (STS) Eclipse extension? Variation? Eclipse based development environment

Spring Starter project Google(SpringBoot Javabrain)

Spring Example = Spring Boot Journal Chapter 2 --

Experience Why are you taking this course? Software Engineering courses? Favorite language? Programs in Java (if none C++ or C#) Estimate lines of Code

Java World Java (the language) JVM (java virtual machine) javac java Write once, run anywhere – Wikipedia a slogan created by Sun Microsystems to illustrate the cross-platform benefits of the Java language. javac java IDEs(Integrated Development environments) Eclipse IntelliJ (IDEA) Netbeans What’s a bean? What’s a POJO?

Essential Scrum by Rubin

Virtual Box Virtual machine

VirtualBox

VDI Dynamically allocated

What’s left? Install Ubuntu Create Share

1) Download: VirtualBox and VirtualBox Extensions 2) run installer 3) New a) Choose Linux b) Memory 4G=4096MB c) Create virtual Hard disk now d) VDI e) Dynamically allocated f) 30 GB 4) Extensions a) File ==> Preferences ==> extensions b) select virtualBox Extensions file downloaded earlier

5) Operating System a) Storage b) Controller c) add optical disk d) select Ubuntu (or other OS) from download folder or ... e) click on disk and select Live CD/DVD f) Start 6) Linux install 7) Storage ==> IDSE Controller: remove linux_iso 8) Shared folder: Storage ==> Shared folders ==> "+" (add shared folder) path on host name on VM

Setup base system like you like; then snapshot Linux Base system java spring STS

Required Tools Java 8 or later Eclipse = STS Maven Spring library Spring Boot conventions

Relationship between Scrum and Agile Scrum is a pre-defined development lifecycle based on agile principles. Agile methodologies promote a project-management process that encourages frequent inspection and adaptation, and a leadership philosophy using teamwork, self-organization and accountability. Agile is a general philosophy regarding software production, Scrum is an implementation of that philosophy pertaining specifically to project management. http://www.360logica.com/blog/what-is-the-relationship-between-scrum-and-agile/

Scrum distinguished from Agile (continued) Agile and scrum are related but distinct. Agile describes a set of guiding principles for building software through iterative development. Agile principles are best described in the Agile Manifesto. Scrum is a specific set of rules to follow when practicing agile software development.  Scrum is an iterative and incremental agile development methodology. Scrum may be viewed as an agile framework for developing software. http://www.360logica.com/blog/what-is-the-relationship-between-scrum-and-agile/

Scrum distinguished from Agile (continued) Unlike many other software development methodologies, scrum does not provide a complete template or detailed description of what to do during software development. Scrum prescribes desired outcomes and leaves it to the agile scrum team to best determine how to solve the problems they encounter. Scrum may be used for both software development and software maintenance projects.  http://www.360logica.com/blog/what-is-the-relationship-between-scrum-and-agile/

Scrum is a framework for organizing and managing work. Not a standardized process Based on a set of values, principles and practices “Scrum is a refreshingly simple, people-centric framework based on the values of honesty, openness, courage, respect, focus, trust, empowerment, and collaboration.” Rubin, Kenneth S.. Essential Scrum: A Practical Guide to the Most Popular Agile Process (Addison-Wesley Signature Series (Cohn)) (p. 13). Pearson Education. Kindle Edition. Essential Scrum by Rubin

Scrum Practices Roles Activities Artifacts Rules Product owner Scrum Master Development team Activities Sprint: planning, execution, review Daily scrum Product backlog grooming Artifacts Backlog: product, sprint Rules Essential Scrum by Rubin

Scrum Roles Essential Scrum by Rubin

Product Owner The product owner is the empowered central point of product leadership. They are the single authority responsible for deciding which features and functionality to build and the order in which to build them. The product owner maintains and communicates to all other participants a clear vision of what the Scrum team is trying to achieve. As such, the product owner is responsible for the overall success of the solution being developed or maintained. Essential Scrum by Rubin

Scrum Master The ScrumMaster helps everyone involved understand and embrace the Scrum values, principles, and practices. She acts as a coach, providing process leadership and helping the Scrum team and the rest of the organization develop their own high-performance, organization-specific Scrum approach. At the same time, the ScrumMaster helps the organization through the challenging change management process that can occur during a Scrum adoption. As a facilitator, the ScrumMaster helps the team resolve issues and make improvements to its use of Scrum. She is also responsible for protecting the team from outside interference Essential Scrum by Rubin

Development Team Traditional Software development roles Architect Programmer Tester DB administrator UI designer Scrum development team – a diverse, cross-functional collection of these tyes who are responsible for … Essential Scrum by Rubin

Scrum Artifacts . Essential Scrum by Rubin

Product Backlog Product Backlog (text) -- (user stories) (use cases) Product Owner prioritizes the user-stories Team Identifies amount of work for each user-story Forecast or commitment – the user stories selected for this sprint Essential Scrum by Rubin

Product Backlog manipulations Essential Scrum by Rubin

Essential Scrum by Rubin

Sprint Backlog -- tasks Tasks to break down entries in product backlog Sprint backlog of tasks Just in time planning Sprint planning 4 to 8 hours Essential Scrum by Rubin

Essential Scrum by Rubin

Daily Scrum Essential Scrum by Rubin

Daily Stand-Up What did I accomplish since the last daily scrum? What do I plan to work on by the next daily scrum? What are the obstacles or impediments that are preventing me from making progress? Rubin, Kenneth S.. Essential Scrum: A Practical Guide to the Most Popular Agile Process (Addison-Wesley Signature Series (Cohn)) (p. 24). Pearson Education. Kindle Edition. Essential Scrum by Rubin

The chickens and the pigs Essential Scrum by Rubin

Essential Scrum by Rubin

Agile Principles (Chapter 3) Before we delve deeper into the mechanics of Scrum, it will be helpful to understand the underlying principles that drive and inform those mechanics. This chapter describes the agile principles that underlie Scrum and compares them with those of traditional, plan-driven, sequential product development. Essential Scrum by Rubin

Categorization of Principles Essential Scrum by Rubin

Variability and Uncertainty Scrum leverages the variability and uncertainty in product development to create innovative solutions. Embrace helpful variability. Employ iterative and incremental development. Leverage variability through inspection, adaptation, and transparency. Reduce all forms of uncertainty simultaneously. Essential Scrum by Rubin

Waterscrum or Scrummerfall Essential Scrum by Rubin

. Essential Scrum by Rubin

Scrum Process Model Essential Scrum by Rubin

Accept that there will be changes in Requirements Essential Scrum by Rubin

Cost of changes to Requirements Essential Scrum by Rubin

Essential Scrum by Rubin

Essential Scrum by Rubin

Validated learning Validate important assumptions fast. Leverage multiple concurrent learning loops. Organize workflow for fast feedback. Rubin, Kenneth S.. Essential Scrum: A Practical Guide to the Most Popular Agile Process (Addison-Wesley Signature Series (Cohn)) (p. 45). Pearson Education. Kindle Edition. Essential Scrum by Rubin

Adapt to real-time information and replan. Measure progress by validating working assets. Focus on value-centric delivery. Rubin, Kenneth S.. Essential Scrum: A Practical Guide to the Most Popular Agile Process (Addison-Wesley Signature Series (Cohn)) (p. 54). Pearson Education. Kindle Edition. Essential Scrum by Rubin

Essential Scrum by Rubin

Performance Go fast but never hurry. Build in quality. Employ minimally sufficient ceremony. “process for the sake of process” Essential Scrum by Rubin

Essential Scrum by Rubin

Essential Scrum by Rubin

continued Essential Scrum by Rubin

Essential Scrum by Rubin