Project task scheduling

1. Assignment1
Mohsen Ansari
Mar 31, 2015
Department of Computer Science

2. Outline
 Outline
— First paper
 Introduction
 Analytical method
 Pros n Cons
— Second paper
 Introduction
 Analytical method
 Pros n Cons
— Comparison between the two papers
2

3. Outline
 Outline
— First paper
 Introduction
 Analytical method
 Pros n Cons
— Second paper
 Introduction
 Analytical method
 Pros n Cons
— Comparison between the two papers

4. Introduction
 Assigning Tasks in a 24-Hour Software Development Model
—Global distributed development teams
—Allocate tasks to different resources
—Minimize overall project development time
http://thumbs.dreamstime.com/z/international-time-zones-clocks-around-world-global-
travel-many-to-illustrate-changes-hours-32194754.jpg

5. Outline
 Outline
— First paper
 Introduction
 Analytical method
 Pros n Cons
— Second paper
 Introduction
 Analytical method
 Pros n Cons
— Comparison between the two papers

6. Analytical method
 Model tasks to graph
 Resource table
 Ready queue
 Choose between most weighted node without skill requirement and most weighted node that selected resource can
do
 Reset available resources and assigned tasks after every time zone set change

7. Outline
 Outline
— First paper
 Introduction
 Analytical method
 Pros n Cons
— Second paper
 Introduction
 Analytical method
 Pros n Cons
— Comparison between the two papers

8. Pros n Cons
 Pros
—It is simple and
applicable
—It is tested on both
real data and
synthesized data
 Cons
— Task assignments are certain
and don’t have any
alternatives
— The use of different time
zones is not well explained
— Algorithm is heuristic and
doesn’t have proof of being
optimum
— Available resources don’t
support overlapping
— Results are not compared
with other multi site task
scheduling methods

9. Outline
 Outline
— First paper
 Introduction
 Analytical method
 Pros n Cons
— Second paper
 Introduction
 Analytical method
 Pros n Cons
— Comparison between the two papers

10. Second paper
 Using Process Simulation to Compare Scheduling Strategies
for Software Projects
—Simulation model for analyzing the effects of a given task
scheduling to progress and completion time of a software
project
—A manager can compare different strategies and choose
the best that fits his/her needs

11. Outline
 Outline
— First paper
 Introduction
 Analytical method
 Pros n Cons
— Second paper
 Introduction
 Analytical method
 Pros n Cons
— Comparison between the two papers

12. Analytical method
 Inputs:
— Base probabilities
— Rework probabilities
— Dependency degrees between components
— Scheduling strategy (list policy)
 Process:
— Scheduling(changes) goes through different phases
— Each phase contains a certain amount of time slots
— State of a project changes at the end of each phase
 Progress vector
 Rework vector
 Countdown to the deadline
 Output:
— Table containing the completion time, number of tasks with success probability of 75% or
more, number of tasks with success probability of 90% or more

13. Outline
 Outline
— First paper
 Introduction
 Analytical method
 Pros n Cons
— Second paper
 Introduction
 Analytical method
 Pros n Cons
— Comparison between the two papers

14. Pros n Cons
 Pros
—It is possible to
analyzes different
strategies
—It is applicable at any
time during the
project
—It is applicable to real
problems
 Cons
— It is only tested on
simulated data
— Not enough details are
provided for method that it
uses
— It is only tested on list policy
and it claims it supports
other dynamic policies
— For achieving the best policy
it is needed to test all the
possible combinations

15. Outline
 Outline
— First paper
 Introduction
 Analytical method
 Pros n Cons
— Second paper
 Introduction
 Analytical method
 Pros n Cons
— Comparison between the two papers

16. Comparison
 First paper generates a policy while the second one gets a
policy as input
 Results of the first paper are certain while the results of
second one are probabilistic
 First paper considers the availability of resources and
overlapping requirements while the second one doesn’t
 Second paper gives more information and insight of impacts
of a scheduling rule

17. Service release planning optimization
 References
— [1] Padberg, Frank. "Using process simulation to compare scheduling strategies for
software projects." Software Engineering Conference, 2002. Ninth Asia-Pacific. IEEE, 2002.
— [2] Jalote, Pankaj, and Gourav Jain. "Assigning tasks in a 24-h software development
model." Journal of Systems and Software 79.7 (2006): 904-911.
1
7

18. Q&A
Thank you (^.^)
Any Questions?