Introduction to Timesheets and Statusing; New and Updated Features; Demo

1. Statusing and Timesheets in Project
Online and Project Server 2013
HTTP://WWW.HENHAPL.NET
Barbara Henhapl

3. About me
• Consulting for Project and Project Server, located in Vienna,
Austria
• Working with Project Server since Project Central (1999)
• MVP since 4 years
• Services:
• Consulting
• Implementation
• Trainings

4. Agenda
• Statusing – different methods
• %Complete
• Actual and Remaining Work
• Actual Work by Time
• Timesheets
• Single Entry Mode – Combining Statusing and Timesheets
• Task Field on Tasks/Timesheet page
Note: For Statusing and Timesheets, there is no difference between
Project Online and Project Server 2013. Therefore, demo will be on
Project Online only

5. % Complete
• Project Team Members update % Complete
• In addition, they can (should) update
• Remaining Work
• Actual Start
When additional information is not updated, project manager will
not be aware of any delays.

6. % Complete

7. % COMPLETE

8. Actual and Remaining Work
• Project Team Members enter Actual and Remaining Work
• In addition, they can (should) update
• Actual Start
When additional information is not updated, project manager will
not be aware of any delays.

9. Actual and Remaining Work

10. ACTUAL AND REMAINING WORK

11. Specify Hours
• Project Team Members enter hours per period (day/week)
• Advantage: Project manager has exact overview on status
• “Disadvantage”: Project manager has to adopt his planning to
reality

12. Specify Hours

13. SPECIFY HOURS

14. Only allow task updates via Tasks and
Timesheets
• When only allow task updates via Tasks and Timesheets, Project
manager will be prevented from overwriting status

15. ONLY ALLOW TASK UPDATES VIA TASKS AND TIMESHEETS

16. Timesheets
• Timesheets are sent to Timesheet Manager
• By default, there is no connection to Status Update on projects
• When timesheet is created after Status Update on Tasks page,
actual work is prepopulated
• When using timesheets, all information is stored at it is at this
moment. E.g. if a task name is changed later on, name of task at
time of creation is still saved in timesheet

17. Timesheets

18. TIMESHEETS

19. Single Entry Mode
• Single Entry Mode (SEM) does connect timesheet data with task
data
• Advantage: Within a matrix organization, you have consistent data
• Single point of entry is Timesheet page
• When sending timesheet to Timesheet Manager, status update is
sent to project manager at the same time
• Tipp: Hide Tasks pages
• See http://technet.microsoft.com/en-us/library/hh694531.aspx,
applicable for Project Server 2013 and Project Online

20. SINGLE ENTRY MODE

21. Status Approval
• Preview
• Try to avoid to “reject”. Instead, ask team member to correct their
update
• Publish required after accepting
• Rules
• Auto-Run
• Auto-Publish

22. STATUS APPROVAL

23. Task Field on Tasks/Timesheet page
• A task field can be designed to be displayed on Tasks resp.
Timesheet page
• User may be allowed to change value
• Note: Changes by users are stored on assignment level

24. TASK FIELD ON TASKS/TIMESHEET PAGE

25. questions?
HTTP://PROJECTBLOG.AT,
HTTP://WWW.HENHAPL.NET

26. thank you.
SHAREPOINT AND PROJECT CONFERENCE ADRIATICS
ZAGREB, 10/15/2014 - 10/16/2014