Difference between revisions of "Afternoon 2 report backs"
Jump to navigation
Jump to search
m (1 revision imported) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
* Good communication with founder, single point of contact | * Good communication with founder, single point of contact | ||
| − | * | + | * Aligning core competencies of provider and organization |
| − | * | + | * Contracts to reflect requirements |
Scope | Scope | ||
| Line 14: | Line 14: | ||
Cross departmental PM | Cross departmental PM | ||
| − | * Basic definition of PM should be expanded to include an informal toolkit, a better define vocabulary of all the soft tools that | + | * Basic definition of PM should be expanded to include an informal toolkit, a better define vocabulary of all the soft tools that PM's use to keep the project moving. Everything as real as email, to much softer teams as team building tools, to understand organizational culture, how to follow up with people, sharing ownership of the project, grounding the project in mission conversations, all these mechanisms should be written into the PM bible to give people a vocabulary. |
| − | User | + | User Testing |
* Simple plain language user stories beginning with "An user can". Write in plain language | * Simple plain language user stories beginning with "An user can". Write in plain language | ||
* Tools to see what people are doing online, you can test your users live. | * Tools to see what people are doing online, you can test your users live. | ||
* Low tech usability test, mock up web-pages and hand the printout to a user, circle or colour a button, get a reaction from the layout of the page. | * Low tech usability test, mock up web-pages and hand the printout to a user, circle or colour a button, get a reaction from the layout of the page. | ||
Latest revision as of 23:08, 14 January 2016
Report backs
Founder and consultant relationship management
- Good communication with founder, single point of contact
- Aligning core competencies of provider and organization
- Contracts to reflect requirements
Scope
- Methods you can use to write out your scope and requirements
- Ways to get there, user needs, getting people involved in creating requirements, allocate time to scope
Cross departmental PM
- Basic definition of PM should be expanded to include an informal toolkit, a better define vocabulary of all the soft tools that PM's use to keep the project moving. Everything as real as email, to much softer teams as team building tools, to understand organizational culture, how to follow up with people, sharing ownership of the project, grounding the project in mission conversations, all these mechanisms should be written into the PM bible to give people a vocabulary.
User Testing
- Simple plain language user stories beginning with "An user can". Write in plain language
- Tools to see what people are doing online, you can test your users live.
- Low tech usability test, mock up web-pages and hand the printout to a user, circle or colour a button, get a reaction from the layout of the page.