Difference between revisions of "Project Management Therapy"
Jump to navigation
Jump to search
(Created page with "==Group needs== *mapping discussions of what clients ask for contracts *interval, client, project management support using client preferred medium: **trello, Asang, etc & keep...") |
Willowbl00 (talk | contribs) |
||
| Line 25: | Line 25: | ||
**online library of PDF resources | **online library of PDF resources | ||
**i.e. literacy rates of HS boys | **i.e. literacy rates of HS boys | ||
| − | ** | + | **contracts used pivitol trackers to write user stories |
**can write priorities | **can write priorities | ||
| − | **needs | + | **needs assessment became like requirements |
| − | **we | + | **we didn't know until we got to that feature |
**client through it was MVP and we didn't <br> | **client through it was MVP and we didn't <br> | ||
| Line 34: | Line 34: | ||
*we did a lot of deep dive workshop | *we did a lot of deep dive workshop | ||
Group ideas: | Group ideas: | ||
| − | *limit | + | *limit expectations |
*we'll slowly develop so we don't pin ourselves into quarters | *we'll slowly develop so we don't pin ourselves into quarters | ||
*start with how much $ do you have let's start there | *start with how much $ do you have let's start there | ||
| − | *don't rush information | + | *don't rush information architecture |
*we create wireframes on paper before anything to get clients | *we create wireframes on paper before anything to get clients | ||
*tell them we need to see what this takes | *tell them we need to see what this takes | ||
*let them know that your teams capacity can not grow | *let them know that your teams capacity can not grow | ||
| − | *we need documents for shared | + | *we need documents for shared understanding |
'''More group process/ideas''' | '''More group process/ideas''' | ||
| Line 61: | Line 61: | ||
*Invision-prototyping tool | *Invision-prototyping tool | ||
*keep agreements in a doc on the tool & track versions by date | *keep agreements in a doc on the tool & track versions by date | ||
| − | *Mantis- old | + | *Mantis- old ticket tracker |
*smart sheet: spreadsheets w/more | *smart sheet: spreadsheets w/more | ||
==TOOLS== | ==TOOLS== | ||
| − | *need | + | *need shared agreements of how to use it |
*actual document | *actual document | ||
*from mtg requests | *from mtg requests | ||
| + | |||
| + | [[Category: 2015]][[Category: Tools]][[Category: Product And Project Management]][[Category: Workflows]] | ||
Latest revision as of 21:43, 22 November 2016
Group needs
- mapping discussions of what clients ask for contracts
- interval, client, project management support using client preferred medium:
- trello, Asang, etc & keeping track --> workflow
- what tools do you use and why
- how to motivate people/ volunteers etc
- being a developer/designer/ hat changing
- how to say “no” and keeping scope-no to burn out
Tools
- basecamp (crossed out) – Design Action
Practices
- how to know your ideal workflow & whats happening
- where are problem points
- whats the vision
- for project management
- shared understanding of:
- roles
- timeline
- central data space
- what are you doing that working well
- whats not working?
- 1 group ex:
- online library of PDF resources
- i.e. literacy rates of HS boys
- contracts used pivitol trackers to write user stories
- can write priorities
- needs assessment became like requirements
- we didn't know until we got to that feature
- client through it was MVP and we didn't
Where was the problem
- we did a lot of deep dive workshop
Group ideas:
- limit expectations
- we'll slowly develop so we don't pin ourselves into quarters
- start with how much $ do you have let's start there
- don't rush information architecture
- we create wireframes on paper before anything to get clients
- tell them we need to see what this takes
- let them know that your teams capacity can not grow
- we need documents for shared understanding
More group process/ideas
- have client & develop reflect each others (ideally written) w/ priorities & feautures
- reverse roles
- “what do you think that I want you to do”
- have them repeat back
- “my understanding of what we agreed upon is”
Like contracting- need change order hen your wit snags -quickly
Documents & tools for shared understanding
- spreadsheets – need to version it
- basecamp
- we create excel w/ each line having est time range
- stories on board- good for features
- trello/libre board
- Asana
- Invision-prototyping tool
- keep agreements in a doc on the tool & track versions by date
- Mantis- old ticket tracker
- smart sheet: spreadsheets w/more
TOOLS
- need shared agreements of how to use it
- actual document
- from mtg requests