VIDEO: How to Create and Use Surveys in SharePoint 2013

written by: Tom Robbins on January 20th, 2015

The video below will demonstrate how to set up a survey in SharePoint 2013, the different options for question creation, how to fill out the survey, and then finally how to review the results.

Greetings fellow SharePointers!  We were going talk about how to create and use surveys in 2013.

Within the SharePoint site, we will set up an Experience survey demonstrating how to use different types of questions. This survey will allow for anonymous and multiple responses, and we will demonstrate how to do that.

Step 1: Creating a Survey

Add an app and type in survey. A survey is just a special type of list.

Step 2: Advanced Settings

Go to Advanced Settings to select for questions to be anonymous and allow for multiple responses.

Step 3: Creating the Questions

As soon as we click next, SharePoint immediately takes me in and lets me start creating the questions.

Question 1: Do you have any experience with SharePoint?-We’ll make that a choice field (yes/no) and require a response, make it a drop down menu

Question 2:  What versions do you have experience with? We’ll make this a required field too. Fill in the version options. Let these be a check box so that you can select more than one.

Question 3:  Please rate the following SharePoint features. List the different features or a few features- lists, libraries, surveys, discussion boards, business intelligence. Then you can set the range 1-10 or 1-5. I think 5 is enough. And then well say at the bottom in the scale, don’t like, its ok, love it, and well do an n/a so that people can say not applicable to any of those items.

Question 4:  Would you like to be kept up to date on the progress of our SharePoint installation? We’ll make this a yes no and a yes by default. That way if you dont change anything well be able to send you emails.

Last and finally create a place to provide an email address and make that a single line of text. We wont make the email address required and then well click finish.

Step 4: Branching Logic for Question 1

So now, where we would normally see the columns for list, we see each of the individual questions and the only thing left to do before we test it out is go back in and put in some branching logic for this first question. So if you have no experience with SharePoint, we are just going to jump straight to this question asking whether you would like to be kept up to date on the progress. So to do branching logic, we simply click on the question that we want to give branching logic to. Now that the question has been created, there will be options for branching logic. So if you say no to do you have any experience with SharePoint, were going to jump straight to would you like to be kept up to date with the progress. That’s how simple it is to create the questions. We used a couple of different options- choice fields, rating scale, yes/no, single line of text.

Step 5: Responding to the survey
Now just click on the experience survey and we can go ahead and respond to the survey. So because the first question has to be answered before any other questions can be shown, we have to answer it.

ex. Do you have an experience with SharePoint?  Yes, I do. Click next. So now you can choose the options of which versions of SharePoint we have experience with. Notice now in the rating scale we have the different features of SharePoint listed from don’t like to love it. After completing all questions and entering email (not required), click finish. That’s how easy it is to create and respond to a survey.

Step 6: Reviewing Results
You can also click the links (see video) to see the survey results as people are filling out the survey as people are filling out the results. You can also switch back and forth to the overview as well as see all responses. For this example, that’s the only response to the survey we’ve had so far, so that’s the only one that will show.  You can also export your results to excel if you want to do any further analysis.


Web Seminar Recap: Leveraging DevOps and Agile for Customer Value-Driven Outcomes

written by: Jennifer Johnson on January 16th, 2015

The DevOps “Way” of thinking is sweeping the more successful IT departments we read about. The implications are rippling across project and program management domains. If you are a project or program manager, team leader, or business analyst, the time has come for YOU to understand how to derive value from the DevOps way of thinking and create positive impacts on your operational methods, applications, and your continuous deployment model.

The DevOps way is disrupting the conventional understanding of the value chain across projects – and not just hard IT projects. As new capabilities and evidence of value arise from successfully implementing the DevOps way of thinking and working, it is important to help team leaders bridge the gap between traditional project and IT learning and the newer DevOps way such that we leverage existing resources and optimize for the future.

