
Beginning Application Lifecycle Management
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
More details
Other editions
Additional editions

Person
Content
- Intro
- Contents at a Glance
- Contents
- About the Author
- About the Technical Reviewers
- Acknowledgments
- Chapter 1: Why Application Lifecycle Management Matters
- Responding to Change
- Understanding the Cornerstones of Business
- Processes
- Business Rules
- Information
- Understanding the Need for Business Software
- Today's Business Environment and the Problems We Face
- Project Health Today: Three Criteria for Success
- Project Delivered on Time
- Project Delivered on Budget
- Project Goal Fulfilled
- Factors Influencing Projects and Their Success
- The Gap between Business and IT
- The Development Process-Or the Lack of One
- Geographic Spread
- Synchronization of Tools
- Resource Management
- Project Size
- Project Success: What Does the Research Say?
- The Standish Report
- Challenging the Report
- Conclusions
- Summary
- Chapter 2: Introduction to Application Lifecycle Management
- Aspects of the ALM Process
- Four Ways of Looking at ALM
- The SDLC View
- The Service Management or Operations View
- The Application Portfolio Management View
- The Unified View
- Three Pillars of Traditional Application Lifecycle Management
- Traceability
- Automation of High-Level Processes
- Visibility into the Progress of Development Efforts
- A Brief History of ALM Tools and Concepts
- Application Lifecycle Management 1.0
- Application Lifecycle Management 2.0
- Application Lifecycle Management 2.0+
- DevOps
- ALM and PPM
- Summary
- Chapter 3: Development Processes and Frameworks
- The Waterfall Model
- Spiral Model
- Rational Unified Process (RUP)
- The Principles of RUP
- The RUP Lifecycle
- Inception Phase
- Elaboration Phase
- Construction Phase
- Transition Phase
- Disciplines in RUP
- Business Modeling Discipline
- Requirements Discipline
- Analysis and Design Discipline
- Implementation Discipline
- Test Discipline
- Deployment Discipline
- Configuration and Change-Management Discipline
- Project-Management Discipline
- Environment Discipline
- Work Products, Roles, and Tasks in RUP
- RUP Benefits
- Manifesto for Agile Software Development
- Extreme Programming (XP)
- Scrum
- Empirical Process Control
- Complexity in Projects
- What Scrum Is
- Roles in Scrum
- The Product Owner
- The Team
- The Scrum Master
- The Scrum Process
- The Kanban Method
- Start With What You Do Now
- Agree to Pursue Incremental, Evolutionary Change
- Respect the Current Process, Roles, Responsibilities, and Titles
- The Five Core Properties
- Visualize the Workflow
- Limit Work in Process (WIP)
- Manage Flow
- Make Process Policies Explicit
- Improve Collaboratively (Using Models and the Scientific Method)
- Common Models Used to Understand Work in Kanban
- Choosing the Process
- Summary
- Chapter 4: Introduction to Scrum and Agile Concepts
- The Scrum Process
- Roles in Scrum
- Product Owner
- Scrum Master
- The Development Team
- Definition of Done
- Agile Requirements and Estimation
- Requirements
- Estimation
- Backlog
- During the Sprint
- Daily Stand-Up
- Sprint Review
- Sprint Retrospective
- How Agile Maps to ALM
- Agile Captures Task-Based Work
- Increased Frequency of Inspection
- Many Tools Collect Much Information
- Test Artifacts Are Important
- Agile Teams Plan Frequently
- Summary
- Chapter 5: ALM Assessments
- Microsoft Application Platform Optimization (APO) Model
- Infrastructure Optimization Model
- Business Productivity Infrastructure Model
- APO Maturity Levels
- Basic
- Standardized
- Rationalized (formerly Advanced)
- Dynamic
- APO Capabilities
- User Experience
- Business Intelligence
- SOA and Business Process
- Data Management
- Development
- Application Platform Capability Assessment
- ALM Rangers' Assessment Guide
- Architecture and Design
- Requirement Engineering and UX
- Software Configuration Management
- Governance
- Deployment and Operations
- Testing and Quality Assurance
- Project Planning and Management
- Development
- Starting the Microsoft Web Assessment
- Sample Questions
- Example 1: Assessing Requirements Handling
- Example 2: Assessing Code Analysis
- Other examples
- Viewing the Results
- How to Use the Results
- Using the Application Platform Capability Assessment
- Why Do an Assessment?
- Summary
- Chapter 6: Visibility and Traceability
- The Importance of Trust and Visibility
- What Is Visibility?
- Why Do You Need Visibility?
- An Agile Approach to Visibility
- Continuous Integration
- Why Should You Implement Continuous Integration?
- Components of Continuous Integration
- Build Automation
- Database Integration
- Deployment
- Testing
- Inspection
- Feedback
- ALM 2.0+ and Visibility
- Automating Visibility
- Traceability
- Software Traceability
- ALM 2.0+ Supports Software Traceability
- Why Traceability is Important
- Agile Frameworks and Traceability
- Automating Traceability
- Summary
- Chapter 7: Automation of Processes
- What Is Process Automation ?
- Project-Management Process
- Test Process
- Build and Release Process
- Continuous Delivery: A Process-Automation Example
- The "Null" Release Cycle
- Release Management
- Things to Consider Before Automating Processes
- Benefiting from an ALM Solution
- Using Different Tool Vendors
- Know the Weaknesses of Your ALM Tool
- ALM and DevOps Is Still a Struggle
- Summary
- Chapter 8: Work Planning
- Task Management
- Tasks or Work Items
- Planning Work Using Work Items
- Reporting that Resolves Estimates and Actuals
- ALM 2.0+ Enables Good Planning Functions
- Support for Historical Data
- Summary
- Chapter 9: Collaboration
- DevOps
- DevOps Overview
- How Well Has Your Organization Adopted DevOps?
- How Can You Start Adopting DevOps?
- Engaging the Business Side
- Better Collaboration between Development and Business
- Requirements Gathering
- Storyboarding
- Continuous Feedback
- Sharing Information
- Maintaining a Shared Backlog
- Sharing Documents and Information
- Summary
- Chapter 10: Metrics in ALM
- Project-Management Metrics
- Agile Metrics
- Metrics for Architecture, Analysis and Design
- Metrics for Developer Practices
- Code Coverage
- Code Metrics
- Compiler Warnings
- Code-Analysis Warnings
- Metrics for Software Testing
- Example Reports
- Bug Status Report
- Reactivations Report
- Bug Trend Report
- Metrics for Release Management
- Sample Reports
- Summary
- Chapter 11: Introduction to ALM Platforms
- Atlassian
- IBM
- Microsoft
- CollabNet
- Summary
- Index
System requirements
File format: PDF
Copy protection: Watermark-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Use the free software Adobe Reader, Adobe Digital Editions, or any other PDF viewer of your choice (see eBook Help).
- Tablet/Smartphone (Android; iOS): Install the free app Adobe Digital Editions or another reading app for eBooks, e.g., PocketBook (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (only limited: Kindle).
The file format PDF always displays a book page identically on any hardware. This makes PDF suitable for complex layouts such as those used in textbooks and reference books (images, tables, columns, footnotes). Unfortunately, on the small screens of e-readers or smartphones, PDFs are rather annoying, requiring too much scrolling.
This eBook uses Watermark-DRM, a „soft” copy protection. This means that there are no technical restrictions to prevent illegal distribution. However, there is a personalised watermark embedded in the eBook that can be used to identify the purchaser of the eBook in the event of misuse and to provide evidence for legal purposes.
For more information, see our eBook Help page.