Working groups (private/ public)
breaking the silos
Knowledge sharing
Knowledge is lost when delegates leave
Allow private space for experts
Bridge in Chad
Brochure site for the project
Show case progress and success
Connected to OpSys system to get data (region, number, funds)
By default an IT project will fail
It's published but doesn't answer all definition of success items
Defintion of succeess
- On Time
- On Budget
- Users Are Happy
Setting Expectations // Common language
אסופה של מתודות ותהליכי עבודה. בקיצור, תקשורת ותיאום ציפיות
Discovery phase
Project is sum of all its tasks
- Index based live stock insurance
- Predict draughts by infra red pictures from satelites
- Get Data from US site
- Process, send to MatLab, get data, push to Site
Development - It's easier than you think
unless when it isn't
.initiative {
.cohorts {
.col-cohort-groups {
padding-right: 15px;
margin-bottom: 20px;
}
.cohort-group.active:after {
content: none;
}
}
}
Work session, Time tracking, Payment
, and Github Issue bundles are pointing at a Project,
which in turn points to an Account bundle. Github Issue
can also reference itself.
Every feature or bug has a price tag
And you don't have to buy them all