Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

A comparative study of process templates in team

612 views

Published on

Describing and Comparing Scrum, Agile, CMMI.

Published in: Technology
  • Be the first to comment

A comparative study of process templates in team

  1. 1. A Comparative Study of Process Templates in Team Foundation Server (Agile, Scrum, CMMI) Amin Mesbahi – April 2017
  2. 2. Agenda • Introduction / Terminology • An overview on Application Lifecycle Management (ALM) • What is Team Foundation Server / Visual Studio Team Services ? • What is Process Template • Agile • Scrum • CMMI • Comparing Process Templates • Making ready your team • An overview on probable risks • Next steps!
  3. 3. Requirements management is the process of documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and continuous process throughout a project. Project management is the discipline of initiating, planning, executing, controlling, and closing the work of a team to achieve specific goals and meet specific success Terminology
  4. 4. • Agile software development describes a set of principles for software development under which requirements and solutions evolve through the functional teams • Scrum is an iterative and incremental agile software development framework for managing product development. the customers can change their minds about volatility), and that unpredicted challenges cannot be easily addressed in a Terminology
  5. 5. • A cross-functional team is a group of people with different functional expertise working toward a common goal • Agile and DevOps are similar, but, while agile software development represents a change in thinking and practice (that change in thinking and practice (that should lead to organizational change), DevOps places more emphasis on implementing organizational change to achieve its goals • The need for DevOps was born from the increasing popularity of agile software development, as that tends to lead to an increased number of releases. Terminology
  6. 6. • The Product Owner represents the product's stakeholders and the voice of the customer; and is accountable for ensuring that the team delivers value to the business. • Scrum Master, who is accountable for removing impediments to the ability of the team to deliver the product goals and team to deliver the product goals and deliverables. The Scrum Master is not a traditional team lead or project manager but acts as a buffer between the team and any distracting influences. The Scrum Master ensures that the Scrum framework is followed. Terminology
  7. 7. • Application lifecycle management (ALM) is the product lifecycle management (governance, development, and maintenance) of computer programs. It encompasses • requirements management • software architecture • computer programming • software testing • software maintenance • change management • continuous integration • project management • release management An overview on Application Lifecycle Management (ALM)
  8. 8. An overview on Application Lifecycle Management (ALM) Agile Tools Reporting Source Control Continuous Integration Release Management Test Management …
  9. 9. What is Team Foundation Server / Visual Studio Team Services ? Team Foundation Server Visual Studio Team Services On-promise Cloud Git, TFVC Agile Tools Continuous Integration Tools for Java Teams Reporting Release Management Package Management DevOps Enterprise Ready Testing Tools Cloud based load testing Marketplace Extend and Integrate
  10. 10. • A process defines the building blocks of the work item tracking system and supports the Inheritance process model for Team Services. • A process template defines the building blocks of the work item tracking system as well as other sub-systems you access through Team Services or an on-premises Team Foundation Server (TFS). It supports Hosted XML and On-premises XMl process models which support customization of team projects through the modification and import of XML definition files. What is Process Template
  11. 11. Scrum Choose Scrum when your team practices Scrum. This process works great if you want to track product backlog items (PBIs) and bugs on the Kanban board, or break PBIs and bugs down into tasks on the task board. This process supports the Scrum methodology as defined by the Scrum organization. Tasks support tracking remaining work only.
  12. 12. Choose Agile when your team uses Agile planning methods, including Scrum, and tracks development and test activities separately. This process works great if you want to track user stories and (optionally) bugs on the Kanban board, or track bugs and tasks on the task board. You can learn more about Agile methodologies at the Agile Alliance. Tasks support tracking Original Estimate, Remaining Work, and Completed Work. Agile
  13. 13. Choose CMMI when your team follows more formal project methods that require a framework for process improvement and an auditable record of decisions. With this process, you can track requirements, change requests, risks, and reviews. This process supports formal change management activities. Tasks support tracking Original Estimate, Remaining Work, and Completed Work. CMMI (Capability Maturity Model Integration)
  14. 14. Main distinctions among the default processes
  15. 15. Workflow states, transitions, and reasons Scrum Agile CMMI Epic EpicEpic
  16. 16. Workflow states, transitions, and reasons Scrum Agile CMMI Feature FeatureFeature
  17. 17. Workflow states, transitions, and reasons Scrum Agile CMMI Product backlog item RequirementUser story
  18. 18. Workflow states, transitions, and reasons Scrum Agile CMMI Bug BugBug
  19. 19. Workflow states, transitions, and reasons Scrum Agile CMMI Task TaskTask
  20. 20. Workflow states, transitions, and reasons Scrum Agile CMMI Task TaskTask
  21. 21. Work item types added to all processes Teams create and work with these types using the corresponding tool: • Test Plan, Test Suite, Test Case Shared Steps, and Shared Parameters: Microsoft Test Manger. • Feedback Request and Feedback Response: Request feedback. • Code Review Request and Code Review Response: My Work (from Team Explorer) and Code Review Request.
  22. 22. WITs that support the test experience
  23. 23. More Details About Scrum Process
  24. 24. More Details About Scrum Process
  25. 25. More Details About Agile Process
  26. 26. More Details About Agile Process
  27. 27. More Details About CMMI Process
  28. 28. More Details About CMMI Process
  29. 29. More Details About CMMI Process Acronym Process Area CAR Causal Analysis & Resolution CM Configuration Management DAR Decision Analysis & Resolution IPM Integrated Project Management MA Measurement & Analysis OID Organizational Innovation & Deployment OPD Organizational Process Definition OPF Organizational Process Focus OPP Organizational Process Performance OT Organizational Training PI Product Integration Acronym Process Area PMC Project Monitoring & Control PP Project Planning PPQA Process & Product Quality Assurance QPM Quantitative Project Management RD Requirements Definition REQM Requirements Management RSKM Risk Management SAM Supplier Agreement Management TS Technical Solution VER Verification VAL Validation
  30. 30. Agile working is a culture! And not a project management software. We need a culture that promotes the environment of trust, collaboration, and cooperation for achieving business objectives. Too many teams facing failures by their agile-enemy culture… Making ready your team
  31. 31. An overview on probable risks 1. Choosing inappropriate process template 2. Working with lazy and unskilled people 3. Dealing with bad customers 4. Overestimating and Underestimating 5. Accepting project you cannot doing them
  32. 32. • Capacity Planning • Storyboarding • Sprint Analysis • Measuring Improvements • Responsibility (against changes, team, customer, market) • …  Next steps!
  33. 33. Q & A Q&A Thank you Amin Mesbahi, 20 April 2017

×