On Wednesday, January 15th, 2015, this one-hour presentation was presented by Richard Jenny, veteran Program Manager and DevOps Director, as he shared some real-world insight and impact of combining Project Management, Agile and DevOps practices to realize significant ROI on both project and operational work.

Missed the web seminar? Find the slides here!


30% off Remaining January Seats

written by: Kaete Piccirilli on January 16th, 2015

Get prepared for projects and growth in 2015 with ASPE-IT course offering. We know that as the year progresses and projects start that it can be hard to find time to squeeze in that training you’ve wanted to get completed. That’s why we are offering one of our best discounts to fill the remaining seats that are available in our January in-person and live online training classes. This offer is even available to be used on our new classes such as DevOps Boot Camp and Effectively Using Microsoft Project Server 2013.

We’ve provided a list for you to browse of the classes with remaining seats available in January. Register now using the code JAN011530. You can register online or by giving us a call. Be sure to reference this code to receive your 30% off discount.


SharePoint 2013 Collaboration Features: Surveys

written by: Tom Robbins on January 12th, 2015

While SharePoint is often initially looked to as a document management system or a replacement for network drives, by definition, SharePoint is an “Enterprise Collaboration Platform”.  Certainly one of the many ways to implement SharePoint is to address the management of documents, or information lifecycle, but because SharePoint is all about collaboration and engagement, there are many tools and features the facilitate this.

Welcome to 2015 and a new year to talk about SharePoint and really learn more about implementing it effectively!  In my January blog posts, I’m going to talk about some of the new and old collaboration features.  It’s all about Engagement and bringing your teams together to work better.  Each week I will talk about the features in my written blog posts and then demo how to implement those collaboration tools in the live environment.

Those collaboration tools that are often overlooked and misunderstood are: Surveys, Blogs, Discussion Boards, and Wikis.  There are also some new features introduced in 2013.  Those are the Newsfeed and Communities.  Many times people just shake their heads and say that these tools are just the “Facebook” or “Internet” social stuff and they immediately turn away from them.  But there is more value than meets the eye.  Ask the Zuckerberg’s of the world if there is interest in social and if social has had an impact on how the planet communicates!!  I think you will find that the internet and social platforms have a huge following and significant impact.  People really do find value in these tools.  Imagine people getting as excited in talking about work as they do about kittens and bagels!  Let’s start the year off right by talking about the first of these SharePoint tools: Surveys.

Click to continue »


CISM Study Notes: Risk Assessment – Part II

written by: Mike Beevers on January 6th, 2015

In part 1 of our CISM exam preparation series we discussed quantitative risk analysis methods.  In this post we will look at it’s counterpart; qualitative risk analysis.

Qualitative risk analysis is possibly the simplest to perform and least exact method of analyzing risk an.  Based on a scenario, qualitative risk analysis provides a “best guess” as to “how bad would it be if….”   Although it is very simple to perform, the result of quality of risk analysis, does not produce a precise numeric value.  Instead, qualitative risk analysis produces a range of opinions based on a given scenario. These opinions can be rated on any sliding scale, perhaps 1 to 10.  The opinions can be used to prioritize risk.

Let’s walk through an example:

As the owner of a small local bakery, how bad would it be if you went into work one rainy morning and noticed a leak in the roof over the electric ovens you use to bake bread every day.  On a scale of 1-10, how bad would this problem be?

Obviously this is a very simple example.  Remember we still want to measure risk based on impact and likelihood, so let’s expand our scenario a little bit:

As the owner of a small local bakery, what is the chance that the roof would leak over the electric ovens you use to bake bread every day?  If this were to happen, how bad would the outcome likely be?

Again, we are not looking for precise numbers, simply a best guess estimate on a sliding scale of, perhaps, 1-10.

Click to continue »


Web Seminar Recap: Using InfoPath Designer 2013 to Build Powerful SharePoint Forms

written by: Tegan Smith on December 22nd, 2014

