myIMD SAM Sprint 1

Get Started. It's Free
or sign up with your email address
Rocket clouds
myIMD SAM Sprint 1 by Mind Map: myIMD SAM Sprint 1

1. Open Issues

1.1. Blockers

1.1.1. .Net client <-> SAML

1.1.2. Correctly functioning test system

1.1.3. DProxy creating mail attr

1.2. Other

1.2.1. CAS complete code

1.2.1.1. deploy to prod

1.2.1.2. All english test (lang modules replaced)

1.2.2. accounts on prod to use to test

1.2.3. Siebel exception handling

1.2.4. Dev environment

1.2.5. Keep an eye out for CAS (LinkedIn) RC -> Full Rel

1.2.6. Fast track new techno replacing CAS?

1.2.7. Test procedure for 15th Oct

1.2.7.1. selenium in TeamCity

2. Past Issues

2.1. Edwin reserved Tues 15th Oct

3. Sprint goal

3.1. Alumni-network ready to rock

4. Team "Definition of Done" List

4.1. Done with a Story/Task

4.1.1. All code checked in

4.1.2. All regression tests passing

4.1.3. code reviewed by opposite pair (Richard/Niki)

4.2. Done with a Sprint

4.2.1. All story criteria plus

4.2.1.1. all p0 and p1 bugs resolved

4.2.1.2. CI server passing

4.2.1.3. All acceptance tests identified, written and passing

4.2.1.4. Architectural review performed by Philippe

4.2.1.5. All API changes/definitions are documented

4.3. Done with release to Staging

4.3.1. All sprint criteria plus

4.3.1.1. QA review performed

4.4. Done with release to Production

4.4.1. All staging criteria plus

4.4.1.1. UAT performed

5. Planning

5.1. Session 1

5.1.1. Admin

5.1.1.1. Block hours

5.1.1.1.1. Richard 100%

5.1.1.1.2. Petya 60%

5.1.1.1.3. Niki 50%

5.1.1.1.4. Philippe 30%

5.1.1.1.5. Atanas 15 days

5.1.1.2. Time for clearance meetings

5.1.1.2.1. 1 hr every Wednesday?

5.1.1.2.2. Goals:

5.1.1.3. Jira usage

5.1.2. Release planning

5.1.2.1. steps:

5.1.2.1.1. sketch a preliminary roadmap

5.1.2.1.2. add a degree of confidence

5.1.2.1.3. include dates and adjust as needed

5.1.2.1.4. update the plan every sprint

5.1.3. QA

5.1.3.1. Petya defines testing plan

5.1.3.1.1. how does it work for each platform

5.1.3.1.2. main web site will be visible

5.1.3.2. Petya works together with Atanas to decide what tests can be automated

5.1.3.3. goal: each automated test goes into continuous integration server (run with each check in)

5.1.4. Dependencies

5.1.4.1. interfaces to:

5.1.4.1.1. CRM (Siebel)

5.1.4.1.2. RMS

5.1.4.1.3. LDAP

5.1.4.1.4. Cold Fusion legacy

5.1.4.2. Sys admin + Siebel + iPad tasks

5.1.4.2.1. need to give them as much pre-warning as possible

5.1.4.3. future arch decision

5.1.4.3.1. to drop Siebel in favor of RMS

5.1.4.4. Architectural understanding

5.1.4.4.1. Philippe overview on whiteboard

5.1.5. Responsibilities

5.1.5.1. Quality first

5.1.5.1.1. dev should favor unit and functional tests (as a spec tool)

5.1.5.1.2. maintain the dev good practices

5.1.5.1.3. follow defect rating system?

5.1.5.2. Soft skills

5.1.5.2.1. favor close collaboration/communication with other members (team spirit)

5.1.5.2.2. raise the alarm if you are stuck and can't make progress (Stand-ups but judgement call on whether to wait)

5.1.5.3. Enjoyment and Challenge

5.1.5.3.1. Looking to engage and stimulate you

5.1.5.3.2. a cool project that is very important for IMD

5.1.6. Engineering practices

5.1.6.1. Continuous Integration and frequent check ins

5.1.6.2. Automated system and acceptance tests

5.1.6.3. Refactoring

5.1.6.4. possibilities

5.1.6.4.1. Pair Programming

5.1.6.4.2. TDD

5.2. Second session

5.2.1. plan for meeting

5.2.1.1. 1. level of understanding (1-5)

5.2.1.1.1. yesterday's meeting

5.2.1.1.2. project view

5.2.1.2. 2. yesterday's takeaway? and clarifications

5.2.1.3. 3. task creation for sprint

