Zen tao introduction
0 likes22 views
The document discusses project management for software development, highlighting the evolution of methodologies from traditional models like Waterfall to Agile frameworks such as Scrum and Extreme Programming. It emphasizes key roles, practices, and meetings within the Scrum process, including sprint planning, daily scrums, and retrospectives, to enhance efficiency and product quality. Additionally, it introduces the Zentao tool for supporting project management and bug tracking throughout the development lifecycle.
Zen tao introduction
- 1. ZENTAO SCAN ME ZENTAO LECTURE ZenTao, A Professional Solution for Software Development Projects 2020
- 2. PROJECT AND PROJECT MANAGEMENT PROJECT A temporary endeavor undertaken to create a unique product or service. PROJECT MANAGEMENT The application of knowledge, skills, tools, and techniques to project activities to meet the project requirements. PAGE 01PAGE 01
- 3. PROJECT MANAGEMENT DEVELOPMENT PROJECT MANAGEMENT HELLO WORLD the concept of project management rose after World War II methods and standards are made in the US as a model CMMI and PMBOOK as standards mainly for engineering projects development project management comes with computers manages the software development projects early development project management learned from engineering project management waterfall model as the mainstream PAGE 02SOFTWARE DEVELOPMENT PROJECT MANAGEMENT
- 4. Requirements Design Implementation Verification Maintenance clear stages easy operation successful cases PAGE 03WATERFALL MODEL
- 5. Fast fish eat slow ones Complex software no iterative work Not the result as expected Now Require high qulaity Release via physical media High aftersakes cost Mild competition Past PAGE 04HISTORY OF SOFTWARE DEVELOPMENT Unlimited requirements B/S as mainstream SAAS Fast delivery and intense competition
- 6. 1990s Various theories and methods came out SCRUM 1995 Scrum is put forward by Ken Schwaber and Jeff Sutherland ... 1999 Kent Beck published Extreme Programming Explained · Individuals and interactions over processes and tools · Working software over comprehensive documentation · Customer collaboration over contract negotiation · Responding to change over following a plan 2001 PAGE 05NEW METHODS Methods Extreme Programming Agile Manifesto
- 7. PAGE 06 SCRUM Rugby Relay Race Waterfall Address complex adaptive problems, while productively and creatively delivering products of the highest possible value. According to business value, priority should be given to high priority functions. Iterating in sprint, including product design, development and testing (2-4 weeks). Implement independent management, continuously improve the internal process efficiency. Stable release rhythm, get feedback and adjust accordingly. No specific engineering practice (Scrum + XP). SCRUM KEYWORDS
- 8. · 5~7 team members · Cross functional: development, testing, design, etc · Self-managed TEAM · Define product features · Determine the content and date of product release · Responsible for the input and output of products · Adjust the priority of user stories according to market · Agree or reject the increment PRODUCT OWNER SCRUM MASTER · Directly manage the project · Lead the team to complete scrum practice and implement its value · Solve problems encountered in the team · Ensure team efficiency and status · Coordinate and communicate within the team PAGE 07SCRUM ROLES
- 9. Sprint Planning · Analyze and evaluate product backlog · Select for sprint backlog · according to the story priority · Task breakdown · Estimate tasks in hours Daily Scrum · Held every day · Stand up for a meeting · Describe what you did yesterday and what to do · Invite all relevant personnel to attend · Only team members speak · Avoid irrelevant discussions Sprint Review · Increment demonstration once the sprint is done · Prepare the demo in advance · All team members shoul take part in · Invite people who want to get updates of the product Sprint Retrospective Story splitting Task breakdown Held daily Report work Demo & review Lessons learned PAGE 08 · Review and learn from this sprint · All team members should take part in · Prepare for the next sprint 4 SCRUM MEETINGS
- 10. PRODUCT BACKLOG An ordered list of everything that is known to be needed in the product The single source of requirements for any changes to be made to the product Product Owner is responsible for the Product Backlog, including its content, availability, and ordering. SPRINT BACKLOG Developers decide which tasks they will do Tasks are not assigned Each task has someone to be responsible for it As work is performed or completed, the estimated remaining work is updated. X-Axis: The project/iteration timeline Y-Axis: The work that needs to be completed for the project. The time or story point estimates for the work remaining will be represented by this axis. BURNDHOWN CHART PAGE 09SCRUM OUTPUT
- 12. PLANNING 01 Paired programming Planning game Test Driven Development Customers as part of the team MANAGING 02 Continuous integration Restructure Build release DESIGNING 03 Coding standards Collective code ownership Simple design System metaphor CODING 04 Communicate with customers any time Unit test first Only one pair integrates code at a time Delay optimization Rhythmic work TESTING 05 Cross test Automated testing Unit test Pass all unit tests before releases Write test cases right after reporting bugs ...... PAGE 11EXTREME PROGRAMMING
- 14. Bug Tracking Testers and developers fix bugs to ensure product quality Documentation Track, store and control attachements and files Test Case Easy to manage test results and report bugs Release Plan the release of products Prioritize stories Build Define the scope of the test Roadmap Intuitive display of releases and unexpired plans PAGE 13NEW CONCEPTS
- 15. Story Product Owner Development Test Team STORY TASK CASE BUG NEW FEATURES PAGE 14 · The concepts of product, project, and test are clearly defined · Product team, dev team and QA team coordinate with each other · The three teams work on stories, tasks, and bugs to deliver the product
- 16. Feedback Update Tasks Update Burndown Daily Scrum TASK Product Owner Scrum Master Dev Team Test Team Link Create Projects Story Breakdown Create Build Test Request Create Release Sprint Estimate & Claim Tasks Write CasesStory1-3 Plan1 Plan2 Case List Reject Report Bug Pass Link Improvement Sprint Review Sprint Retrospective Increment Pro duct Story4-6 Sprint Backlog Story1--P1 Story4--P2 Story3--P4 GO! ZENTAO WORKFLOW PAGE 15
- 17. THANKS Visit ZenTao and get a free trial zentao.pm