DAY TO DAY TASKS Flashcards
Documentation? Where do you document the SailPoint IIQ processes and procedures?
Documenting all SailPoint IdentityIQ (SAILPOINT IDENTITY IQ) tasks on Confluence, I began by setting up a dedicated space named “SAILPOINT IDENTITY IQ Implementation”. Within this space, I
created distinct pages for each primary task associated with SAILPOINT IDENTITY IQ such as “Identity Aggregation”, “Access Review”, “Role Management”, and so on. Each page detailed the
objective, steps, and best practices related to the respective task.
To ensure clarity, I included visual aids like flowcharts and screenshots wherever necessary. These visual components highlighted the SAILPOINT IDENTITY IQ user interface, assisting team members in correlating the documentation with the actual software.
For tasks that involve multiple steps or subtasks, I utilized Confluence’s collapsible content macro, allowing readers to expand sections as required. This kept the documentation concise, enabling users to quickly find the information they sought.
Additionally, I added a “Troubleshooting” section to each page, listing common issues faced during each task and their resolutions.
On the main page of the “SAILPOINT IDENTITY IQ Implementation” space, I incorporated an index, linking to all individual task pages. This table of contents provided users a holistic view and easy navigation to specific tasks.
Finally, to foster collaboration, I embedded a comments section at the bottom of every page. This allowed team members to ask questions, provide additional insights, or suggest revisions.
Over time, as tasks evolved or when new tasks were introduced in SAILPOINT IDENTITY IQ, I ensured the Confluence documentation was promptly updated, maintaining its relevance and utility.
How did you pick or select your Daily Tasks from the Jira board?
In determining my daily tasks for SailPoint projects, I primarily leverage JIRA, a widely used project management tool that offers a visual board for task tracking.
Each morning, I start by opening my JIRA board dedicated to SailPoint specific tasks. The board, typically structured in a Kanban or Scrum format, is populated with tasks categorized into different columns like “Backlog,” “In Progress,” and “Done.” Each task (or “story”) on the board represents a specific work item related to the SailPoint implementation or support, and is tagged with essential metadata like priority, assignee, and estimated completion time.
I follow these steps to pick my tasks:
1. Review Priorities: I begin by reviewing any high priority or urgent tasks. These are often highlighted or tagged with labels like “Critical” or “Urgent” and may be related to production issues, key milestones, or client demands.
2. Check Due Dates: Some tasks have strict deadlines. I filter tasks that are due in the next few days to ensure timely completion.
3. Progress on Ongoing Tasks: Before taking up new tasks, I assess the status of tasks already “In Progress.” If any are close to completion, I focus on finishing them to keep the workflow moving
smoothly.
4. Collaborate with a Team: Sometimes, tasks require collaboration. I reach out to team members to align on joint tasks, ensuring that we’re not blocking each other and that tasks are being handled efficiently.
5. Pull from the Backlog: After addressing high priority and ongoing tasks, I pull new tasks from the “Backlog” column, starting with those that have been prioritized or earmarked for the current sprint or cycle.
This daily ritual helps me stay organized, ensures that critical tasks don’t fall through the cracks, and allows me to provide stakeholders with timely updates on SailPoint related activities.
