Welcome to PMConnection

     

Menu
· Home
· The Project Management Search Engine
· Exclusive Articles

Related Sites

Related Books 1
   
Agile Practice Guide from PMI  

   
A Guide to the Project Management Body of Knowledge: PMBOK 6th Edition 2017

  
PMP Exam Prep: Rita's Course
 
  
  
Microsoft Project 2016 for Dummies

   

Microsoft Project 2016
  

  
The Ultimate Application Administrators Guide for Project Online

PMConnection: PMConnection Articles

Search on This Topic:   
[ Go to Home | Select a New Topic ]

Project Management: 461 Project Management Terms
PMConnection Articles

Note: You may find this helpful:

Posted by webadmin on Saturday, July 28 @ 06:47:40 CDT (758 reads)
(Read More... | 2206 bytes more | Project Management | Score: 0)

PMP: PMBOK® Glossary Terms and Definitions
PMConnection Articles Photo

Note: You may find this book helpful:


Posted by webadmin on Sunday, July 22 @ 05:05:14 CDT (499 reads)
(Read More... | 1755 bytes more | PMP | Score: 0)

MS Project: Quickly Switch Sprint Views and Move Tasks Forward in MS Project
PMConnection Articles

Screenshot of moving a task from one Task Board column to another.


Quickly switch sprint views and move tasks forward

In Project Online Desktop Client, you can more easily switch between sprints, identify your current sprint, and move tasks forward to the next sprint.

To view specific sprints or move tasks forward:

  1. Open a project that uses sprints and go to the Agile Tools: Scrum tab.

  2. Do one of the following:

    • In the View Sprints drop-down box, choose the sprint you want to view.

    • Right-click a task and choose Move to Next Sprint.


For more on using sprints in Project, see Use agile in Microsoft Project Online Desktop Client.


Note: You may find this helpful:

Posted by webadmin on Sunday, May 06 @ 21:56:37 CDT (318 reads)
(Read More... | 1573 bytes more | MS Project | Score: 0)

MS Project: Set Percent Complete from Sprint and Kanban Views in MS Project
PMConnection Articles

Set percent complete from a task board

In Project Online Desktop Client, the Set % Complete field in Task Board, Sprint, and Kanban views allows you to update percent complete for tasks when you move them from column to column. This percent complete will persist in your Gantt Chart view as well.

To use Set % Complete:

  1. Open a Project file and on the View tab, choose Task Board.

    You can also use Set % Complete in a Sprint or Kanban board. 

  2. On the task board, select Set % Complete below a column name and enter a value, such as 50.

    Screenshot of the Task Board, with the cursor entering the number 50 for % Complete
  3. Move a task into that column.

    Screenshot of moving a task from one Task Board column to another.

    When you open the task, you'll see that the Percent complete for that task now matches the column's percent complete.

    Screenshot of a task's Task Details dialog showing Percent complete

To hide Set % Complete from your Task Board view:

  • On the Task Board Tools: Format tab, clear the Show % Complete Mapping check box.


For more on how to use these, see Use agile in Microsoft Project Online Desktop Client.


Note: You may find this helpful:

Posted by webadmin on Sunday, May 06 @ 21:51:02 CDT (287 reads)
(Read More... | 2774 bytes more | MS Project | Score: 0)

MS Project: Filter Sprint or Kanban boards in MS Project
PMConnection Articles

Filter the Task Board View

If you're using Project Online Desktop Client, you can filter your Task Board view to see tasks related to either a specific resource or summary task. You can also use these filters when viewing Sprint or Kanban boards.

To filter the Task Board:

  1. On the View tab, choose Task Board.

  2. In the upper right of this view, select the filter button.

    Screen shot of the filter button in task board view.
  3. Select the down arrow next to Summary Task (0) or Resource (0), and choose from the list. You can choose multiple summary tasks or resources to filter by.

    Screenshot of the Filter Resources drop-down on the Task Board with two resources selected



Note: You may find this helpful:

Posted by webadmin on Sunday, May 06 @ 21:41:12 CDT (264 reads)
(Read More... | 2144 bytes more | MS Project | Score: 0)

MS Project: Nearly 200 Microsoft Project Schedule Templates Sorted by Popularity
PMConnection Articles

Nearly 200 Microsoft Project Schedule Templates Sorted by Popularity.  You can also sort them by name, date added, or user ranking.

See all the MS Project Schedules Templates from here.


Note: You may find this helpful:

Posted by webadmin on Tuesday, April 03 @ 19:54:56 CDT (1493 reads)
(Read More... | 1858 bytes more | MS Project | Score: 0)

