Skip to content

Instantly share code, notes, and snippets.

@xpepper

xpepper/project.portfolio.tips.md

Last active April 25, 2019 17:31
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save xpepper/9f6a4e89ccb8d7822b3a13b53a53f6b2 to your computer and use it in GitHub Desktop.
Save xpepper/9f6a4e89ccb8d7822b3a13b53a53f6b2 to your computer and use it in GitHub Desktop.
Download ZIP
Project Portfolio Tips
Raw
project.portfolio.tips.md

Tip 1. Make your work visible.

Tip 2. Ask whether the work is still useful.

Tip 3. Flow the project work through stable teams.

If you have stable teams, they can adjust to whatever work you have for them. Even in many transitioning-to-agile organizations, managers find it difficult to think about stable teams. Managers---and team members---often ask, "What do we do if we need an expert for this part?"

Here's the quick answer:

  • Ask the expert to work with the team so the team can learn with the expert
  • Ask the team to work together so the team can learn without the expert
  • If you must use an expert, make sure the expert never works alone.

(from 3 Quick Project Portfolio Tips by Johanna Rothman, from https://madmimi.com/p/8e3ee7?fe=1&pact=213571-133941768-8729210744-a73d911cb2f5ade4eac27b9e35ca4a6b01d07ff2)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment