meet our characters...

Patty, the PM

wants to keep her project on track, on scope, on budget

Derek, the Developer

wants to develop, with as few interruptions as possible

Trevor, the Tester

wants to make sure everything is working fine

Barbara, the BSA

wants to make sure her dear requirements get implemented

how do we address those needs?

Enter ALM

current state

• Manual process

  • Labor intensive
  • Ad-hoc and misaligned
  • Fail-prone and vulnerable

• Lots of red tape, difficulty in procuring access/tools

goals

• automation
  • builds, tests, metrics, deployments
• streamlined process/tools
  • easy setup, easy reviews
• easy to reproduce prod-like environments
  • works on my machine

the tools

ALM diagram here

Jira: planning & tracking

• Barbara: I want to add and track my requirements
• Derek: I want to report what I'm doing and my progress
• Patty: I want to track it all :)

●

Box: document sharing

• Barbara: I want to share a detailed scope doc
• Trevor: I want easy access to relevant info

●

Zephyr (& Jira): testing

• Trevor: I want to plan and run my tests
• Patty: I want to know about testing blockers

●

Stash

• Derek: I want to share code with my team members
• Derek: I want an easy way to review code

●

Bamboo

• Derek: Is build alright?
• Derek: I want deploys to be automated

●

All team members

"Eeek, there's an ARB coming!"

●