Agile and ALM by example : managing the whole application lifecycle

Get Started. It's Free
or sign up with your email address
Rocket clouds
Agile and ALM by example : managing the whole application lifecycle by Mind Map: Agile and ALM by example : managing the whole application lifecycle

1. Project Management

1.1. Project Management

1.1.1. Project

1.1.1.1. Budgeting

1.1.1.2. Transverse Tasks

1.1.1.3. Work Breakdown Hierarchy

1.1.1.4. Epic

1.1.1.5. Product Backlog Items

1.1.2. Project Dashboard

1.1.2.1. Product Burndown by Project

1.2. Iteration Management

1.2.1. Iteration plan

1.2.1.1. Product Backlog Items...

1.2.1.2. ...according their Story Points...

1.2.1.3. ...and Velocity

1.2.2. Tasks

1.2.2.1. Tasks estimation

1.2.2.2. Completed & remaining work tracking on Tasks

1.2.3. Done Story Points

1.2.3.1. Story Points

1.2.3.2. Definition of Done

1.2.4. Iteration closing

1.2.4.1. Retrospective

1.2.4.2. Velocity update

1.2.5. Iteration Dashboard

1.2.5.1. Velocity

1.2.5.2. Iteration Burndown (with Points)

1.2.5.3. Iteration Burdown by Project (with Points)

1.2.6. Team Member Dashboard

1.2.6.1. Process auto-controls

2. Engineering

2.1. Continuous Integration

2.1.1. Build

2.1.2. Deploy in test env

2.1.3. Tests

2.1.4. Package

2.2. Delivery

2.2.1. Release

2.2.1.1. Content

2.2.2. Product Backlog Items Delivery Workflow States

2.2.2.1. Ready for Deliver

2.2.2.2. To test in Qualification

2.2.2.3. Ready for Production

2.2.2.4. In Production

2.2.3. Versioning

2.2.3.1. Generated Build Number

2.3. Requirements - Product Backlog

2.3.1. PB Items

2.3.1.1. Defect

2.3.1.1.1. Subtyping

2.3.1.1.2. No business value

2.3.1.1.3. In Production or during Release process, not in Dev !

2.3.1.2. User Story

2.3.1.2.1. Business Value

2.3.1.2.2. Convention : "As [User] I can [do something] in order to [reach a goal] in a [user context]"

2.3.2. Epic

2.3.2.1. To be splitted in PB Items

2.3.2.2. Cannot be produced nor released

2.3.3. Product Documentation when Done

2.3.3.1. Obsolescence

2.3.3.1.1. Obsolete Workflow State

2.3.3.1.2. Replace/Replaced by link

2.3.3.2. Parent/child hierarchy

2.3.3.3. Theme

2.3.4. Story Points

2.3.5. Definition of Done

2.3.5.1. Items Workflow States

2.3.5.1.1. New

2.3.5.1.2. In progress

2.3.5.1.3. Resolved

2.3.5.1.4. Rejected

2.4. Testing

2.4.1. TDD

2.4.2. Acceptance TDD

2.4.2.1. Test Cases

2.4.2.2. Acceptance criteria

2.4.3. Tests Automation

3. ALM : from Application birth to its death, why ?

3.1. ALM phases/activities

3.1.1. Project from scratch

3.1.2. Evolutionary Project

3.1.3. Support

3.1.4. Maintenance

3.2. Dedicated team to application Vs dedicated to project

3.2.1. Collective code ownership

3.2.2. Application service homogeneity

3.2.3. Activities diversity/motivation

3.3. Processes Integration

3.3.1. Including Transverse ones

3.3.1.1. Accountability

3.3.1.2. Timesheet

3.3.2. CMMI Dev areas

3.3.2.1. Project Management

3.3.2.2. Engineering

3.3.2.3. Support

4. Example with TFS 2010

4.1. Integrated tool...

4.1.1. Source Control

4.1.1.1. Changesets linked with Work Items

4.1.1.2. Check-in policies

4.1.2. Team Build

4.1.2.1. MSBuild

4.1.2.2. Work Items links

4.1.3. Work Items

4.1.3.1. Workflow

4.1.3.2. Fields

4.1.3.3. Links

4.1.3.4. Hierarchy

4.1.4. Reporting

4.1.4.1. Datawarehouse SQL Server

4.1.4.2. Cube SS Analysis Services

4.1.4.3. Reports SS Reporting Services

4.1.5. SharePoint Portal

4.1.6. TFS Web Access

4.2. ...easily customizable...

4.2.1. Process Templates for packaging

4.2.2. Work Item Type Definition (XML)

4.2.3. Datawarehouse extensions (SQL views...)

4.2.4. Cube extensions (dimension, measures, calculations...)

4.2.5. Custom Reports SSRS

4.2.6. Agility through easy incremental deployment for all components

4.2.7. ..."at worst" TFS API .NET

4.3. ...even if not the best for each function...

4.3.1. Source Control with Git

4.3.2. Continuous Integration with Hudson

4.4. ...with some external tools

4.4.1. Sonar with plugins

5. Support

5.1. Configuration Management

5.1.1. Documents in SharePoint Portal

5.1.2. Wiki in SharePoint Portal

5.1.3. Source Control in TFS

5.1.4. Change request tracking with Work Items

5.2. Measurement and Analysis

5.2.1. Velocity

5.2.1.1. Relative to Available Time

5.2.1.2. Production velocity

5.2.1.3. Global velocity

5.2.2. Definition of Done

5.2.3. Story Points

5.2.4. Estimated/Completed/Remaining Work

5.3. Process and Product Quality Assurance

5.3.1. Process Control

5.3.1.1. Process Control Requests

5.3.1.2. Work Items Type Integrity

5.3.2. Product Quality

5.3.2.1. Code Metrics with Sonar

5.3.2.2. Engineering practices