School of Business Administration harrisburg psu edu Penn
School of Business Administration harrisburg. psu. edu Penn State Project Management Conference
School of Business Administration harrisburg. psu. edu Agile in the Classroom A First Sprint IST 361 Jesse Middaugh, PMP Instructor of IST Penn State Harrisburg President of PMI Keystone Chapter
Agenda • • Brief Introduction Change in Methodology / Pedagogy Initial Results Wrap-Up
Information about Me 4
Information about the Class • Application Design Studio Class – Focus on independent Design – Problem-based / project-oriented – Peer and Instructor design critiques – Complete deliverables in various project stages • Not actually a Project Management Class
Agile Vs. Traditional • Traditional Requirements – Written Sentences & Paragraphs – Diagrams and Figures • User Stories – Limited Descriptions – User Stories (Focus on Customer Perspective) • Easier to remember that written Requirement
What is Agile? Traditional Design Code Test Analysis Agile Analysis Design Code • Breaking projects down into little bits of user functionality • Prioritizing them • Continuously delivering them in short cycles Test http: //www. agilenutshell. com/ Continuous Activities 7
Project Grading Scale Last Year’s (Traditional) Topic Initiation (Proposals & Scope) Planning Project Plan Requirement Document Design Document Execution % 10% 35% Testing Walk-Thru Design Journal Close 10% Quizzes & Postings 10 % Professional / Social Responsibility 5% Current Years (Agile) Topic % Process - (SDLC Project Methodology) Product - (Design Project) 15% Presentations & Participation 15% Quizzes, Design Questions & Postings Peer & Design Review Testing 15% 40% 15 %
Traditional Project (SDLC) Initiating Project Idea Project Charter Team Charter Proposal Planning Project Plan Gathering Requirement Developing Design Closing Report Prototype Walk-through Final Product Test Plan Test Results
Agile Project (SDLC) User Stories Project Idea Project Charter Team Charter Proposal User Stories Release Planning Product Backlog Sprint Planning Sprint Backlog Sprint Prototype Walk-through Sprint Review Releasable. Product Test Results
Agile Approach Planning Review Sprint #1 Product Planning Backlog Review Sprint #2 Planning Backlog Review Product Sprint #3 Product Today Backlog
User Story Writing The 3 -C’s 1. Cards 1. User Stories 2. Can help smaller sub-stories 2. Conversation 1. Details about the stories (requirements) come out with conversation with the product owners 3. Confirmation 1. Acceptance tests confirm the user story was correctly code 12
User Story 1 - High 2 – Med 3 - Low How Long? 13
User Story – Acceptance Criteria 14
User Story Review • When user clicks on Button, upper right, it goes to the cart • This screen displays items selected
Student Comments PROJECT ORGANIZATION “With the limited experience, I have with the agile development approach, I believe that it has kept the actual development for my team and I much more organized. Especially with some projects, we tend to get lost on what to develop first after designing the interface and try to develop the entire project together. Using sprints, has helped my team and I narrow down on what we need to accomplish first before other less important parts of the program. ” Sean Goshens TESTING “Also, testing after each sprint gives us some initial feedback on our current iteration of the system that we can improve upon. This is in contrast towards finishing either some storyboards or the entire program and having the feedback towards the end of development. ” Sean Goshens
Student Comments ESTABLISHING PRIORITIES “Splitting the whole project into these sprints and phases has definitely played a crucial role in narrowing down the tasks needed to be accomplished, thus helping us prioritize it accordingly. This way, the most crucial tasks and aspects of the projects will be completed early enough to allow time for changes to be made based on the feedback received. ” Alina D. Silva
Questions
Lessons Learned • What’s on the next Sprint – Better defined process • • Some more time with the agile concepts Release Planning Sprint Review Sprint Retrospective
- Slides: 19