Visual Studio 2010 Agile Tools (overview)
•Download as PPTX, PDF•
3 likes•1,501 views
brief overview of agile tools in visual studio 2010
Recommended
More Related Content
What's hot
What's hot (18)
Similar to Visual Studio 2010 Agile Tools (overview)
Similar to Visual Studio 2010 Agile Tools (overview) (20)
Visual Studio 2010 Agile Tools (overview)
- 1. Visual Studio 2010 Agile Tools in 15 minutes Alexei V. Govorine ALM Consultant | Cardinal Solutions Group Visual Studio ALM MVP, Microsoft Virtual TSP Professional Scrum Developer Trainer Agovorine@CardinalSolutions.com http://govorin.blogspot.com http://www.twitter.com/Leshka 1 © 2009 Cardinal Solutions Group
- 2. Enter name here WHAT IS AGILE? TIMEBOX ACTIVITY – 1 MIN © 2006 Cardinal Solutions Group 2 Please write down a few words or sentence on what Agile means to you.
- 3. Enter name here * AGILE Agile software development focuses on regularly delivering business value. It embraces change while leveraging feedback to produce high quality, desired results. © 2009 Cardinal Solutions Group 3 * Different for every company Agile is a Movement Represented by Methodologies & Frameworks Comprised of a set of Development & Engineering Practices
- 4. Enter name here Why Agile? (Project Challenges) 4 © 2010 Cardinal Solutions Group
- 5. Enter name here The Forrester Wave™: Agile Development Management Tools, Q2 2010, Forrester Research, Inc., May 5, 2010.
- 6. Enter name here Development Roles and Responsibilities Project Managers Business Analysts Architects UI Designers DBAs DevelopersTesters Operations Development Executives Requirements Management QoS Management Requirements Analysis Architecture Modeling Analysis and Design Design for Deployment UI Design UI Prototyping UI Flow Modeling Database Design Database Source Control Database Test Data Gen Code Analysis Unit Testing Version Control Test Case Management Manual Testing Load Testing Automated Testing Customer Support Infrastructure Architecture Infrastructure Deployment Portfolio Management Project Organization Stakeholder Communication Project Planning Task Assignment Bug Tracking
- 7. Enter name here Visual Studio 2010 • No longer just a developer IDE • TFS added server-side capability to manage the entire software lifecycle • No need to license separate tools from HP/Mercury, IBM/Rational, Rally, etc… • Already own with MSDN subscription.
- 8. Enter name here • Improved MSF Agile V5.0 process template – Agile Workbooks • Product Backlog • Iteration Backlog • Visual Studio Scrum V1.0 process template – Adherence to Scrum terminology • 3rd Party Templates
- 9. Enter name here – Product Backlog – Iteration Backlog
- 10. Enter name here • Ease of Accessing Projects Artifacts • Improved Data warehouse and SQL Reports • New Excel Reports and Planning Tools • Rich API for Integrations
- 11. Enter name here Task hours getting completed… Tasks are getting closed…
- 12. Enter name here Test are passing… Are the builds healthy? Bugs reactivations are low…
- 13. Enter name here • Re-design Work Items – Linking – New types: Test Case, Shared Steps • from Requirements to Production Deployment • Rich Toolset
- 14. Enter name here Tree Workitem support © 2009 Cardinal Solutions Group 18
- 15. Enter name here New WorkItem Types • Test Step • Shared Steps © 2009 Cardinal Solutions Group 19
- 16. Enter name here Are we making progress on running test plans? How many test plans failed? How many bugs are found?
- 17. Enter name here • Ease of Accessing Projects Artifacts • Improved Data warehouse and SQL Reports • New Excel Reports and Planning Tools • Rich API for Integrations
- 18. Enter name here Team Explorer
- 19. Enter name here Team Project portal
- 20. Enter name here Ad-Hoc reports in Microsoft Excel • Workbook queries with Microsoft Office Excel. – Fast and flexible
- 21. Enter name here • Support for all Team Roles – Product Owners, Stakeholder, Project Managers, Business Analysts, Architects, Database Developers, Testers, Control Management, Infrastructure, Support, etc • New Products • Improved Refactoring • Simplified Builds
- 22. Enter name here • Workflow based builds – Support Continuous Integration – Support Continuous Deployment • Team Lab • Power Shell Support
- 23. Enter name here Test % passing… Code % covered… Code % changed…
- 24. Enter name here Lines of code tested… Lines of code changed…
- 25. Enter name here • Test Manager • Team Lab • Rich Bug Filing • Improved Testing tools
- 26. Enter name here Bugs are resolved steadily… Bugs count by person…
- 27. Enter name here Overcome Complexity Quality Mindset Culture of Innovation Collaboration Transparency Integration Highly integrated Productive Extensible Low admin Clarity Alignment Efficiency Agile Customizable Lightweight Patterns and Practices Focus on people, process and tools
- 28. Enter name here Visual Studio ALM Solution Increase Project Transparency Facilitate Team Collaboration Improve Software Quality Approachable and intuitive products Tight integration across tools, process and roles Single integrated server for collaboration Real-time reporting from data warehouse Audit trail for compliance Improve predictability and reduce risk Lightweight, customizable process Integrated quality tools for each role Reduce defects and security vulnerabilities
- 29. Enter name here Thank You • @Leshka • AGovorine@CardinalSolutions.com • http://govorin.blogspot.com © 2009 Cardinal Solutions Group 33 • Sharpen your Scrum Game • Learn Visual Studio 2010 • http://www.scrum.org/about/alexei-govorine
Editor's Notes
- Agile development is not a methodology in itself. It is an umbrella term that describes several agile methodologies. At the signing of the Agile Manifesto in 2001, these methodologies included Scrum, XP, Crystal, FDD, and DSDM. Since then, Lean practices have also emerged as a valuable agile methodology and so are included under the agile development umbrella in the illustration later in this topic.Each agile methodology has a slightly different approach for implementing the core values from the Agile Manifesto, just as many computer languages manifest the core features of object-oriented programming in different ways. A recent survey shows that about 50 percent of agile practitioners say that their team is doing Scrum. Another 20 percent say that they are doing Scrum with XP components. An additional 12 percent say that they are doing XP alone. Because more than 80 percent of agile implementations worldwide are Scrum or XP, MSF for Agile Software Development v5.0 focuses on the core processes and practices of Scrum and XP.Our highest priority is to satisfy the customerthrough early and continuous deliveryof valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
- The path to any successful solution is a long and winding road with many challenges along the way. From initial idea to eventual solution the challenges can be numerous and varied. There are many reasons why software projects fail and not all failing reasons are the same. One of the biggest reasons why 44% of projects are challenged relates to two issues:Estimation – Over 50% of projects will cost almost 200% of their original budget. These cost overruns make the whole process problematic and may result in projects being cancelled. Scope Management – Large projects only deliver a little over 40% of features that they originally planned (but that does not mean they have not added more features or spent loads of time on the 60% features they did not deliver writing specs etc..).When you look at the macro level it tends to be associated with value and predictability:Predictability – On top of general estimation providing feedback loops into the process that allow directional changes and make the right decisions is crucial.Value – Building the right software is massive. Most organizations do a very poor job of deciding what software to build and if doing x is more important than y.In terms of engineering issues that make projects fail. Classical problems are:Build quality – Not having a well-defined, predictable build process and instead having a random approach to build management. This causes many problems in terms of quality, with teams unable to answer the question ‘didn’t we fix this’, and operations deploying the wrong software.Integration Hell – When everything is complete at the unit level it is then input into integration and everyone finds everything does not play well together.Analysis paralysis – Consensus is important, but the amount of time thinking, talking and sharing requirements can deeply reduce effectiveness of development.Chinese whispers – with many classical development approaches, artifacts are handed off with very little support collaboration and support. This leads to problems be re-solved and different ideas creeping into the development process. The bigger the artifacts the more likely that is.Of course there are individual issues that if not managed can cause project failure in the areas of architecture and quality. But the majority of those issues manifest themselves in second or third releases. These include:Low Cohesive and High Coupling – at the heart of any poor architecture is bad structure. Regression testing backlog – As you grow the software it becomes more and more expensive and time consuming to test.Poor documentation – the majority of legacy systems are maintained by trial and error, as no one understands them.
- Set the stage for Dev is on par with several other stake holders in the enterprise. What are you using today to aggregate and rationalize the data and work flow????
- With Visual Studio 2010 the investment in Agile continues. The Agile process template has been improved and now has out-of-the-box tools for Agile teams. This increased level of Agile support means that you can take advantage of best practices including creating and maintaining a Product Backlog, planning iterations with an eye on previous performance—including managing planned interruptions such as holidays and Spikes, and managing status with an Excel based burndown.The new Agile Planning Workbooks enable you to use the most popular tool used by Agile teams and Scrum masters – Microsoft Office Excel. The new Product Backog and Iteration Backlog workbooks enable you to plan your efforts with a light weight easy to use tool that is completely integrated with your team’s repository, Team Foundation Server. As you add user stories to the Product Backlog, they are added as new work items in Team Foundation Server. As you distill stories into tasks, those too are added as new work items in Team Foundation Server. Finally you have light-weight, easy to use Agile planning tools that integrate with Team Foundation Server right out of the box.
- With Visual Studio 2010 the investment in Agile continues. The Agile process template has been improved and now has out-of-the-box tools for Agile teams. This increased level of Agile support means that you can take advantage of best practices including creating and maintaining a Product Backlog, planning iterations with an eye on previous performance—including managing planned interruptions such as holidays and Spikes, and managing status with an Excel based burndown.The new Agile Planning Workbooks enable you to use the most popular tool used by Agile teams and Scrum masters – Microsoft Office Excel. The new Product Backog and Iteration Backlog workbooks enable you to plan your efforts with a light weight easy to use tool that is completely integrated with your team’s repository, Team Foundation Server. As you add user stories to the Product Backlog, they are added as new work items in Team Foundation Server. As you distill stories into tasks, those too are added as new work items in Team Foundation Server. Finally you have light-weight, easy to use Agile planning tools that integrate with Team Foundation Server right out of the box.
- With Visual Studio 2010 the investment in Agile continues. The Agile process template has been improved and now has out-of-the-box tools for Agile teams. This increased level of Agile support means that you can take advantage of best practices including creating and maintaining a Product Backlog, planning iterations with an eye on previous performance—including managing planned interruptions such as holidays and Spikes, and managing status with an Excel based burndown.The new Agile Planning Workbooks enable you to use the most popular tool used by Agile teams and Scrum masters – Microsoft Office Excel. The new Product Backog and Iteration Backlog workbooks enable you to plan your efforts with a light weight easy to use tool that is completely integrated with your team’s repository, Team Foundation Server. As you add user stories to the Product Backlog, they are added as new work items in Team Foundation Server. As you distill stories into tasks, those too are added as new work items in Team Foundation Server. Finally you have light-weight, easy to use Agile planning tools that integrate with Team Foundation Server right out of the box.
- With Visual Studio 2010 the investment in Agile continues. The Agile process template has been improved and now has out-of-the-box tools for Agile teams. This increased level of Agile support means that you can take advantage of best practices including creating and maintaining a Product Backlog, planning iterations with an eye on previous performance—including managing planned interruptions such as holidays and Spikes, and managing status with an Excel based burndown.The new Agile Planning Workbooks enable you to use the most popular tool used by Agile teams and Scrum masters – Microsoft Office Excel. The new Product Backog and Iteration Backlog workbooks enable you to plan your efforts with a light weight easy to use tool that is completely integrated with your team’s repository, Team Foundation Server. As you add user stories to the Product Backlog, they are added as new work items in Team Foundation Server. As you distill stories into tasks, those too are added as new work items in Team Foundation Server. Finally you have light-weight, easy to use Agile planning tools that integrate with Team Foundation Server right out of the box.