Agile Development with ICONIX Process: People, Process, and Pragmatism - page 1
- 1
- 2
- Agile Development with ICONIX ProcessPeople, Process, and Pragmatism
- Agile Development with ICONIX ProcessPeople, Process, and Pragmatism
- Table of Contents
- IntroductionRigor Without the Mortis
- Recurring Themes
- So, Lets Get Started
- Part 1: ICONIX and Agility
- Chapter 1: What Is Agility? (And Why Does It Matter?)
- What Software Agility Isnt
- The Goals of Agility
- Why Is Agility Important?
- What Makes a Project Agile?
- Challenges of Being Agile
- Agile Methodologies
- Agile Fact or Fiction: What Does Being Agile Mean?
- Summary
- Top 10 Practices and Values That Make a Project Agile
- Chapter 2: Characteristics of a Good Software Process
- Whats in a Software Development Process?
- What Makes a Good Agile Logical Process?
- Human Factors
- Agile Fact or Fiction: Team Structure and Human Factors
- Summary
- Chapter 3: ICONIX ProcessA Core UML Subset
- A Brief History of ICONIX Process
- What Can ICONIX Process Do for My Project?
- ICONIX Process in Theory (aka Disambiguation and Prefactoring)
- ICONIX Process in a Nutshell
- More About Disambiguation
- More About Prefactoring and Model Refactoring
- Key Points to Remember
- Summary
- Chapter 4: A Core Subset of Agile Practices
- Why Define a Core Subset of Agile Practices?
- Agile ICONIX: The Core Subset of Agile Practices
- Refactoring the Agile Manifesto
- Agile Fact or Fiction (Continued)
- Summary
- Part 2: Agile ICONIX Process in PracticeThe Mapplet Project
- Chapter 5: Introducing the Mapplet Project
- So, Whats a Mapplet, Anyway?
- Mapplet Goals
- Mapplet Requirements
- Project Inception: A JumpStart Workshop in Action
- Mapplet Architecture
- Initial Use Case Modeling for the Mapplet
- First Release Plan
- More Information on ArcGIS As Used by the Mapplet
- Summary
- Chapter 6: Modeling the Mapplet (Release 1)
- Visual Acceptance Testing
- First Pass Modeling Efforts (and Some Typical Modeling Mistakes)
- Tightening Up the Model
- Lets Take a Look at Some Code
- Et Voila The First (Working Prototype) Release
- Summary
- Chapter 7: Synchronizing the Model and CodeOne Small Release at a Time
- Keeping It Agile
- Divergence of Code and Design over Time
- Design Review
- And Today s Lesson Is
- Summary
- Chapter 8: Mapplet Release 2
- How Persona Analysis Was Used to Drive the Requirements
- Planning the Second Release
- Analysis Review
- Designing Release 2
- Source Code: Refactoring Is Still Useful After Doing Use Case-Driven Modeling
- Screenshots of the Finished Product
- Agile Scorecard for the Mapplet Project
- Summary
- Part 3: Extensions to ICONIX Process
- Chapter 9: Agile Planning
- Agile Planning Terminology
- Agile Planning Building Blocks
- Agile Planning Phases
- Agile Planning Principles
- Summary
- Chapter 10: Persona Analysis
- Extending ICONIX Process with Persona Analysis
- 1
- 2
Similar products
Use Case Driven Object Modeling with UML : A Practical Approach (Addison-Wesley Object Technology Series)
User Stories Applied: For Agile Software Development
ICONIX Process Roadmaps: Step-by-step Guidance for SOA, Embedded, and Algorithm-intensive Systems
Design Driven Testing: Test Smarter, Not Harder