SharePoint is an Enterprise Collaboration platform which drives organizational engagement and allows teams to work on information together in a central portal. InfoPath 2013 is a part of the Microsoft Office Professional suite of products that allows users to design, distribute, fill out, and submit online forms. Integration with SharePoint allows for seamless information management by allowing users to fill out forms in the SharePoint site directly in a browser window. With the InfoPath web part, users are able remain in the context of site pages while filling out the forms. Users are able to customize the default SharePoint forms to provide unique branding to match their organization. InfoPath is a powerful application development tool which includes conditional formatting, logic and validation, and integration with SharePoint workflow to create a complete business process automation experience. This webinar introduced the user to InfoPath and some it’s features. There will be demos using InfoPath to edit a SharePoint default form, as well as create a form based on a template or from scratch. The future of InfoPath has changed with Microsoft’s recent announcement regarding its position on future support of InfoPath.

The topics that were covered in this one hour webinar:

• Explanation of the tool and it’s uses
• What is the future of InfoPath 2013?
• Tour of the InfoPath interface
• Features of InfoPath
• Editing a default SharePoint form
• Creating a sample form to automate business data gathering

This one hour seminar, Using InfoPath Designer 2013 to Build Powerful SharePoint Forms, was held on Friday, December 19th by Tom Robbins. If you missed this seminar and want to catch up download the slides and recording here.


Web Seminar Recap: Automating Builds using TFS 2013

written by: Tegan Smith on December 16th, 2014

Developers still wasting time building code manually? Do you struggle with running builds and deployments in a consistent way each and every time? TFS can help you fully automate the build and deployment process.

This webinar, Automating Builds using TFS 2013, was held on Friday, December 12th by Bryon Brewer. The webinar will include a live demo to walk attendees through the process.

Missed this seminar? Download the slides and recording here.


Video Demo: SharePoint 2013: Creating Document Sets

written by: Tom Robbins on December 16th, 2014

This week’s video blog is a follow up to the first two videos talking about creating and working with document sets. Before starting on creating the document sets, I’m going to review the first two video blogs.


The goal is to use the document sets to address the creation of a feature request process. The feature request process is made up of four pieces of content:

  1. Feature Request Document (.docx)
  2. Request Details Document (.xlsx)
  3. Proof-of concept presentation (.ppt)
  4. Feature functionality flowchart (.vsd)

These pieces must be created before the document set is generated. That is done by creating the content types for each.

  • Attach a template
  • Define any document Meta data
  • Define information management policies if required
  • Update the document information panel template
  • Attach a document specific workflow

Create the document set. Document settings allow you to:

  • Set allowed content
  • Set default content
  • Specify any shared columns
  • Welcome page configuration

Requester, requested date and status will be defined as Meta data. Create a library where the document set will be used. (Version control can be turned on if needed.) Enable management of content types on the library and add the new document set to the content types on the library.

To create the document set, first create all the document content types in feature requests under my site content types section.

Each of these documents has a template attached to them built in the respective applications and uploaded into the content types. I created a site here to house all of the content, and a default document library called feature requests.

Under site settings, look for site content types. Choose create. Name this ‘feature request document set’. The document set content type is in the document set content type’s group. Under that, choose the content type. Create a group to store this feature request document set and name it.

Take a look at advanced settings. This is where it is defined whether the document set is ‘read only’ and whether or not any changes to this document set should also be propagated to any document sets that were based upon this content type.

If we had a workflow that we wanted to attach to this document set, we could do that under workflow settings. Under that is where you delete the document set. Here we can also manage retention, audit barcode policies, etc. We can specify the specific document set settings and the Meta data. The Meta data I was going to specify was the requester, requested date and status.

  1. The requester may need to be created from scratch but for this video we can use ‘Referred By’.
  2. We’ll add requested date and make that a date and time column.
  3. And then add status, we’ll call this request status. Make that a choice field.
  4. Next make a dropdown menu with the following: started, in progress, approved, and declined.
  5. The default will be set to ‘started’ the instant you create the document set.