Program and PMO: DAD vs SAFe vs Scrum
PMConnection Articles


The following table has been developed to quickly compare the three different methodologies of DAD, SAFe and Scrum along-side their seven respective domains of; roles, processes, artifacts, benefits, complexity, usage, and tools.


Domain

DAD

SAFe

Scrum

Details

What is DAD?

What is SAFe?

What is Scrum?

Roles

Primary Roles:

• Team Lead

• Product Owner

• Architecture Owner

• Team Member

• Stakeholders

Secondary Roles

• Independent Testers

• Specialists

• Domain  Expert

• Technical Expert

• Integrator

Team:

• Product Owner

• Scrum Master

• Team

Program:D

• Product Management

• Release Train Engineer

• System Architect

Large Solution:

• Solution Management

• Solution Train Engineer

• Solution Architect

Portfolio:

• Lean Portfolio Management

• Epic Owners

• Enterprise Architect

• Product Owner

• Scrum Master

• Team

Processes

Inception      

• Form Initial Team

• Develop Common Vision

• Align with Enterprise Direction

• Explore Initial Scope

• Identify Initial Technical Strategy

• Develop Initial Release Plan

• Secure Funding

• Form Work Environment

• Identify Risks

• Develop Initial Test Strategy

Construction

• Produce a Potentially Consumable Solution

• Address Changing Stakeholder Needs

• Move Closer to a Deployable Release

• Improve Quality

• Prove Architecture Early

Transition    

• Ensure the Solution is Consumable

• Deploy the Solution

Ongoing        

• Grow Team Members

• Govern Delivery Team

• Leverage and Enhance Existing Infrastructure

• Address Risk

• Improve Team Process and Environment

• Coordinate Activities

Portfolio

• Establish Strategic Themes

• Define Epics

• Create Portfolio Backlog

• Create Portfolio Kanban

• Align Budgets to Value Streams

Large Solution

• Define Capabilities

• Create Large Solution Backlog

• Create Large Solution Kanban

• Conduct Solution Planning

• Conduct Solution Demo

Program

• Define Features

• Create Program Backlog

• Create Program Kanban

• Conduct WSJF

• Conduct PI Planning

• Establish PI Objectives

• Conduct System Demos

• Conduct Inspect and Adapt

Team

• Define User Stories

• Create Team Backlog

• Prioritize User Stories

• Create Sprint Backlog

• Execute Sprint

• Conduct Daily Standups

• Conduct Review

• Conduct Sprint Retrospective

• Define User Stories

• Create Sprint Backlog

• Conduct Sprint Planning

Execute Sprint

• Conduct Daily Standups

• Conduct Sprint Review

• Determine if shippable product

• Conduct Retrospective

Artifacts

• Initial Vision and Funding

• Business Roadmap

• Technology Roadmap

• Initial Requirements

• Release Plan

• Initial Architectural Vision

• Iteration Backlog

• Consumable Solution

• Funding and Feedback

 

Portfolio

• Investment Themes

• Business and Architecture Epics

• Portfolio  Backlog

• Portfolio Vision

Metrics

Program

• Product Roadmap

• Vision

• Program Backlog

• Team Backlog

• NFR's

• Architecture Runway

• Business and Architecture Features

• Metrics

Team

• Team Backlog

• Team PSI Objective

• Sprint Goals

• Working Software

• Spikes

• Metrics

• Product Backlog

• Sprint Backlog

• Burn-Down Chart

• Increment

Benefits

• Proven, well documented and flexible

• Clear roles, artifacts and events

• Scalable from 2, 3 or 4 levels

• Hybrid framework

• Flexible

• Phases with milestones support large scale agile delivery

• Geared for individual teams or small organizations

• Easier to implement than DAD or SAFe

• The basis or the foundation in which both DAD and SAFe are built upon

Complexity

Medium

High

Low

Usage

Scalable throughout entire organization – Not prescriptive.

Scalable throughout entire organization – Very prescriptive.

Team Level

Tools

• Microsoft TFS

• Blueprint

• The Enterprise • Transformation Advisor

• MethodPark Stages

• IBM Rational Method Composer (RMC)

• Atlassian - JIRA

• Microsoft - InCycle

• CA Technologies - CA Agile Central

• VersionOne - VersionOne

• Allocable

• One2Team

• Sciforma

• Target Process

• SmartCore

• AgileZen

• VersionOne

• CA Agile Central

• YouTrack

• GitLab

• JIRA



Note: You may find this book helpful:

