2011 July August
From UG
(Difference between revisions)
(→Aug 15) |
(→Dev Sprint Manager and Support Manager role) |
||
| Line 235: | Line 235: | ||
''Currently in this role: Tira'' | ''Currently in this role: Tira'' | ||
| - | Dev Sprint Management | + | '''Dev Sprint Management:''' |
* Before Sprint starts: | * Before Sprint starts: | ||
| Line 247: | Line 247: | ||
** email this project plan to everyone | ** email this project plan to everyone | ||
| + | * During the Sprint: | ||
| + | ** once a week look at tasks scheduled to be completed that week (in mantis sort by week# and see if there any tasks tagged for this week and still in Dev). If there are ask developer/BA why, what is the new estimate. Escalate issue to Dev Manager as required. | ||
| + | ** (optional but useful) have weekly status update meeting with all developers/QAs/BAs | ||
| + | * At the end of the Sprint: | ||
| + | ** | ||
==== Dev Manager and Technical Architect role ==== | ==== Dev Manager and Technical Architect role ==== | ||
Revision as of 16:11, 16 August 2011
Contents |
Sprint Info
- Start: May 30 Mon
- Staging: July 4 Mon
- Prod: July 7 Thu
- Working Days: 23
- Holidays: none
- Dev: http://ct.jaguarfreight.com/mantis/view.php?id=2995
- BA: http://ct.jaguarfreight.com/mantis/view.php?id=3068
- Sprint plan: Plan for July August Sprint
- Rel Notes: Release Notes for 2011 July August Sprint
Daily Log
PM & Estim week schedule and project reviews with Sprint manager
- Mon (Jul 4) - preliminary new Sprint plan is to be announced (Alex)
- Tue - Smartphone App (Kostya)
- Wed
- Int Portal (Sasha);
- EDI with Trenset (Misha)
- Th - Rates DB (AK/Misha)
- Fri - Dash/DashReps framework&reports (AK)
- Mon & Tue (Jul 11, 12)
- follow up meetings for all key projects discussed last week - review of Dev Methodology, mantis structure, fields, roles and responsibilities, etc - New Sprint plan is to be confirmed
DT WUp - Dev team weekly updates meeting
- When: Thursdays, 7-9 am
- Who: all devs, QAs, Sup eng
- Why:
- individual updates from developers/QA/support:
- explain tasks assigned
- what work has been completed over last week
- on schedule? behind schedule? why? how to improve? how to learn from this?
- suggestions from everyone
- updates/conclusions from Lead PM
- old/new biz proc review\
- systems review
- updates from upper managers
- individual updates from developers/QA/support:
Org chart
Roles and relationships
New Mantis
Folders
result
| Name | Descr |
| * Archived / Released | All tasks that have been released, completed, discontinued, etc |
| * CT2 map | All CT2 components, subcomponents, etc (a.k.a. “parents”) |
| * Watchlists / Files / Misc | |
| 0. Support | Support related tasks |
| 1. Backlog | Dev backlog (pre-BA and tasks on hold) |
| 2. BA Sprint | tasks in current BA sprint |
| 3. Dev Est | tasks passed BA phase and in Estimation phase by development |
| 4. Dev Sprint | tasks in current Dev sprint |
| 5. WU Backlog | Wiki update backlog (tasks released but not wiki updated) |
Fields
| Name | Meaning | Type | Possible Values |
| %UAT | to be discontinued? | Numeric | |
| %WU | to be discontinued? | Numeric | |
| .amh | total num of dev man hours spent | String | |
| .emh | estimated man hours | Float | |
| .emhR | estimated man hours with Risk | Float | |
| .rmhR | remaining man hours (with Risk) | Float | |
| b? | bug? | Enumeration | Y |
| comp | CT2 component | Enumeration | AccCore|AccMisc|AccReps|-|OpsCore|OpsMisc|OpsRep|OpsPdf|-|Misc/Sys|JagIT|-|Client|ClientReps| |
| p.BA | Business Analyst | Enumeration | Denise|Tracie|Alex|Tira |
| p.Dev | Developer | Enumeration | Kostya|Sasha|Koltsov|Mihail|Vlad|Andrei|Roma|Alex|Tira |
| p.MO | Module Owner | Enumeration | Simon|Marc|Karen|Alex|Chikei|All |
| p.SQA | Systems and Quality Analyst | Enumeration | AG|Roma |
| phase | Dev phase | Enumeration | Dev|QA|UAT|WU |
| QApf | passed QA? | Enumeration | pass|fail |
| Rel# | Release number (discontinue?) | Enumeration | |
| Spec updated | wiki spec updated after implementation? | Enumeration | Yes|N/A |
| Spr# | Sprint number | Enumeration | jan7-feb3|April|JA.dev|JA.ba|AS.dev|AS.ba |
| T | Priority | Enumeration | p0|p1|p2|p3|p4|p5|p6|p7|p8|p9 |
Aug 4
Todos Roma:
- For Pdfs:
- move all wikis from "Ops Pdfs Coommon" to "OpsPdfsMisc"; kill Common
- move 1997 1686 1698 1755 1680 1666 into 664
For OpsReps:
- move 1585 2036 into 1600
Todos AG:
- create mantis and wiki struct for OpsCore, OpsMisc, Client and call(present) BA/SQA team for review
Todos Alex:
- create mantis and wiki struct for JagIT, MiscSys and call(present) BA/SQA team for review
Aug 5 Fri
Roma todos:
- when have time review all bugs in DevEst (count: 30). Suggest a list for next Spr.
Aug 6
Clients E0:
Cosmetech Mably Europe Cosmetech Mably Int'l Cosmetech Mably Int'l (HK) Ltd
Coty Australia Coty Espana COTY EUROPE Coty Geneva S.A Div. CP Trex COTY GERMANY COTY ITALY Coty Prestige Japan K.K. Coty Prestige Southeast Asia (HK) Ltd Coty Prestige Southeast Asia Pte. Ltd. Coty Sanford Coty Sanford Vendors Coty Services and Logistics Coty Shanghai COTY SPAIN Coty UK
Bill To:
COSMETECH MABLY EUROPE - GENNEVILLIERS COSMETECH MABLY INTL (HK) LTD - CENTRAL
Coty US LLC - Sanford COTY SERVICES AND LOGISTICS GMBH - MAINZ COTY PRESTIGE SOUTHEAST ASIA (HK) LTD - Wanchai COTY PRESTIGE SHANGHAI (HK) LTD - NT COTY MANUFACTURING UK LTD - ASHFORD
Users:
10 users, all have email like @cotyinc.com
Aug 15
Columns for "View Issues" page in "3. Dev Sprint" folder:
Status ph s# T m MO BA QA Dv .e .eR .rR 1 2 3 4 b <checkbox> <edit pen> ID comp Summary
Aug 16
BA Sprint Manager and Solutions Architect role
Currently in this role: Alex
Dev Sprint Manager and Support Manager role
Currently in this role: Tira
Dev Sprint Management:
- Before Sprint starts:
- request wish list from BAs for next Spr
- identify tasks that will roll over from current sprint
- calculate emh per developer and make sure it is reasonable
- if space permits add more tasks from "Dev Backlog"
- send this list to BAs/MOs for review
- schedule CT2 Board and confirm final version there
- get together with BAs and map tasks into weeks (use 1,2,3,4 mantis fields to indicate num of week when task will be completed)
- email this project plan to everyone
- During the Sprint:
- once a week look at tasks scheduled to be completed that week (in mantis sort by week# and see if there any tasks tagged for this week and still in Dev). If there are ask developer/BA why, what is the new estimate. Escalate issue to Dev Manager as required.
- (optional but useful) have weekly status update meeting with all developers/QAs/BAs
- At the end of the Sprint:
Dev Manager and Technical Architect role
Dev Sprint Manager and Support Manager role
Currently in this role: Kostya
