• Like

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Visual Studio 2010 Agile Tools (role based)

  • 1,485 views
Published

brief overview of agile tools in visual studio 2010, based on project roles

brief overview of agile tools in visual studio 2010, based on project roles

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

Views

Total Views
1,485
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
35
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • 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.

Transcript

  • 1. Visual Studio 2010Agile 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
    © 2010 Cardinal Solutions Group
  • 2. What is Agile?
    TIMEBOX ACTIVITY – 1 MIN
    © 2010 Cardinal Solutions Group
    2
    Please write down a few words or sentence on what Agile means to you.
  • 3. * AGILE
    Agile software development focuses on regularly delivering business value. It embraces change while leveraging feedback to produce high quality, desired results.
    © 2010 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. Why Agile? (Project Challenges)
    © 2010 Cardinal Solutions Group
  • 5. The Forrester Wave™: Agile Development Management Tools, Q2 2010, Forrester Research, Inc., May 5, 2010.
    © 2010 Cardinal Solutions Group
  • 6. Business requirements not actively managed
    Disparate tools and data
    Testing not aligned with business objectives
    Lack of defined process and guidance
    Limited visibility into project status to make decisions
    Communication issues between team members
    Common Challenges
    © 2010 Cardinal Solutions Group
  • 7. The path to any successful solutions requires negotiating many twists and turns.
    Idea is here
    Legacy Code
    Broken
    Builds
    Reporting overhead
    “No-Repro”
    Bugs
    Hardware
    costs
    Poor Estimation of cost and time
    Poor Documentation
    Integration Issues
    New Team Members
    No Shared
    Vision
    Poor Usability
    Solution is here
    Changing architecture
    Build Quality
    Heterogeneous Environment
    Scope Creep
    Quality concerns
    Changing Requirements
    © 2010 Cardinal Solutions Group
  • 8. Development Roles and Responsibilities
    Requirements Management
    QoS Management
    Business Analysts
    Requirements Analysis
    Project Planning
    Project Managers
    Task Assignment
    Architecture Modeling
    Bug Tracking
    Analysis and Design
    Architects
    Design for Deployment
    ?
    Development Executives
    Portfolio Management
    Project Organization
    UI Design
    Stakeholder Communication
    UI Designers
    UI Prototyping
    UI Flow Modeling
    Customer Support
    Operations
    Infrastructure Architecture
    Database Design
    Infrastructure Deployment
    DBAs
    Database Source Control
    Database Test Data Gen
    Test Case Management
    Testers
    Developers
    Code Analysis
    Manual Testing
    Unit Testing
    Load Testing
    Version Control
    Automated Testing
    © 2010 Cardinal Solutions Group
  • 9. Visual Studio 2010
    • No longer just a developer IDE
    • 10. TFS added server-side capability to manage the entire software lifecycle
    • 11. No need to license separate tools from HP/Mercury, IBM/Rational, Rally, etc…
    • 12. Already own with MSDN subscription
    © 2010 Cardinal Solutions Group
  • 13. The Microsoft Approach
    • Raise productivity from developer to development team
    Integration from the ground up
    Team communication without barriers
    Integrated quality tools for all
    Leverage existing development methodology
    Enable process improvement
    Provide transparency to the business
    © 2010 Cardinal Solutions Group
  • 14. VS2010 Updates
    Significant Process Template Updates
    Increased Project Transparency
    Improved Traceability
    Team Collaboration Innovations
    Productivity Improvements
    Automations & Integration Advancement
    Quality Support Expansion
    And a lot more
    11
    © 2010 Cardinal Solutions Group
  • 15. Out-of-the-Box Agile Support
    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
    © 2010 Cardinal Solutions Group
  • 16. As a Stakeholder, I want
    Visibility into a Project
    To be Heard
    Start using the final product
    13
    Visual Studio 2010 Answer
    SharePoint Dashboards, Reports
    Easy Bug Filings with Work Items
    © 2010 Cardinal Solutions Group
  • 17. © 2010 Cardinal Solutions Group
  • 18. As a Product Owner, I want
    ROI
    Effectively to Manage Work Queue
    Communicate Project Status
    15
    Visual Studio 2010 Answer
    Team Tools and Automations
    Work Item and query Improvements
    Reports
    © 2010 Cardinal Solutions Group
  • 19. Ad-Hoc reports in Microsoft Excel
    Product Backlog
    Iteration Backlog
    © 2010 Cardinal Solutions Group
  • 20. As a Business Analyst, I want
    Capture Requirements
    Collaborate with Team and End-Users
    17
    Visual Studio 2010 Answer
    Tools Integration
    Access to Work Items
    Alerts
    © 2010 Cardinal Solutions Group
  • 21. Tree Workitemsupport
    18
    © 2009 Cardinal Solutions Group
    © 2010 Cardinal Solutions Group
  • 22. As a Team (Tester), I want
    Know what to Test
    Tools to Help with Testing
    19
    Visual Studio 2010 Answer
    Test Impact Analysis, IntelliTrace
    Microsoft Test Manager
    Team Lab
    © 2010 Cardinal Solutions Group
  • 23. New WorkItem Types
    Test Step
    Shared Steps
    20
    © 2009 Cardinal Solutions Group
    © 2010 Cardinal Solutions Group
  • 24. As a Developer, I want
    To Know what to Develop
    Tools to Assist with Development
    21
    Visual Studio 2010 Answer
    Refactoring and Automation Tools
    New Functionality: ArcDB Tools
    Workflow Based Build, Gated Checkins
    © 2010 Cardinal Solutions Group
  • 25. © 2010 Cardinal Solutions Group
  • 26. As a Control Manager I want
    To Know what to Deploy
    Trace Production Code to Requirements
    Simplify Audit and Traceability Tasks
    23
    Visual Studio 2010 Answer
    Work Item Queries
    Build Reports
    Branch Visualization
    © 2010 Cardinal Solutions Group
  • 27. Focus on people, process and tools
    Overcome ComplexityQuality MindsetCulture of Innovation
    Collaboration
    Transparency
    Integration
    Clarity
    Alignment
    Efficiency
    AgileCustomizable Lightweight Patterns and Practices
    Highly integratedProductive Extensible Low admin
    © 2010 Cardinal Solutions Group
  • 28. Visual Studio ALM Solution
    Real-time reporting fromdata warehouse
    Audit trail for compliance
    Improve predictability and reduce risk
    Increase Project
    Transparency
    Approachable and intuitive products
    Tight integration across tools,process and roles
    Single integrated serverfor collaboration
    Facilitate Team
    Collaboration
    Lightweight, customizable process
    Integrated quality tools for each role
    Reduce defects andsecurity vulnerabilities
    Improve Software
    Quality
    © 2010 Cardinal Solutions Group
  • 29. Thank You
    @Leshka
    AGovorine@CardinalSolutions.com
    http://govorin.blogspot.com
    26
    Sharpen your Scrum Game
    Learn Visual Studio 2010
    http://www.scrum.org/about/alexei-govorine
    © 2010 Cardinal Solutions Group