Posted by webadmin on Monday, January 08 @ 23:01:01 CST (6669 reads)
(Read More... | 35163 bytes more | Program and PMO | Score: 5)

PMP: There is Still Time to Pass the PMP Exam!
PMConnection Articles


When is the PMP Exam Changing?

The PMP Exam is changing on 26 March 2018.  Learn more here

  • Is there still value in obtaining the PMP certification?  Answer here and then see the results from you peers.
  • Get a PMP Exam Prep Plan here.
  • Find the PMBOK® Glossary Terms and Definitions 5th Edition online here.
  • Get a PMP Application Template in Excel here.
  • Get thousands of FREE PMP Exam Prep questions here.
  • PMP Exam Day Tips here.

 

Find more information: #‎PMPExamPrepWeek

Note: You may find this book helpful:

Posted by webadmin on Saturday, December 02 @ 06:28:12 CST (1194 reads)
(Read More... | 2737 bytes more | PMP | Score: 0)

Project Management: What is Scrum
PMConnection Articles


Scrum is a management and control process that cuts through complexity to focus on building products that meet business needs.  It is also one of the most rigid Agile appraoch in terms of recommended practices and procedures.  Scrum is an implementation of Agile. The process involves performing just enough planning to get started, creating the minimal feature set.  Then we build what was planned, then it is tested and reviewed.  Once this cycle is complete, we end up with a Potentially Shippable Product.  This process usually occurs over a time period of one to three weeks.  This process of Plan, Build, Test and Review is known as a Sprint.  Depending upon what is being built, it may take multiple Sprints before a Shippable Product is complete.

In Scrum, there are three key roles needed in order for the framework to work well.  The Product Owner is responsible for defining the Features that are needed in the product.  The Scrum Master is a servant leader to the team.  Their responsibility is to protect the team and the process, running the meetings and keeping things progressing forward.  The Team is the third role.  It can be made up of Developers, Testers, and anyone else who helps in building the product.  Team members often play multiple roles.  For instance, sometimes Developers may end up doing some testing or Testers may perform some form of development.  Either way the team works collaboratively to get the product done.

There are three artifacts or documents used for Scrum.  First is the Product Backlog.  This is where the Product Owner keeps a list of all the User Stories and then works to prioritize that list.  This list evolves and priorities may change at every sprint.  User Stories are a way of describing a feature set.  A User Story follows the format of "As a _______, I need _______, So that ______." format.  By phrasing the User Story in this way, this allows the Product Owner to specify the right amount of detail for the team to estimate the size of the task.  The highest priority User Stories go into the Sprint Backlog. These are estimated for size and are committed to for the next sprint.  Burn down charts show the progress during a sprint of the completion of tasks in the sprint backlog.  This chart should approach zero points as the work is being completed.

There are three ceremonies that make up Scrum.  Think of these as meetings or discussions.  Sprint Planning is where the Product Owner, Scrum Master and Team meet to discuss the User Stories and estimate their relative sizes.  The Daily Scrum is a brief stand-up meeting where the team discusses what they completed since the previous meeting, what they are working on and anything that might be blocked or need help.  The Sprint Review and retrospective occurs at the end of the Sprint.  This is where the team demonstrates the completed work to the Product Owner.  The team also discusses what they can do to improve the process going forward.

The Scrum workflow looks like Backlog to Sprint Planning to Sprint Backlog and then into the Sprint.  The Sprint is a one to three week time-box where the User Stores committed to during the Sprint Backlog are worked through to completion.  During the Sprint, the Daily Stand-up occurs.  The outcome of the Sprint is a potentially shippable product.  The Product Owner makes the decision if it can ship or if more features are needed.  Finally, at the end of the Sprint, the Sprint Review and Retrospective occurs.  This workflow is repeated for each Sprint until all features for the product are complete.


For more information on this topic, visit Scrum.org



Note: You might find this helpful:

Posted by webadmin on Thursday, November 02 @ 23:16:22 CDT (1670 reads)
(Read More... | 5451 bytes more | Project Management | Score: 0)

Project Management: What is Scaled Agile Framework or SAFe 4.5?
PMConnection Articles

Scaled Agile Framework (or SAFe) is an agile software development framework consisting of a knowledge-base of integrated patterns intended for enterprise-scale Lean-Agile development.  SAFe is scalable and modular, allowing an organization to apply it in a way that suits its need.

