mfeighner created the topic: Five Key Enterprise Development Trends
- Understanding the Feature Path from TFS 2013
- TFS 2013 Update Timeline
- Agile Tools
- Demo: Agile Tools
- Demo: Git Improvements
- Demo: Git CodeLens
- Demo: Pull Requests
- Demo: Testing Features
- Install Options
- TFS Pre-upgrade Tool
- Demo: Pre-upgrade Process
- Upgrading to TFS 2015
- Demo: Upgrade from TFS 2013 to TFS 2015 Update2
- Demo: Verify the Upgrade
- Demo: Project Rename
- Portfolio Management
- Demo: Epics
- Demo: Features
- Product Backlog
- Demo: Product Backlog
- Demo: Kanban Board Intro
- Demo: Kanban Columns
- Demo: Kanban Swimlanes
- Demo: Kanban – Working with Tasks
- Demo: Customizing the Cumulative Flow Diagram
- Demo: Customizing Working Days
- Demo: Customizing Bugs on the Backlog
- Demo: Creating Work Item Templates
- Demo: Quick Search
- Sprint Planning
- Demo: Capacity Planning
- Demo: Sprint Planning
- Demo: Sprint Progress
- Tracking Work
- Demo: Charts and Alerts
- Demo: Working with Dashboards
- Version Control Enhancements
- Demo: Git Branching Enhancements
- Demo: Working with Git Branches
- Git Rebase
- Demo: Git Rebase
- Git Branch Policies
- Demo: Configure Branch Policies
- Demo: Create a Pull Request
- Demo: Resolve Branch Policy Issues
- Quick Code Edit
- Demo: Quick Code Edit
- Build Agent
- Demo: Configure a Build Agent
- Demo: Build Capabilities
- Build Definition
- Demo: Create a Build Definition
- Running a Build
- Demo: Running a Build
- Build Customization
- Demo: Customize a Build and View Test Results
- Demo: Customize with Build Steps
- Demo: Multiple Configurations and Parallel Builds
- Demo: Build Triggers – Continuous Integration and Pull Requests
- Demo: Capabilities and Demands
- Demo: Build Definition History
- Demo: Build Definition Templates
- Test Hub1
- Demo: Create a Test Plan
- Demo: Create Test Suites
- Demo: Create Test Cases
- Demo: Create Test Cases from the Grid View
- Demo: Shared Steps
- Demo: Test Parameters
- Demo: Shared Parameters
- Demo: Running Tests
- Demo: Test Run Analysis
- Demo: Export Test Plans
- Exploratory Testing Extension
- Demo: Install Exploratory Testing Extension
- Demo: Exploratory Testing
- Demo: Exploratory Testing Results
- Kanban Integration
- Demo: Creating Test Cases from the Kanban Board
- Demo: Installing Marketplace Extensions
- Demo: Working with Extensions
- Demo: Manage Extensions
- Creating Extensions
- Demo: Create an Extension
- Demo: Packaging Extensions
- Demo: Install an Extension
- TFS 2015 API
- Demo: TFS 2015 API
- Service Hooks
- Demo: Service Hooks
Software development has traditionally suffered from producing end products with a definite lack of inherent quality. The symptoms of this quality lack are listed here:
- Software development projects are often delivered late and over budget.
- Often the delivered product does not meet customer requirements and is never used.
- Software products simply do not work right.
As we look into the symptoms of our software development malaise, five principal issues related to software development arise.
Lack of Visibility
Software is conceptual in nature. Unlike a bridge, a building, or another physical structure, it is not easy to look at software and assess how close it is to completion. Without strong project management, “software is 90% complete 90% of the time.” Through the adoption of SCM policy and the definition of the configuration management model of the software under development, all CIs, components, and subcomponents are immediately visible for versions, releases, and product families.
Lack of Control
Because software is inherently intangible, it is also more difficult to control. Without an accurate assessment of progress, schedules slip and budgets are overrun. It is hard to assess what has been accomplished and what remains to be done. SCM provides the mechanism for controlling the project through measuring the amount of effort compared to the project management plan and estimating the future effort based on past work.
Lack of Traceability
A lack of linkage between project events contributes to project failures. The main benefit of SCM is providing the traceability among versions, releases, and product families. The value of this traceability is enormous when a problem arises in one release or product family that impacts other client releases and products. Making one change and promoting that through the entire product software base is an incredible cost savings in time, money, and client good will. A lack of linkage between project events contributes to project failures where solving one problem either exacerbates a problem in another area or fails to fix the same problem elsewhere. A traceability thread allows management to examine the chain of events that caused a project to encounter difficulty as an integral process within the auditing capability of SCM. A project becomes a year late one day at a time unless the effort reported on the schedule maps to the actual work being done and traced within the software configuration management system.
Lack of Monitoring
Without traceability and visibility, monitoring of software development projects becomes extremely difficult. Management cannot make informed decisions, and thus schedules slip further and costs continue to exceed budget.
There is no way to monitor a project when the project manager has no tools to look into the actual product development within the project. SCM provides the tools that open up the process to external monitoring. With SCM in place and a policy of traceability and visibility accepted, monitoring of software development projects becomes a simple part of the overall project management task. Management makes informed decisions avoiding schedule slips and budget excesses through the monitoring available with SCM tools and the integral workings of the CCB.
Software is very malleable; it is idea-stuff, and customers constantly have new ideas for it. People would rarely ask a bridge constructor to make the kinds of changes midproject that software customers tend to request. The impact of such changes can be just as great. All SCM tools, along with the CCB, support a mechanism for appropriate change control.
SCM Interacts with Verification and Validation
SCM is most important, and most often neglected, during V&V activities, which include software testing. It is employed in tracking which module versions are included in a particular system build, as well as which tests have been run. The results of the tests are tied directly to the modules or subcomponents being tested. Many times there are “action items” resulting from the tests. SCM tracks the action item status, so overall system status can be assessed well before final builds and releases are done.
Verification and validation testing are supported through the four basic SCM processes: identification, control, auditing, and status accounting. Let’s look at examples of V&V testing in the context of each of these components.
SCM Identification Benefits to V&V
- Automatic preparation of release notes
- List of changed software modules
- Definition of development baseline
- Generation of incident reports
- Definition of operational baseline
- Control of the configuration item identification
- Management of CCB meetings
- Prioritization of test and incident issues
- Establishment of turnover dates
- Approval of audit and test reports
- Approval of incident report resolutions
SCM Auditing Benefits to V&V
- Comparison of new baseline to previous baseline
- Assurance that standards have been met
- Audit trail of the testing process (verification, validation, and acceptance) of the software system
- Documentation of experience with technical aspects of system engineering or software engineering
SCM Status Accounting Benefits to V&V
- Logging and tracking of incident reports
- Publication of CCB minutes
With all of these potential benefits of SCM, project managers must address real-world considerations. Management commitment is the real key to implementing SCM on a specific project in a given organization. By treating the implementation of SCM as a project, the project plan must start at the top to secure commitment to checks and balances. Now is the time to bring out the organization’s list of project disasters to draw on management experience with their previous software project difficulties. If there are no historic disasters in the organization, or if it is inappropriate to discuss them, refer to literature articles that provide accounts of project disasters (refer to the Web resources at the end of this chapter). Finally, after putting a notional return-on-investment financial argument in place, explain the intangible benefits of SCM.
One of the major sources intangible benefits is auditing. Auditing can be a heavy consumer of configuration management resources, and management may question the benefit of this kind of expenditure. Auditing pays for itself through the avoidance of larger, unnecessary expenses. Savings of 100:1 (large projects) or 4–6:1 (small projects) are obtained by finding and fixing problems early in the life cycle. The auditing process in SCM uncovers the areas where a little more effort or control will result in higher-quality software products and lower overall project costs.
There can be audit compromises to reduce costs. As a project manager, plan audits based on both the phases of the life cycle and the frequency of builds, versions, releases, and product families. Auditing each baseline in a project while reducing the depth of each audit maintains some traceability with loss of visibility.
Eliminating one or more audits (installation baseline, for example) maintains visibility but slightly impacts traceability.