5.2.1.3.1. dev

5.2.1.3.2. QA

5.2.1.4. 4. estimate tasks in sprint

5.2.1.5. 5. conventions

5.2.1.6. 6. questions

5.2.1.6.1. technical needs?

5.2.1.6.2. pair programming between Niki and Richard?

5.2.1.6.3. yours ...

5.2.1.7. 7. to do

5.2.1.7.1. Philippe

5.2.1.7.2. Niki

5.2.1.7.3. Richard

5.2.1.7.4. Petya

5.2.1.7.5. Shane

5.2.2. TO DO

5.2.2.1. send me your block hours

5.2.2.2. architectural overview

5.2.2.2.1. interfaces to other (sub)systems

5.2.3. Conventions

5.2.3.1. if you break the Continuous Integration (CI) build, you fix it ASAP

5.2.3.1.1. Richard intro to/demo of team city

5.2.3.1.2. including

5.2.3.2. code review of every line (xml, unit tests included)

5.2.3.2.1. how will we do that?

5.2.3.2.2. Ideally to be done same day (stop laughing/crying :-) )

5.3. Follow-up

5.3.1. stand-up

5.3.1.1. < 1 min per question

5.3.1.1.1. What did I do yesterday?

5.3.1.1.2. What will I do today?

5.3.1.1.3. What blocking issues do I have?

5.3.1.1.4. What is your confidence, on a scale of one to ten, that the team will accomplish the goal of this sprint?

5.3.2. Still to talk about

5.3.2.1. Jira usage:

5.3.2.1.1. leaf tasks should be less than 2 days

5.3.2.1.2. estimate

5.3.2.1.3. amount of time spent

5.3.2.1.4. see burndown chart

5.3.2.2. time juggling

5.3.2.2.1. Richard away from Wed 9th and back Fri 25th

5.3.2.2.2. Niki can we steal more of your time to compensate?

5.3.2.3. Setting up a sandboxed test environment?

5.3.2.3.1. wait a few sprints to see destiny of

5.3.2.4. Set a weekly time for an architectural review by Philippe (if needed?)

5.3.2.4.1. no, use Q&A time for this

5.3.2.5. Define stylecop and resharper rules

5.3.2.5.1. agreement?

6. TO DO

6.1. Release Planning

6.1.1. Shane: we should do this on the week of 28th Oct

6.2. Knowledge base

6.2.1. Architectural model

6.2.1.1. what subsystems do we use?

6.2.1.1.1. current

6.2.1.1.2. future

6.2.1.2. what API calls are we making and vice-versa?

6.2.2. myIMD bible

6.2.2.1. A document describing how this service can be used by a service that is to be integrated into the myIMD space (e.g., new Alumni network), detailing the API, the architecture, the common usage scenarios (desktop, tablet and mobile), the common pitfalls, the known limitations, the style requirements, any maintenance requirements and tips, and references to information about all off-the-shelf (OTS) components used

6.3. Infrastructure

6.3.1. Set up Team City server

6.3.1.1. stylecop

6.3.2. Set up dev's machine

6.3.2.1. stylecop

6.3.2.2. trial NCrunch

6.3.2.3. Team City notifier?

6.4. Work

6.4.1. consider Def of Done

6.4.2. Petya

6.4.2.1. define block hours from when you are able to and send them to me

6.5. Shane

6.5.1. bring Iain into mockup review and propose to come to review

6.5.1.1. ensure Iain agrees with responsive html5 as way to go forward

6.5.2. set review and retro

6.5.3. document interactions with other subsystems

6.5.4. wireframe acc mgmt and present to persona owners

6.5.4.1. goal

6.5.4.1.1. IMD-388

6.5.4.2. define myIMD bus meetings

6.5.5. SQLI

6.5.5.1. ensure team devs meet with Aldo Ferrari early

6.5.5.1.1. bootstrap?

6.5.5.1.2. dive lib

6.5.5.2. test what they provide us before we integrate

6.5.6. CLN account registration

6.5.7. test accounts

6.5.7.1. test & prod

6.5.7.1.1. prod

6.5.7.1.2. test

6.5.8. LinkedIn: use std api; lawyer: Stefan Giellieron

6.5.9. tests

6.5.9.1. english only

6.5.9.2. error messages

6.5.9.2.1. failed login communicated

6.5.9.3. multi-browser

6.6. alumni-network rel

6.6.1. what is not working

6.6.2. CAS deploy to test

6.6.3. remove Remember me and other check-box if not working

6.6.4. fix CF on test

6.7. next steps

6.8. cold fusion dev: Robin in USA