KANBAN and TEAMWORK. Natural User Interface Technology to Business Erasmus Intensive Programme LAHTI

Transcription

1 KANBAN and TEAMWORK Natural User Interface Technology to Business Erasmus Intensive Programme LAHTI HEIKKI PAANANEN - Lecturer, MSc (Econ) Lahti University of Applied Sciences heikki.paananen@lamk.fi

2 THEMES IN THIS LESSON Flexibility through Agile project methods Todo Ongoing Done Illustrating team s work with Kanban

3 Lesson outline WHAT IS AGILE? Scrum in nutshell Kanban to bring visibility

4 What is Agile? Not trying to accomplish everything at once, but instead, slicing the big goal into little iteration Easier to control the process of work Easier for customer to see actual outcome Illustrating figure outlines Adding background Adding snowflakes Snow man s hat adding colors and details Monday PROJECT START! Tuesday Wednesday Thursday Friday PROJECT READY!

5 MANIFESTO Agile rules & Manifesto Agile methods drives for reasonable ratio between documentation, design and implementation The main focus is on customer satisfaction and system that works Individuals and interactions over processes and tools Working software Customer collaboration Responding to change over comprehensive documentation over contract negotiation over following a plan

6 Good to understand what is needed in a software development project! Waterfall / Traditional Model Waterfall model Developed in 1970s Based on physical process models Software development process is seen as process flow that is hard or even unnecessary to halt & go backwards Pre study Analysis Design Implementation Testing Deployment Maintenance

7 Traditional Waterfall development As a generalization, waterfall contains 4 stages: Requirement (R) Design (D) Coding (C) Testing (T) = R D C T first time customer can see the working system R D C T Feature 1 All features under test simultaneously at the end of the project Feature 2 Feature 3 Feature 4 PROJECT DEADLINE Project Outcome 100% ready

8 Efforts WATERFALL TIMELINE Start Development efforts Project Timeline Backlog Of unresolved defects Testing efforts End Development: Strong emphasis on the 1st half of the project Test: Strong emphasis on the 2nd half of the project Backlog of unresolved defects Significant, asymmetric peak towards end of the project Does not sound good to have increasing number of defects so late in project? Chart by: Stober & Hansmann, Agile Software Development, 2010

9 Evaluation of traditional Waterfall approach POSITIVE Clear and ideallic model - giving information what tasks are needed in a IT project Good for relatively small projects NEGATIVE Customers cannot see working solution before second half of the project Changes in requirements are difficult Does not give must flexibility at the end of the project

10 Agile methods going beyond waterfall Agile methods aims to: Verify customer wishes really early on the project Value & high quality by giving possibility to customer to alter the solution during the development Instead of making all at once, everything is done ready piece by piece Offering possibilities to customer to evaluate each improvement puzzle piece Put focus on delivering fully working features Keeping current version as ready as possible 1st iteration R D C T 2nd iteration R D C T 3rd iteration R D C T 4th iteration R D C T Final Product

11 Agile development approach first time customer can see the working system R D C T + R D C T Iteration outcomes are always integrated into main solution (shippable solution) Features built one by one 100% ready (working solutions) + R D C T + R D C T PROJECT DEADLINE

12 Efforts MATURE AGILE TIMELINE Development efforts Backlog of unresolved defects Development: Continous development Test: Continous testing Backlog of unresolved defects Curve is quite flat throughout the project Start Testing efforts Project Timeline End Agile drives for continous development and tackling of defects in really early Chart by: Stober & Hansmann, Agile Software Development, 2010

13 Playlist Slicing down Agile project [EXAMPLE] Search functionality Browsing collection UI graphics Project: Creating music player software for a customer Breaking system into smaller functionality pieces which are developed and created one by one Play functions

14 Further from design to implementation Agile gives possibilities to slice down the big system into smaller parts through defining system with user stories, a full definition of particular use of the system. Customer can see in iterations (R D C T ) a fully functional small part of the system in hand User story 1: browsing collection User story 2:..searching function User story 3: playing songs User story 4:..player functions User story 5:..adding to playlist User story 6: playlist functions User story 7:.. additional graphics R D C T R D C T R D C T PROJECT DEADLINE

15 Lesson outline What is agile? SCRUM IN NUTSHELL Kanban to bring visibility

16 Scrum in nutshell - Functionalities of the solution - Technical work, - Knowledge acquisition Priorized list! Daily Standup 15min meeting. Every team member will speak: - What did I do yesterday? - What will I do today? - Are there any obstacles? Daily Standup MEETING 24h Shippable software product Sprint Backlog 1-4 weeks SPRINT Sprint outcome Increment Product Backlog (maintained by customer) Tasks decided in Sprint Planning Increments are integrated to earlier sprints outcomes

17 Scrum Master: - Keeps the Process moving - Helps solve bloking points - Responsible for team health Scrum Agile methods in practice 2 Business Owner: - Supplies resources to the scrum team - Helps resolve blocking points Product owner: - Represents the Business owner and SMEs in team - Responsible for features, release date and content - Understands profitability of the product (ROI) - Prioritizes What a Scrum team does Business owner Implementation and Developer testing Scrum master Product owner SME Design & Analysis R D C T Quality Assurance and Acceptance testing Deployment SCRUM TEAM Detailed requirements Evaluation / prioritization SME = Subject Matter Expert Subject Matter Expert (SME): - People who should be on the team but they are not - Have skills that the team needs SME Development team: - Cross-functional (<7 members) - Determines & agrees team s work - self-organizing