Define the allowed content types that will be in the document set. Select from the feature request content types and add each of these documents.

Choose each of the content types to tell SharePoint what should be provisioned when the document set gets created. Point to the template again. You may not actually want to use the same template that’s defined on the content type here in the document set, but in my case I do. These are the default pieces of content. Remove the default content type that’s just a blank word document.

Shared columns allow me to specify which of the default Meta data could also be created on the documents themselves. Out of the Meta data we created on the document set, I’ll create everything on the welcome page. If we have any content types already based on this one we can make an update. Select yes to do the update. Click ok.

The content type and document set are ready to go.

  1. Go under library settings
  2.  Enable the use of content types with the management of content types on this library under advanced settings.
  3. Click allow the management of content types.
  4. Scroll down and click ok.
  5. From here add from existing content types. Add from my feature request document sets. Click ok.

Make sure the default word document is not an option when we go to create a document set. Make it invisible by unselecting the checked box under visible. The feature request document set is now the default content for this library. Open the default all documents view and add in the referred by, the request date and the request status, so they appear on the default view.

We’re ready to test out the documents with a new feature. Any time we use a new feature, we need to go through this process:

  1. Select request feature document set and give it a name.
  2. Enter description, referred by and requested date.
  3. Notice the status is on ‘started’.
  4. Click save

Across the top is your welcome page. In the document sets you also have a separate tap to manage the document sets and complete various actions. This completes the document set creation process.



CISM Study Notes: Part I – Risk Assessment

written by: Mike Beevers on December 15th, 2014
Through an official partnership with (ISC)² we offer the most current, continually updated and rigorous CISSP authorized certification training on the market. Master the security concepts and best practices maintained in the CISSP Common Body of Knowledge, and get certified.

ASPE has teamed up with Tactical Security, Inc. to offer CISM training courses beginning with the June 2014 exam cycle.  In order for you to begin preparation, we are going to begin a series of articles to help you study for the CISM exam.  The CISM exam consists of four domains:

  1. Information Security Governance (24%)
  2. Information Risk Management and Compliance (33%)
  3. Information Security Development and Management (25%)
  4. Information Security Information Management (18%)

The percentages indicate the number of questions you are likely to see in each domain.  Please note that the percentages are in accordance with the 2015 version of the CISM exam.  The percentages may vary by year.

These study notes are designed to be quick snippets of information related to one or more topics within the exam.  Today we are going to look at Risk Assessment, a part of Information Risk Management and Compliance domain.

Risk is measured in impact and likelihood.  Impact will tell you how much damage or loss the company may incur, while likelihood indicates the chance of that loss incurring.  There are four main methods of assessing risk; quantitative, qualitative, Failure Mode and Effect Analysis (FME), and Fault Tree Analysis (FTA).

Click to continue »


Web Seminar Recap: What is DevOps? A Colorful Introduction

written by: Tegan Smith on December 12th, 2014

For decades, application developers and IT operations people have been set up in armed camps, often at odds with each other and unable to trace sources of frustration to their root cause. The business suffers while non-technical people wonder “what everyone in IT is doing.”

DevOps is a grassroots movement sweeping IT and project shops across the western world. Like any buzzword, there’s no exact definition and lots of misconception. However, the underlying forces and reasons behind the DevOps movement are clear. It’s an exciting and heady brew of corporate culture shifts, IT worker empowerment, amazing new tools, cloud computing capabilities, and movement towards a new vision of enterprise IT capability which is unified, agile, and oriented around the needs of the business. Properly understood, this movement reveals a world where it’s possible to deploy code faster and more effectively than ever – continuously, with an ethic of non-stop quality improvement and value for the business.

In this one-hour presentation by Chris Knotts on December 8th, 2014, we will take you on a tour of the DevOps movement and explain the massive potential that lies behind it.

Missed this seminar? Download the slides and recording here.