Effective Team Management with VSTS and TFS (eBook)

Chaminda Chandrasekara is Microsoft Most Valuable Professional (MVP) for Visual Studio ALM and Scrum Alliance Certified ScrumMaster®, who believes in continuous improvement of Software Development Life-cycle. He works as the ALM/DevOps Architect for Datavail, Sri Lanka, a fully owned subsidiary of Datavail Corporation, based in United States of America.  He is an active Microsoft Community Contributor (MCC), well recognized for his contributions in Microsoft forums, TechNet galleries, Wikis, stackoverflow and contributes extensions to Visual Studio Team Services/TFS, in Microsoft Visual Studio marketplace. He also contributes to other open source projects in GitHub. Chaminda published his first book, Beginning Build and Release Management with TFS 2017 and VSTS, in June 2017. Sanjaya Yapa currently work as Microsoft Dynamics CRM Consultant at Oaktan Pty Ltd Australia, who has more than 12 years of experience in the industry. He has been working with various Microsoft technologies since 2005 and possess wealth of experience in Software Development, Team Leadership, Product Management and Consultancy. He specializes in Dynamics CRM and Application Life Cycle Management. 

Chapter 1:  How to handle teamsChapter Goal: Explains what are the challenges with ideal size teams and large size teams. Then gives an explanation on how to effectively use VSTS/TFS features to overcome those challenges.No of pages 25Sub -Topics1. What are the challenges faced with ideal size teams?2. What can be done to resolve issues in an ideal size team with TFS/VSTS3. What are the challenges faced with larger teams?4. What can be done to resolve issues in larger teams with TFS/VSTS5. How to work with when project/product goes to productionChapter 2:  Working with a BacklogChapter Goal: Using VSTS/TFS features to effectively manage a backlog/portfolio backlog. Working with stakeholders closely to better understand the requirements and getting the entire team into a common understanding regarding the requirements.No of pages: 20Sub - Topics 1. Getting stakeholder feedback2. Planning for team process3. Grooming the requirement and test criteria4. Prioritizing and sizing the requirements5. Planning the first iterationChapter 3:  Working on the IterationChapter Goal: You will learn how to facilitate the team needs while executing the development cycle. You will also learn how to detect risks and challenges early using the capabilities of VSTS/TFS and apply practical solutions to them.No of pages : 60Sub - Topics:1. Daily activity planning 2. Tracking and resolving impediments3. Monitoring the progress while avoiding micro management 4. Facilitating disaster situations during the iteration5. Avoiding defects rather than fixing defects 6. Facilitating unavoidable and mandatory fixes7. Ensuring the stability of the release 8. Visualizing progress of the iteration and positively impacting the team Chapter 4: Work after an IterationChapter Goal: Exploring how to perform the post execution analysis and planning for next development cycle and forecasting using.No of pages: 15Sub – Topics1. Monitoring overall progress of the software2. Evaluating the outcome of an iteration 3. How to plan the future iteration after reprioritization and re-estimationChapter 5: Roadmap/Project Plan and ResourcesChapter Goal: You should be able to learn how to create the project road map/plan the project time liens using the features of VSTS/TFS. This chapter also covers the integration with other Microsoft tools and none Microsoft tools to facilitate team and management needs.No of pages: 15Sub - Topics:  1. Planning your roadmap/project2. Facilitating business analysis with office and mobile integration 3. Providing the visibility required to the higher management with effectively utilizing resources Chapter 6: Adopting VSTS/TFS to your team’s processChapter Goal: In this chapter, you will discover how to alter the behavior of the VSTS/TFS to represent your process. No of pages: 15Sub - Topics: 1. Introducing your own process workflow into VSTS/TFS.2. Could (VSTS) vs. On premises (TFS) for your team