• Like
  • Save
Managing business requirements in Agile (level 100)
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Managing business requirements in Agile (level 100)


How do you ensure that you are focusing your attention, efforts and resources on the highest-priority requirements, while managing change and cutting costs? Visual Studio provides teams with the …

How do you ensure that you are focusing your attention, efforts and resources on the highest-priority requirements, while managing change and cutting costs? Visual Studio provides teams with the ability to effectively manage requirements and collect feedback from customers. The new features in Team Foundation Server open an new world of possibilities to effectively manage requirements and drive customer feedback into the system to help prioritize and understand customer needs. We will show you how to gain cost savings, improve business processes, and increase efficiency with Microsoft’s ALM (application lifecycle management) strategy and toolset of Visual Studio and Team Foundation Server, while improving quality and delivery of modern applications.

Published in Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • How do you ensure that you are focusing your attention, efforts and resources on the highest-priority requirements, while managing change and cutting costs? Visual Studio provides teams with the ability to effectively manage requirements and collect feedback from customers. The new features in Team Foundation Server open an new world of possibilities to effectively manage requirements and drive customer feedback into the system to help prioritize and understand customer needs. Level 100 Description:Introductory and overview material. Assumes little or no expertise with topic and covers topic concepts, functions, features, and benefits.
  • Won’t cover dev/build/…Assuming an understanding of Agile and Scrum
  • Software development in enterprises and business organizations is a cross-functional undertaking. Barriers and chasms between the cross-functional teams that need to integrate in delivering software are the top impediments that hinder value delivery. Such impediments are usually a manifestation of rigid processes, ineffective collaboration tools, and development practices that do not take advantage of the advances in technology and opportunities to better integrate teams.
  • Note : the ALM circle/loop visual is commonly misinterpreted as implying a SCRUM affinity. The intent of the circle/loop is not to imply a SCRUM or Agile (Agile with a Caps A) alliance. The intent of the circle/loop visual is to reflect a continuous evolution of software investments and the notion of continuous value delivery. The Define, Develop, and Operate lifecycle phases and the impediments that can surface within/across them are methodology agnostic. Team barriers and boundaries result in value delivery impediments that adversely impact the entire software lifecycle from requirements definition to production deployment & operations, and continuous evolution to sustain new and incremental value delivery. The net adverse impact is increased cycle times in delivering value to take the business forward at the needed velocity.Presenter TODO : Select and drill down on an impediment in each of the lifecycle phases – Define, Develop, and Operate. Pick a mix of impediments that can be used to illustrate the following root causes : rigid processes (Ex : sequential/waterfall transition from development to testing)ineffective collaboration tools (Ex : lack of tools to enable continuous feedback loops with users, lack of integrations between tools used to manage development and operations workloads)development practices that do not take advantage of advances in technology and opportunities to better integrate dependent functions (Ex : not practicing acceptance test driven development, not using automated testing to validate business rules at the services layer, or DevOps practices to integrate development and operations teams in designing for operations and resolving production incidents)
  • Manage resources poolDefine new workCreate wireframe and Use CaseRevise the architectureCode the solutionRecord completed work daily Test the featuresTrack progress with reports and dashboards
  • Best tool for the job, based on role
  • Work items = artifact documentation, e.g. word template, predefined fields, sometimes predefined possible valuesQueries = Dynamic view, real time, of work items based on filter and criteriaReports = Reporting Services on SQL datawarehouse/cubeDocuments = pre-defined templates standardized for all and include XLS workbooks to be used to manage some of the workKanban + custom
  • Work items = artifactsQueries = dynamic viewsReports = SQL reporting (delay)Sharepointdashboarding
  • Also CMMIKanban boardPick the closest to your process and adapt
  • Ba/ui…tool already familiar with
  • Dev can see it in VSPO in web access…
  • Solicit early feedback from your stakeholders to improve quality and delivery
  • Want to use xls orpjt? Not a problem with bi-directional sync
  • Vs2012 – user story/PBI then tasks in TFS , other levels would be in XLS, pjt or …Now included in vs2013
  • Each team project is configured with one level of portfolio backlog using the Feature work item type. In addition, you can configure up to four additional levels of portfolio backlogs, In total, this provides you with seven levels from the top-level portfolio backlog to task. To access portfolio backlogs from an upgraded team project, you must configure them using the Configure Features wizard. Access to portfolio backlogs requires full access.
  • Ordering – drag and dropEffort
  • Forecasting based on velocity
  • Based on dates, velocity and capacity
  • Capacity report by assigned to
  • Capacity report by activity type
  • Drag and dropPersonnalize WIPStates
  • Remember reports/queries
  • VelocityBurndownCumulativeDepends on process template
  •  Modeling (Use, conceptual, activity, sequence, layer, etc.) Linked them to WI – done by architect/ba, can be viewed by dev in WI
  •  Few examplesCode duplicateCode metrics
  • From Administration panel2012 now supports the concept of multiple teams within a team projects.A Team is responsible for an areaSpecify the areas and iterations a team owns and the dates for sprints to occur. Create customized home pages for teams. Define and manage team favorites and team alerts.See status and gain quick access to team favorites from a lightweight dashboard.
  • Per teamprovide an area for fostering and capturing communication among team members, both near and far. Teams can discuss work in progress, ask questions, share status, and clarify issues that arise in real time.By using the team room instead of email threads, you automatically receive an audit trail of conversations and decisions
  • Testing without a pre-defined scriptAgain quality faster
  • SCOM – Service Center integrationCapture application issues in production and provide an actionable workflow between development and operations by leveraging System Center and TFS work items integration
  • See overall work effort
  • Easily manage: drag and drop and edit on board without opening WI
  • Logoincycle imageGold ALM partner Since 2002ServicesMVPLocations


  • 1. Managing business requirements in Agile Frederic Persoon,ALM Practice frederic.persoon@incyclesoftware.com
  • 2. Agenda
  • 3. ALM
  • 4. “Application lifecycle management (ALM) is the marriage of business management to software engineering made possible by tools that facilitate and integrate requirements management, architecture, coding, testing, tracking , and release management.” -Wikipedia Application lifecycle management
  • 5. Team barriers = value delivery impediments | |
  • 6. Continuous value without barriers Define • Requirements toolbox • User and stakeholder engagement Develop • Continuous testing • Continuous feedback • Acceptance test driven development • End-to-end traceability with PMO integration REQUIREMENTS WORKING SOFTWARE SHARED ARTIFACTS
  • 7. The scope
  • 8. TeamFoundation Server is the collaboration hub
  • 9. Typical scenario New project proposal Project Task Timesheet Business objectives New Change Yes Details Progress Time per Resource per day Approval Alignment Consolidation Roll-up of Progress Allocation update
  • 10. How it works – The basics
  • 12. Access
  • 13. TFS process templates
  • 14. Work items – Queries - Reports - SharePoint
  • 15. Scrum vs. Agile
  • 16. How it works – The features
  • 17. Insight - Define Feedback mechanism Work Item Microsoft Integration
  • 18. Storyboarding
  • 19. Storyboarding
  • 20. Storyboarding
  • 21. Feedback
  • 22. Integration
  • 23. Insight – Track and Monitor
  • 24. Enterprise agile project portfolios
  • 25. The hierarchy of requirements
  • 26. Work breakdown per team
  • 27. Portfolio backlog
  • 28. Product backlog
  • 29. Assign to sprint
  • 30. Sprint backlog
  • 31. Capacity planning
  • 32. Capacity planning
  • 33. Insight – visibility
  • 34. Board
  • 35. Web access– Queries - Reports - SharePoint
  • 36. Portfolio – Product - Sprint
  • 37. Insight – relationship, modeling & code Modeling the architecture Improve code quality
  • 38. Modeling
  • 39. Code analysis
  • 40. Insight – collaboration Team rooms
  • 41. Teams Multiple teams working on the same backlog
  • 42. Team rooms
  • 43. Insight – quality Production incidents
  • 44. Exploratory testing
  • 45. Loop back production incident
  • 46. Insight – Additional features Project server integration Extensibility
  • 47. Charting
  • 48. Project Server
  • 49. Extensibility
  • 50. Conclusion
  • 51. • You can manage multiple teams working on the same backlog; • You can manage several level of requirements; • You can forecast utilization and capacity; • You can easily manage your backlogs; • Real time visibility and transparency are build in; • Dashboards and reports are available to assess progress at a glance; and • Easy to loop in feedback and incidents into your backlog. VS-TFS fully supports your agile process
  • 52. QA InCycle Software – http://www.incyclesoftware.com – frederic.persoon@incyclesoftware.com Managing Business Requirements in Agile (Level 100)
  • 53. VM: http://blogs.msdn.com/b/briankel/archive/2013/08/27/new-lab-agile-planning-and-portfolio- management-with-team-foundation-server-2013.aspx What’s new in Planning and Tracking: http://msdn.microsoft.com/en-us/library/hh913786(v=vs.110) What’s New in 20122 RC: http://msdn.microsoft.com/en-us/library/bb386063(v=vs.110) Agile Planning and Iterations: http://msdn.microsoft.com/en-us/library/hh500404(v=vs.110) Customize Task Board : http://msdn.microsoft.com/en-us/library/hh739066(v=vs.110).aspx Engaging Stakeholders Through Continuous Feedback: http://msdn.microsoft.com/en- us/library/hh301769(v=vs.110) Enabling Data Flow Between TFS and Project Server: http://msdn.microsoft.com/en- us/library/gg455680(v=vs.110) Teams (An older Blog post): http://www.clemensreijnen.nl/post/2011/10/09/Teams-in-VS11.aspx http://msdn.microsoft.com/en-us/library/vstudio/dn306083(v=vs.120).aspx http://blogs.msdn.com/b/visualstudioalm/ http://msdn.microsoft.com/en-us/library/vstudio/hh913786(v=vs.120).aspx Estimate: http://msdn.microsoft.com/en-us/library/vstudio/hh765979(v=vs.120).aspx Ordering: http://msdn.microsoft.com/en-us/library/vstudio/hh765981(v=vs.120).aspx Analytics: http://msdn.microsoft.com/en-us/library/vstudio/jj620913(v=vs.120).aspx Additional Resources
  • 54. North American Leader in ALM Services
  • 55. Services & Solutions
  • 56. Visit www.incyclesoftware.com