JD Meier

High Performance & Innovation Coach

by

Profile of a hispanic freelancer wearing glasses and reading the coding software on the computer. Focused programmer checking the app code

“I am not here to speak the Truth. I am here just to give you a method to perceive it.” ― Jaggi Vasudev, Of Mystics & Mistakes

I’m a fan of simple maps to help drill in. After all, it’s hard to explore the concepts if you don’t know they exist, or you don’t know what they are called.

Below is a work in progress.  I’m making a quick, simple map of the key activities from some software project-relevant processes.

I’m sure I’m missing key practices and some of the names have changed. 

So I’m sharing it, so that folks can help share what they know, to get to a map that includes the right top level names of key practices.

Process Practices
Kanban
  • Limit WIP (Work in Progress)
  • Measure the Lead Time
  • Visualize the workflow
Scrum
  • Burndown Chart
  • Daily Scrum
  • Definition of Done
  • Estimation
  • Impediment Backlog
  • Product Backlog
  • Product Owner
  • Retrospective
  • Scrum Master
  • Scrum Team
  • Sprint
  • Sprint Backlog
  • Sprint Demo
  • Sprint Planning Meeting
  • Velocity
XP
  • Coding Standard
  • Collective Code Ownership
  • Continuous Integration
  • On-Site Customer
  • Pair Programming
  • Planning Game
  • Refactoring
  • Simple Design
  • Small Releases
  • Sustainable Pace
  • System Metaphor
  • Test-Driven Development

RUP at a Glance

For comparison and fun, here is a balcony view of RUP.

Process Practices
RUP

Activities

  • Analyze Runtime Behavior (Implementer)
  • Architectural Analysis (Architect)
  • Assess viability of Architectural Proof-of-Concept (Architect)
  • Capsule Design (Capsule Designer)
  • Class Design (Designer)
  • Construct Architectural Proof-of-Concept (Architect)
  • Database Design (Database Designer)
  • Describe Distribution (Architect)
  • Describe the Run-time Architecture (Architect)
  • Design Testability (Designer)
  • Design the User-Interface (User-Interface Designer)
  • Develop Installation Artifacts (Implementer)
  • Elements (Designer)
  • Execute Developer Test (Implementer)
  • Identify Design Mechanisms (Architect)
  • Identify Design Elements (Architect)
  • Implement Design Elements (Implementer)
  • Implement Developer Test (Implementer)
  • Implement Testability Elements (Implementer)
  • Implementation Model (Software Architect)
  • Incorporate Existing Design Elements (Architect)
  • Integrate Subsystem (Integrator)
  • Integrate System (Integrator)
  • Plan Subsystem Integration (Integrator)
  • Plan System Integration (Integrator)
  • Prototype the User Interface (User-Interface Designer)
  • Review Code (Technical Reviewer)
  • Review the Architecture (Technical Reviewer)
  • Review the Design (Technical Reviewer)
  • Structure the (Software Architect)
  • Subsystem Design (Designer)
  • Use-Case Analysis (Designer)
  • Use-Case Design (Designer)

Artifacts

  • Analysis Class
  • Analysis Model
  • Architectural Proof-of-Concept
  • Build
  • Capsule
  • Data Model
  • Deployment Model
  • Design Class
  • Design Model
  • Design Package
  • Design Subsystem
  • Event
  • Implementation Element
  • Implementation Model
  • Implementation Subsystem
  • Integration Build Plan
  • Interface
  • Navigation Map
  • Protocol
  • Reference Architecture
  • Signal
  • Software Architecture Document
  • Test Design
  • Test Stub
  • Testability Class
  • Testability Element
  • Use-Case Realization
  • User-Interface Prototype

MSF Agile

For historical purposes and a trip down memory lane, here is an old version of the MSF Agile methodology.

MSF Agile

Activities

  • Build a Product
  • Capture Project Vision
  • Close a Bug
  • Create a Quality of Service Requirement
  • Create a Scenario
  • Create a Solution Architecture
  • Fix a Bug
  • Guide Iteration
  • Guide Project
  • Implement a Development Task
  • Plan an Iteration
  • Test a Quality of Service Requirement
  • Test a Scenario

Artifacts (Work Products)

  • Architectural Prototypes
  • Bug Reports
  • Change Sets
  • Check In Notes
  • Classes
  • Development Tasks
  • Interface Models
  • Personas
  • Scenarios
  • Storyboards
  • System Architecture
  • Test Plan (see Context-Driven Testing)
  • Test Cases
  • Unit Tests
  • Vision Statement

You Might Also Like

10 Ways to Make Agile Design More Effective
40 Hour Work Week
Don’t Let the Big Get in the Way of the Small
Don’t Push Agile, Pull It
Extreme Programming at a Glance
How To Drive Digital Transformation the Agile Way
Kanban for High-Performance Teams
Scrum at a Glance
The 4 Circles of Extreme Programming
Waterfall to Agile
What is Agile?

Category:

About JD Meier

Reader Interactions

Leave a Reply

Your email address will not be published.