SAFe is a framework meant to cover the entire organization.  The current version is SAFe 4.5.  It has 4 levels; Portfolio, Large Solution, Program and Team.  The Team level works very much like standard scrum.  At this level, there is an Agile team which is cross functional and works together to deliver working systems every two weeks which are called iterations.  The content of the iteration is determined by the Product Owner who is in charge of the team backlog.  The iteration starts with a team planning meeting in which the team decides what user stories they can deliver by the end of the iteration.  Each day the team meets in a daily standup meeting to discuss the progress and at the end of the iteration they demo their results to the Product Owner to make sure they have delivered the desired results.  The team then conducts a retrospective to determine what they can improve for the next iteration before starting the cycle again with a new planning meeting.  All of this is guided by a Scrum Master who makes sure the team works smoothly within the process and that it keeps improving.

The Program level is very similar to the Team level.  The Program is comprised of multiple Teams working to deliver a larger system together.  The Program ranges from 50 to 125 people.  This team of teams is called an Agile Release Train or ART.  It will also time-box it’s effort into Program Increments or PI’s which are 5 iterations by default.  The content for each PI is determined by a Product Manager in the Program Backlog in the form of Features.  This will provide most of the content for the Team Backlogs.  The ART is governed by the RTE or Release Train Engineer.  This role acts as the trains Scrum Master ensuring that it runs smoothly and stays on track.  He is somewhat of the Program Manager at the Program Level.  Each PI begins with a planning meeting in which all members of the teams get together to hear the Vision and Roadmap of the train and the features for the upcoming PI.  Each team then plans what objectives they can achieve in this PI.  They also identify dependencies with other teams on the train as well as risks.  The teams commit to these PI objectives as a group providing visibility to Business Owners and Customers of what they can expect to be delivered in this PI.
  
To make sure the train will meet its objectives, we have both a bi-weekly meeting of the Scrum Masters and the Release Train Engineer to ensure all are on the same page and everything is on track.  At the end of the iteration, a system demo is delivered.  This is a demonstration of the integrated system.  This ensures that we don’t have one team running ahead but that the whole train is iterating together.  Adequate architecture and infrastructure is needed to ensure the trains are running as fast as possible.  Each PI serves as a time to lay down the track for what we think we will need in order to achieve our goals in the following PI.  This is called the Architecture Runway and it is facilitated to by the trains System Architect.  
Each PI is 5 iterations long, but only 4 iterations are planned.  The fifth iteration is called the IP iteration or Innovation Planning iteration.  The iteration part is for the team engage in creative ideas like hackathons.  Within the Planning part, three things occur; a) demo our accomplishments, b) maintenance for the train by retrospective on how to improve collaboration, c) plan next PI together.  The IP also serves as an estimating guard-band to make sure the teams deliver on their commitment.

The Large Solution level provides the means to coordinate ARTS who are building even larger solutions in which a single ART can’t deliver by itself.  At this level Solution Management is the content authority.  The Value Stream Engineer is the coach and guide and a Solution Architect to help ensure good architecture is used.  The Value Streams run the same PI cadence as the ARTS and has Planning, Solution Demo, and Inspect and Adapt for cross-ART capabilities.

The Portfolio Level is somewhat different than the other levels.  Portfolio Management helps dictate direction for all underlying Value Streams by deriving Strategic Themes from the Enterprise Strategy and then allocates budgets to Value Streams to support these Themes.  They also manage cross Value Stream initiatives which impact several solutions in the form of Epics.

See interactive SAFe Big Picture from here


Note: You may find this book helpful:

Posted by webadmin on Wednesday, October 04 @ 14:21:50 CDT (2008 reads)
(Read More... | 6755 bytes more | Project Management | Score: 5)

Feature Product



Website Sponsors
"Over 20 templates for $20"

Survey
Which version of Microsoft Project do you currently use?

a) 2016
b) 2013
c) 2010
d) 2007
e) Older
f) I do NOT work with Microsoft Project
g) Project Online Professional - Most current from Office 365

Answer here, then see results from your peers.

Search This Site
Use Google technology to search the entire PMConnection website here.

Buzzword


Event Calendar

PDU's via the Web here

Total Hits
We received
28926401
page views since January 2006

Looking for Books?
Try this link!!

Need a Template?
Free Project Management and Microsoft Project Schedule Templates here!

The Project Management Mall - Now Open!

Latest Exclusive Articles
1. Project Management

2. Microsoft Project

3. PMP

4. PMO and Program Management

5. Microsoft Project Server

6. Portfolio Management

All Exclusive Articles...



Copyright 2005-2017 PMConnection.com. All Rights Reserved.
http://www.pmconnection.com a
PHP-Nuke Copyright © 2005 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 1.59 Seconds