Team Kurtulmak
Purpose
Product Vision
All new employees have work stations and logins that are ready to go on the first day of work. (Sponsor/Vision Keeper: Dir HR and PO/HR Business Partner)
Team Mission
We build a solid enterprise solution for identity management, including: standardized access controls; centralized security of accounts; and a centralized, flexible reporting and certification process. We work with our HR business partners to identify consistent ID-M processes across all divisions. We provide automated account provisioning, which integrates smoothly with critical organizational systems.
Mission Tests
-
By end of this fiscal year, self-service ID management access expands to usage by 25% more employees and contractors.
-
By end of FY Q3, we have surveyed new employees about their experience related to parts of system deployed (for example, access to screens they need to do their work).
-
By end of FYQ2, we have gained working proficiency in the access control system we selected.
Alignment
Simple Rules
-
Hold to our quality standards—in every step of the process.
-
Advocate exploration—of tools, technologies, and processes—around identity management.
-
Identify and promote collaborative efforts within the team and elsewhere.
-
Honor our commitments and expectations.
Core Team
This development and production support mission brings together members of three former teams to create a centralized identity management team. (+ roles and expectations chart). We take time to understand how each of us will contribute and what each of us needs to do his/her best work.
| Expectations | Product Owner | DevTeam Member | Scrum master | Business Analyst |
|---|---|---|---|---|
| Define business needs | X | |||
| Long-term strategic planning | X | O | O | |
| Accept work as “done” at end of sprint | X | |||
| Attends daily standup and contributes | O | X | O | X |
| Provides feedback on impacts to schedule | O | X | X | X |
| Helps teammates as needed | X | X | X | X |
Working Agreements
We work together best when:
-
We define done for our stories as: code complete, unit tested, code deployed to stage, and functional testing complete.
-
All team members are available for meetings and communication during the core team hours of 9 a.m. to 4 p.m.
-
We hold daily standup meetings from 9:00 to 9:15 a.m.
-
We cast no silent vetoes; we speak up if we disagree.
-
We acknowledge and accept if we are an impediment for the team.
-
Product owner, business analyst, scrum master, and development team members all advocate for the team.
Context
Boundaries and Interactions
Committed Resources
Team K worked with their product manager to identify resources they needed. Primarily, they discovered that in order to practice continuous integration, they needed a build server that no one had ordered yet. The product owner took on the influencing assignment to make sure they would get one fast.
Prospective Analysis
