So#ware Development Methodologies Project Management Phases Agile Methodology Agile Manifesto Roles. Team Roles and Responsibili?

Size: px

Start display at page:

Download "So#ware Development Methodologies Project Management Phases Agile Methodology Agile Manifesto Roles. Team Roles and Responsibili?"

Cleopatra Deborah Black
8 years ago
Views:

1 Module Summary So#ware Development Methodologies Project Management Phases Agile Methodology Agile Manifesto Roles Team Roles and Responsibili?es Goal for First Client Mee?ng Expecta?ons Client Student Team

2 Agile So1ware Development in Today s Industry CompSci Fall 2014 Professors: Robert Duvall, Ajay Patel, Salman Azhar (rcd@cs, ajay.patel, azhar@cs)

3 Overview Introduc?on So#ware Development Methodologies Agile Methodology Project Management Phases

4 Introduc>on My background Course to simulate a so#ware consul?ng firm What you, the student, can expect from this course

5 So1ware Development Methodologies Waterfall Itera?ve Waterfall Agile - Scrum

6 Waterfall Methodology

7 Itera>ve Waterfall Methodology

8 Agile Methodology

10 Agile Approach Agile so#ware development is a group of so#ware development methods based on iterakve and incremental development where requirements and solu?ons evolve through collabora?on

11 Agile Methods Scrum (SCRUM) Extreme Programming Ra?onal Unified Process Crystal Clear Adap?ve So#ware Development Feature Driven Development Dynamic Systems Development Method (DSDM)

12 Agile Manifesto Individuals and interac?ons over processes and tools Working so#ware over comprehensive documenta?on Customer collabora?on over contract nego?a?on Responding to change over following a plan hpp://agilemanifesto.org

13 Scrum iterakve and incremental framework for managing so#ware projects focused on delivering features small, tested, independent, valuable diversifies risk if one feature does not go as planned, should not impact another feature hpp:// scrum

14 Roles Product Owner a stakeholder represen?ng the customer Development Team responsible for delivery Scrum Master accountable for removing impediments so the team delivers the sprint goal/deliverables Test and Evalua?on Team responsible for finding, documen?ng, and repor?ng all bugs or defects to the rest of the team

15 Sprint A sprint is the basic unit of development in Scrum Incremental feature development Specific dura?on normally one week to one month Each sprint is preceded by a planning mee?ng Iden?fy tasks and es?mate commitment for the goal Review progress and learn lessons from sprint

16 Sprint Process During each sprint the team creates finished por?ons of a product the feature set that goes into a sprint come from the product backlog which is an ordered list of requirements The backlog items for a sprint s goals are determined during the sprint planning mee?ng The Product Owner choses the highest priority items and gets agreement from the team

18 RECAP So#ware Development Methodologies Agile Methodology Project Management Phases

19 Ques?ons?

20 Team Roles and Client Mee>ng Prepara>on CompSci Fall 2014 Professors: Robert Duvall, Ajay Patel, Salman Azhar (rcd@cs, ajay.patel, azhar@cs)

21 Overview My background Team Roles and Responsibili?es Goal for First Client Mee?ng

22 Team Roles & Responsibili>es Project Manager & Team Lead Business Analyst Technical Lead Quality Assurance (Test) Lead

23 Role: Project Manager & Team Lead Maintains project milestones &?meline Manage JIRA (Tasks, Agile Board & Sprints) Primary contact for team Insures team has necessary resources (tools/access/info) Communicate project deliverables (to instructors)

24 Role: Business Analyst Primary client contact Coordinates client mee?ngs Manages requirements Represents/understands client needs Manages Confluence (organize, publish client info, document mee?ng minutes)

25 Role: Technical Lead Provides technical direc?on in terms of: solu?on pla^orm (ios, Android, Web) database, languages, etc. toolkits design paperns

26 Roles: Quality Assurance (Test) Lead Plans and implements tes?ng to insure adequate quality

27 RECAP: Team Roles & Responsibili>es Project Manager & Team Lead Maintains project milestones &?melines Manage JIRA (Tasks, Agile Board & Sprints) Primary contact for team Insures team has necessary resources (tools/access/info). Communicate project deliverables (to instructors) Business Analyst Primary client contact, coordinates client mee?ngs Manages requirements, represents/understands client needs Manages Confluence (organize, publish client info, document mee?ng minutes) Technical Lead Provides technical direc?on in terms of solu?on pla^orm (ios, Android, Web), database, languages, toolkits, design paperns Quality Assurance (Test) Lead Plans and implements tes?ng to insure adequate quality

28 Goal for First Client Mee>ng (Project Ini>a>on/Planning) Establish project team Client stakeholders Student Team: BA, PM, QA, TL ( instructors by Sep 5 8am) Establish communica?on Primary client contact & student contact (BA) Tools for Collabora?on (Confluence) Understand project purpose & scope Schedule next mee?ng Document mee?ng minutes date/?me, apendees, discussion topics, issues, ac?on items

29 RECAP Team Roles & Responsibili?es Goal for First Client Mee?ng

30 Ques?ons?

31 Expecta>ons CompSci Fall 2014 Professors: Robert Duvall, Ajay Patel, Salman Azhar (rcd@cs, ajay.patel, azhar@cs)

32 OVERVIEW: Expecta>ons Student Team Expecta?ons Client Expecta?ons

33 Your Expecta>ons of the Client The client is your customer You are providing a service to them The client decides the features, func?onally and behavior of the so#ware

34 Student Team Expecta>ons of Yourself Sa?sfy the client They are your customer Schedule mee?ngs with client with sufficient no?ce Be accommoda?ng At least 2 team members apend every client mee?ng Use Confluence (Wiki) to collaborate with client Document requirements, project?meline with milestones, mee?ng minutes, user documenta?on, training material Manage client expecta?ons of project deliverables Be organized and prepared for mee?ng the client The beper organized you are and your ability to convey project ambiguity the more produc?ve you will be Hold the client accountable for their deliverables in the most business professional (polite) way

35 Project Communica>on compsci408s- Project issues Guidance Deliverables

36 Clients Expecta>ons Introduc?on What to expect Prototype versus so#ware ready for users

37 Expected of Client Meet with student team weekly if possible some can be remote Two in- class mee?ngs for Alpha and Beta releases Consistent representa?on: Have at least one person (same person) who understands the requirements & apends every mee?ng with the student team Students have about 8-10 weeks of coding?me so define the project scope accordingly and know what you want. You provide content (e.g. graphics, text). Be organized & prepared for mee?ngs with the student team Minimize requirement changes (short fixed?me frame) Hold the student team accountable for their deliverables You will need about 10 users for user tes?ng Prepare your IT group to maintain and host the solu?on

38 RECAP Student Team Expecta?ons Client Expecta?ons

39 Ques?ons?

CompSci 408 - Fall 2014 Professors: Robert Duvall, Ajay Patel, Salman Azhar (rcd@cs, ajay.patel, azhar@cs)

Agile Software Development in Today s Industry CompSci 408 - Fall 2014 Professors: Robert Duvall, Ajay Patel, Salman Azhar (rcd@cs, ajay.patel, azhar@cs) Overview Introduction Software Development Methodologies