18 Items in the backlog Items in the backlog are called User Stories Requests for valuable items User story template according to Agile Consortium: As a <User Role> I want <Something> so that <Some value or benefit> For Developers, the I want clause is what counts Functionalities For Product Owner, the so that clause is what counts Value

19 Values and estimates are done by team User Stories [Sample] Purchase Train ticket Size: Large Value: 40 Analyze shopping cart Size: Timeboxed 2 days As a <ticket buyer> I want <to purchase a train ticket to destination city> so that <I have some way of paying for it that works> Agreement: This story is done when: - A user can purchase a already-found route ticket through the web interface - The code has been peer reviewed - The code is protected by unit tests, and all passed in the integrated environment - Purchasing done after the route is searched and returned Agreement: John Doe the analyst will be the Storyboss: - Identify SMEs (Subject Matter Experts) and include them in the contacts list - Meet SMEs, discuss and document issues in wiki -Generate First protype

20 Creating estimates with Planning poker Because Team decided that estimation is How long this story will take? (in man-days) Scrum master 1 =4 5 3 Product owner Every team member thinks of the man-days required for the story, and then cards are put to table simultaneously Because After showing the cards, team members showing biggest difference in estimation give their arguements.

21 Lesson outline What is agile? Scrum in nutshell KANBAN TO BRING VISIBILITY

22 TODO ONGOING DONE Kanban to bring visibility Literally meaning "signboard" or Visual Card Agile / ultra light method to improve project work visibility Pull-system: new work is taken under work when there exists capabilities to handle it Kanban can be used to enhance any software development process including Scrum, XP, Waterfall, and other methods

23 TODO ONGOING DONE Visualize your work with Kanban GOAL is to illustrate Delivery of value WHERE WE ARE at the moment with the project work WHAT WE SHOULD DO NEXT CORE PRINCIPLES 1. Bring visibility to FLOW OF WORK Visual model of your work and workflow Delivering tasks that create value 2. Limit unfinished tasks Minimizing WIP (Work In Progress), promoting quality, focus and finishing tasks. E.g. WIP = 2, means that person is allowed to take work only worth 2 units 3. Focus on Flow Priorize tasks, executing most urgent work 4. Continuous Improvement Teams measure their effectiveness by tracking flow, quality, throughput, lead times

24 Storyboard during sprint Backlog items in user story form: as a sales clerk I want to list customer Tasks are small action items that are needed to create functionalities for user story Swimlanes to indicate work process needed. WIP restricts amount of work - indicates how many items can be under work Indicators to show who is doing what and if there exists problems Backlog To Do WIP: 2 Ongoing Done USER STORY#1 As a developer I want to connect Kinect into a computer and launch the program the controller ican be used from the SDK CREATE TEST#1 USER STORY#2 As a player I want to see two ellipse figures displayed on my hands USER STORY#3 As a player when I raise my hand above my head the color of the ellipse is changing to black CREATE TEST#2 Connecting Kinect to Visual Studio Verify from customer requirements for feature Create architechture for feature Production tests Create function X Get kinect drivers Install Kinect SDK User story Task Bug Problem Team member#1 Team member#3 Team member#2

25 Alternative storyboard during sprint In Progress as several columns Backlog To Do Code Test Release Done FEATURE 1 As a player when I raise my hand above my head the color of the ellipse is changing to black CREATE TEST#2 Connecting Kinect to Visual Studio Verify from customer requirements for feature Create architechture for feature Production tests CREATE TEST#1 Create function X Get kinect drivers Install Kinect SDK FEATURE#2 As a developer I want to utilize User story Task Bug Problem Team member#1 Team member#3 Team member#2

26 Using electronical Kanban Boards

27 Simple Example Starting point at the beginning of iteration Planned tasks for the project

28 Simple Example (Work progressed)

29 Complex Example Starting point at the beginning of iteration User Stories are containing all tasks as sub items inside the card In progress lane organized to illustrate in which development phase the user story is This approach is also possible, but more advanced Recommendation is to keep the board simple

30 Complex Example (Work progressed)

31 TODO for project teams In teams that have been created, do following tasks: 1. Create your team space in Create identifier / name for the group. It will be used in team space URL: E.g. NUI_TEAM01.leankit.com Add all team members as users into project workspace

32 Sources for further details Books Peter Schuh, Integrating Agile Development in the Real World. Charles River Media, Inc. Geoffrey Moore, Crossing the Chasm. (revised 1999). Harper Business Essentials Shalloway, Beaver & Trott, Lean-Agile software development: Achieving enterprise agility Welin, M Agile Software Development. In publication: New Trends in Mobile and Web Development Lahti University of Applied Sciences. Tampere: Tampereen yliopistopaino Oy. Welin, M Kanban in Software Development. In publication: New Trends in Mobile and Web Development Lahti University of Applied Sciences. Tampere: Tampereen yliopistopaino Oy. Web resources

33 END