Process flows
Processes and Reports
Agile team delivery empowers teams to view and execute planned work through the use of customizable Kanban boards. Teams create discrete user stories to describe and categorize their work, then estimate the effort needed to complete the work. Stories are prioritized and scheduled into an appropriate timebox, such as a sprint, and as work progresses, team members move cards across boards towards review or completion. Planview's agile integration capabilities allow organizations to integrate multiple agile team tools into Planview AgilePlace, so teams can work using their preferred methodology and processes.
Video: Team Backlog Management Demo
Team Backlog Management Process Steps
Team backlog management process flow
| Process Step | Description |
|---|---|
|
Create stories |
Break features down into discrete user stories for the team to work on. |
|
Describe and categorize stories |
Clearly define a goal for each user story that team members can work toward. |
|
Estimate story sizes |
Realistically assess the scope of the work that will be required to complete each user story. |
|
Prioritize story backlog |
Rank the stories in the backlog to determine which stories should be worked on first. Use metrics in Card Scoring to determine what work should be prioritized. |
|
Schedule stories into appropriate timebox |
Schedule story cards across timeboxes or sprints, and set work in progress (WIP) limits to avoid overloading team members with work. Use the Agile Planning Series view to visualize how planned stories and delivery dates align to higher-level planning increments, such as program increments (PIs). After planning, teams begin work toward their defined goals. |
Video: Team Execution Demo
Team Execution Process Steps
Team execution process flow
| Process Step | Description |
|---|---|
|
Assign stories to relevant team members |
Spread story assignments across the available team members based on available team members' abilities, workloads, and schedules. |
|
Deliver stories |
Iterate on the work required to complete each user story. |
| Collaborate on designs and plans using whiteboard | The Whiteboard is a tool that you use to create designs and plans while collaborating or brainstorming, similar to an actual whiteboard. You can use elements such as shapes as you brainstorm, and if desired convert text within elements to cards on a specified board. |
|
Update card status |
As work is accomplished on each user story, assigned team members can update cards by moving them toward review or completion. |
Video: Team Integration Demo
Team Integration Process Steps
Team integration process flow
| Process Step | Description |
|---|---|
|
Deliver work using connected agile tools |
Teams use their preferred agile team tools to complete work and user stories, with status information visible in Planview AgilePlace. This is supported by Planview's agile integration capabilities which allow organizations to connect one or more agile team tools, as well as multiple federated instances of a given team tool, into Planview AgilePlace. |
AgilePlace (Connected) Process Steps
Planview AgilePlace connected to Planview Portfolios
| Process Step | Description |
|---|---|
|
Create AgilePlace board and make available for integration |
After creating your board in AgilePlace using a template or a custom setup, set the board to be available for integration with supported Planview products so real-time information about work progress can sync between AgilePlace and Portfolios. To create new work tasks in a project’s work breakdown structure (WBS) from new cards created on the AgilePlace board, define the card type and the lanes where this work will appear in Portfolios. For more information: |
|
Create project/epic in Portfolios and flag for sync to AgilePlace |
When creating a work epic or project in Portfolios, initiate the link between Portfolios and AgilePlace to begin syncing work across platforms. You will also select the default AgilePlace board for the sync. |
|
Set the appropriate tasks in the work breakdown structure (WBS) to sync to AgilePlace |
In the Portfolios WBS, designate which tasks to sync to the AgilePlace board. Set the Sync with the AgilePlace flag to create the synced card in AgilePlace. Each task will sync to the defined default board but can be changed to a different board. Here you can select the option to import AgilePlace child cards, which will automatically create synchronized tasks for child cards of the connected AgilePlace parent card. |
|
Card is created on assigned AgilePlace board |
When tasks in the Portfolios WBS are synced to AgilePlace, cards are added to the default drop lane of the selected AgilePlace board. In AgilePlace, add card details and create parent-child connections to cards if needed. |
|
User story created and marked to sync to Portfolios |
Once you have synced Portfolios to AgilePlace, new cards created in AgilePlace can sync to projects in Portfolios. This creates a new task in the project’s WBS. |
|
New task created in WBS |
When you create a new card in AgilePlace and set it to sync to an available Portfolios project in the Parent Card drop-down, the card creates a task in the assigned project’s WBS, complete with card details, start date, end date, and more. |
|
Maintain plan; update milestone/activity status as work is completed |
Maintain the project plan by reviewing and updating milestones and activity status in the WBS. |
|
Monitor project progress |
In Portfolios, review progress using data synced from cards in AgilePlace. This information is used to monitor the project progress and can be viewed within the WBS, work portfolio column sets, and Power BI dashboards. This provides the ability to assess and make real-time decisions with all available information. |
|
Parent/child connectors automatically updated |
With synced tasks, you can change parent/child card relationships in AgilePlace and the connector will automatically update the parent/child task relationships in Portfolios. |
|
Describe and categorize stories via users, start/finish dates, etc. |
Clearly define goals for each user story that team members can work toward. Categorize card types to reflect the kind of work in process and set start and end dates to keep track of planned deadlines. Descriptions and categorizations on AgilePlace cards will update task information in Portfolios. |
|
Prioritize backlog |
Rank stories in the AgilePlace backlog to determine which stories should be worked on first. Use AgilePlace Card Scoring to prioritize work. |
|
Assign stories to appropriate timeboxes |
Schedule story cards across timeboxes or sprints, and set work in progress (WIP) limits to avoid overloading team members with work. Use the Agile Planning Series view to visualize how planned stories and delivery dates align to higher-level planning increments, such as program increments (PIs). After planning, teams begin work toward their defined goals. |
|
Time reporting |
Users enter time via time reporting in Portfolios, or if Planview's Agile Costing solution has been enabled, the connector will automatically populate timesheet data into Portfolios using data derived from cards in AgilePlace. |
Team Execution Process Steps
Team execution process flow
| Process Step | Description |
|---|---|
|
Assign stories to relevant team members |
Spread story assignments across the available team members based on available team members' abilities, workloads, and schedules. |
|
Deliver stories |
Iterate on the work required to complete each user story. |
| Collaborate on designs and plans using whiteboard | The Whiteboard is a tool that you use to create designs and plans while collaborating or brainstorming, similar to an actual whiteboard. You can use elements such as shapes as you brainstorm, and if desired convert text within elements to cards on a specified board. |
|
Update card status |
As work is accomplished on each user story, assigned team members can update cards by moving them toward review or completion. |
Team Integration Process Steps
Team execution process flow
| Process Step | Description |
|---|---|
|
Deliver work using connected agile tools |
Teams use their preferred agile team tools to complete work and user stories, with status information visible in Planview AgilePlace. This is supported by Planview's agile integration capabilities which allow organizations to connect one or more agile team tools, as well as multiple federated instances of a given team tool, into Planview AgilePlace. |
Best Practices
Center on continuous improvement
One of the main benefits of agile methodology is the understanding that incremental steps in the right direction will lead to vast improvement over time through an iterative, emergent process. Remember that change can be difficult, and results will not happen overnight, but driving with continuous improvement and sticking to the process will pay dividends over time.
Aim for Minimum Viable Product (MVP)
Remember that the first iteration will never be perfect, and that’s intentional, as future iterations will leverage the team’s continued experience and feedback to optimize the improvement process. MVP lets teams quickly bring deliverables to the table, which enables the feedback, experience, and improvement processes.
Use what works
Different teams may need different tools or methodologies, and that’s encouraged within the agile framework. Some teams may need different timeboxes, others may not need any. Let teams work in a way that is most effective for them, whether that is Scrum, Kanban, Scrumban, or another method.
Integrate tools
However your teams work, it’s important they are equipped with tools that support them and that organizational leaders still have line-of-sight into the work they are doing. Make sure your tools are integrated, making use of dashboards and onboard reporting, so that data is communicated and visualized in a single source of truth that is easy for all parties to use and understand.
Create cross-functional teams
Silos break down communication and cause delays for organizations. Eliminate silos altogether by implementing cross-functional teams that are grouped not based on similar job roles but instead on working together towards creating a specific value for the organization.
Limit Work-in-Progress (WIP)
Agile is not about fast, it’s about focus. Assigning team members too much work causes everything to be delayed. Team leaders must ensure tasks are broken down into small, achievable chunks, and that work-in-progress stays within a certain threshold, so that team members are not bogged down but can instead focus on one small task at a time.
Visualize work and blockers
The ability to quickly decipher what each team member is working on and determine the cause of unexpected delays is critical to on-time delivery and optimizing working processes. Use a work visualization strategy such as Kanban to be able to easily show work progress and identify bottlenecks.
Measure delivery time
Flow, throughput, scope, lead and cycle times are all different ways of measuring delivery time. Tracking these metrics can show where inefficiencies are occurring so that you can adjust accordingly, allowing the team to anticipate or eliminate these issues and bring value faster.