Project Planning & Managment Flashcards
PM software uses (11)
project personnel time and fees track time and fees to compare tract consultant costs schedule in office work invoices maintain project documentation track construction docs ie change orders maintain design and spec info team contacts track productivity compile individual jobs into financial management reports
team selection basis (6)
type and complexity size of project staff availability experience levels billing rates personalities
things included in work plan (7)
scope of services from agreement
breakdown of services into phases
dependencies
milestones
staff needed
allocation of time and fees to phases / tasks
what work will be done by consultants & cost
design office staff coordination (14)
communication clarify expectations reasonable responsibility based on skill level relationship sensitivity stay calm if ppl get angry resolve conflicts quickly provide growth opportunities give recognition evaluate performance often open communication among team model behavior include the client direct client interest where it can have greater impact encourage initiative
project notebook (8)
general references ie contacts contracts fees and schedules programming budget communications CA closeout / follow up
meeting tips
be respectful of consultants time establish times and stick to them conference call as option keep minutes organize an outline & alert ppl of it before meeting
meeting notes
minutes for meeting should be taken and distributed
use a template
blank sign in sheet to record attendees and their contact info
ubiased and to the point
serve as a formal record and may have legal implications later
typed immediately after meeting
statement at end for others to reply with corrections if necessary - minimizes disagreements later
project perfection syndrome
pm must decide whether the additional time andmoney are justified to spend on making the project closer to perfect
usually a joint decision is made if it is a tough call
pm should make sure the project team understands how much time is budgeted for each task and which tasks must be completed to avoid over doing it
perfection curve is different for every office
bar / gantt chart
simple scheduling graph, common
shows tasks tat must be done inorder to complete the project - listed chronologically along vertical axis
horizontal axis shows time to accomplish task
arrows represent dependency
can be used for projects of any size
critical path method
float
used more often with construction projects
solid arrow = tasks
task connot begin until all arrows leading to it have been completed
number under arrow = time to complete in days
dependencies are shown as dashed lines(dummies)
heaviest arrow shows critical path
noncritical tasks may be flexible with time without affecting completion date
float is the max length a noncritical task can be delayed before it causes overall project delay
top down approach
estimates total fee needed to complete project by rule of thumb and historic data
includes direct labor indirect labor fees expenses and contingency
everything is subtracted from fee to determine what is left over for direct labor (total working fee)…then that number is divided into standard design phases (15,20,40,5,20)
percents will vary if there are add services like programming
total working fee is divided by average billing rate for ppl on project and that will leave you with the amount of hours everyone should be working on the project per week - if over 40 add people
monitoring a project
monitoring employees time sheets weekly a pm can compare the actual hours to the budget and fix if necessary
can be done using a pm chart
full wall schedule can be used as a hand drawn tool to schedule a project with the team
consultant coordination
pm is responsible for coordinating work of all consultants
consultants should be involved as early as possible for design input and avoiding misdirected design
pm informs consultants about code reqs
consultants are responsible for code compliance regarding their own areas of work & accuracy of their own drawings
arch is liable to owner for consultants work
code coordination
should begin during programming
code checklists are useful in coordinating
all info from sd should be verified in dd
design elements that have a great cost impact should be verified against code earlier rather than later
bottom up approach
breaking projects down into tasks and estimating how much time will be needed to complete each
fee is calculated by assigning specific staff with defined billing rate to each task
use top down and bottom up to compare
