Webcast: Professional Scrum Development with Visual Studio - Presented by: Richard Hundhausen - What are you looking for?
Looking for:
Professional scrum development with microsoft visual studio 2012 free |
- Professional scrum development with microsoft visual studio 2012 free
Maybe you are just the kind of developer who leaves a bunch of half-eaten sandwiches sitting around your house. Later, when the crisis has passed and the developer is able to return to the planned work, he or she can select the suspended work and click the Resume link.
The original pending changes will be unshelved, and the task will be put back in the In Progress section. Other IDE settings and behaviors will be restored as well.
In the event that your interruption gets interrupted, you may want to suspend it, and return to your original work. If this is the case, then instead of a Resume link, there will be a Switch link. Clicking Switch will suspend the interruption work, and return context to the original task. Alternatively, you can choose to Merge With In Progress and bring all the pending changes from the two tasks together.
Visualizations allow the Development Team to elicit feedback more easily. This feedback can come from other members of the Scrum Team, as well as stakeholders, especially domain experts.
Shapes and lines drawn on a whiteboard to represent components and actions enable ideas to be vetted by the right people. As previously mentioned, feedback is important when brainstorming how to tackle a problem such as developing a particular feature or scenario.
This is especially true when the developers are not familiar with the domain or the workflow is complex. Having the right people involved in the conversation is critical. The more eyes you can put on a problem, the better the chances of finding an optimal solution. Unfortunately, this is not always possible when the required people are geographically distributed. The Scrum Master might have to get involved to make sure the introductions, communication, and collaboration occur effectively.
This is natural in an organization that encapsulates its critical business processes into software. The developers know the software, and thus the domain behind it. For Development Teams that love their whiteboards, I recommend setting up a laptop with a webcam in the meeting room or team area. By aiming the webcam at the whiteboard, and then strategically standing out of the way after drawing on it, remote attendees can be part of the design session and discussion.
This is less ideal than collaborating in person, but still allows for rapid design with a dry erase pen, rather than fumbling with a software design tool. When the Development Team has a need to present their ideas to and gather feedback from remote stakeholders, then the new PowerPoint Storyboarding feature in Visual Studio can be beneficial.
The illustration is created by dragging and dropping predefined, inline images and adding formatted text. It could be that the Development Team had to iterate on the design of a complex feature or scenario with a remote stakeholder or two before they were able to estimate it. From my experiences, the more likely reason is that someone on the team got bored, fired up PowerPoint, and started designing something.
When a developer has spare time, he or she should help the rest of the Development Team complete their forecast work. Wary of generating waste, he and the other developers keep them to the right rough level of detail.
This was a practice that they opted into as a team. You can also start the tool from the Start menu under Microsoft Visual Studio or by starting PowerPoint directly. Add slides, shapes, and text to the blank presentation to illustrate a PBI, feature, or scenario, as shown with the Customer Login storyboard in Figure Others may provide feedback by annotating the PowerPoint document or by using the Feedback client.
As the stakeholders review the storyboard, they can add comments or even make changes to the illustrations using the built-in features of PowerPoint. If the presentation is stored on SharePoint, it can enjoy the dual benefit of broad availability and revision control. Users can check out the presentation and check in any changes. Feedback can also be provided out-of-band, via email, voice, or using the Feedback client, which is covered in the next section.
On the surface, they appear to be very similar in functionality. Another important difference is that SketchFlow is able to convert forward-engineer the prototypes into starter projects. They will always just be illustrations. To create a storyboard, a developer can select from several layouts that support common user interfaces, such as web and Windows Phone backgrounds.
Images can be dragged and dropped from the Storyboard Shapes pane in addition to using all the features available within PowerPoint. These features include clipping and inserting screenshots, hyperlinking from one page to another, animation, inserting images and shapes, and aligning and grouping objects.
You can save a custom shape to MyShapes and then use it in the same way that you use the predefined storyboard shapes. Also, you can export shapes to share with other developers on the team or import shapes that others have created. Microsoft has also created a Storyboard Shapes Authoring tool to help make storyboard shapes that can be used with PowerPoint Storyboarding. Before you can link a storyboard to a work item, you must save it to a shared location.
The shared location can be any shared folder on the network or a SharePoint site such as the team project portal. By linking the storyboard to a work item, you are essentially inviting the rest of your team to access this shared file, so be sure they have the appropriate permissions.
They can open the presentation, review it, and add their comments. You can link storyboards only to certain types of work items based on the process template from which your team project was created. It is possible to link a storyboard to more than one work item. You cannot create work items from PowerPoint, but you can link to them. This means that if you create the storyboard first, you will have to switch to Visual Studio or Team Web Access to create the PBI so that you may link it.
This situation is less likely to occur for a Scrum Team, who should be creating and grooming PBIs a long time before the Sprint.
Storyboarding is not available in Visual Studio Professional or Express edition. To view storyboards that were created by using the PowerPoint Storyboarding template, users must have PowerPoint or later installed. They do not need Visual Studio installed.
In the past, some developers on the team have used Balsamiq to mock up complex UIs. Over time, the Development Team realized that in-person conversations at a whiteboard provide the most value.
They take this approach whenever possible. When this happens, they will usually generate and send the storyboard over email or even store them on SkyDrive, allowing the stakeholder to review and comment.
Once the feature or scenario is done, the storyboards are deleted. As you read in the last section, the PowerPoint Storyboarding tool enables a team to create rapidly a UI mockup or illustration of a feature that can be shared with other team members or stakeholders. Feedback should always be welcomed, and even encouraged. If the feature has been released and valid feedback is given, it can be captured in the Product Backlog to be considered for future development.
One of the new features of Visual Studio is the ability to capture rich stakeholder feedback on features being implemented and bugs being fixed.
This is good for distributed organizations who want stakeholders to evaluate the emerging Increment or a design that may still be in flux. The Feedback client is used to gather this type of feedback. It is versatile enough that it can be used to provide feedback on anything the user can see and interact with on the desktop. This type of feedback can either be formally requested via a work item and email sent from Visual Studio, or it can be provided voluntarily, without solicitation.
We will look at both scenarios shortly. The first feedback scenario occurs when a member of the Scrum Team, preferably the Product Owner, solicits feedback from one or more stakeholders. These stakeholders will receive a feedback request through an email that is constructed from the feedback request form. From the email, the stakeholders can install and launch the Feedback client tool, which guides them in providing and capturing their feedback.
TFS stores this feedback as a Feedback Response work item. This requirement was mentioned earlier in the chapter in the context of setting up email alerts and, hopefully, it is already configured. Feedback can be requested on any aspect of the product, from the entire application down to a specific scenario within a feature. Because the feedback request is essentially an email, the requester can be as ambiguous or as specific as he or she wants to be. In addition, one request can be partitioned to ask for feedback on up to five discrete items.
For example, if the Development Team is code-complete on three scenarios within a PBI, a request could be created that contains three items—one for each scenario the Product Owner desires feedback on. Regardless of the size and scope of the request, the stakeholders must be able to access physically the application and feature s in question, and they must have the time and know-how to do it.
This should be considered as the feedback request is created. When creating the feedback request, one or more stakeholders must be selected. These users must have an email address associated with their user name.
The stakeholders should also be told how to access the application in question. An address and instructions can be provided for a web application, rich client application, or a remote machine.
Finally, the item s to be evaluated and any related notes are added to the request. Figure shows a feedback request ready to be sent to a stakeholder to evaluate the Customer Login feature of a web application.
Consider previewing the request before sending it. It will show what the email that the stakeholder s receive will look like and allow you to customize it. It will also show the email addresses rather than the user names, so you can see if there are any discrepancies, such as wrong or missing email addresses associated with the user names.
If this occurs, you can just add the email address manually and continue with the request. However, you should ask the stakeholder to update his or her profile and provide a valid email address to avoid this error in the future. As the feedback requester, you will receive a copy of the email submission automatically when you send it. You can also add other email addresses in the To box when previewing the email.
Figure shows a sample email requesting feedback. If an administrator has not granted permissions to the accounts of those stakeholders that you add, they will not be able to provide feedback through the Feedback client. When the stakeholder receives the request, he or she should first make sure that the Feedback client is installed. If this is the first time providing feedback, it will need to be installed.
The email contains a hyperlink to download it, if necessary. Next, the stakeholder starts the feedback session by clicking the large hyperlink in the email, or copying and pasting the supplemental URL into the web browser. As the stakeholder reviews the new feature, he or she is able to perform the following tasks using the Feedback client:. On the Provide page of the Feedback client, one or more items appear for the user to provide feedback.
Figure shows the various recording options. If there are multiple items, clicking Next will advance to the next item for which to provide feedback. Figure The Feedback client provides many ways to record and attach your feedback. By annotating screenshots, the reviewer can indicate corrections or improvements by adding text or images to the screenshot that was captured.
By default, Paint opens automatically when the user opens a screenshot image that was captured within the Feedback client. Another annotation tool, such as Paint.
NET or Snagit, can be configured instead by clicking on the cog icon at the top of the feedback tool, as shown in Figure After feedback has been provided for each item, the user can review, make corrections or additions, and then submit the feedback to the requesting user via TFS. Be careful when recording sensitive data, such as user names, passwords, account numbers, etc. If the recording is going, everything will be captured. If you do record sensitive data, you can delete the recording by deleting its representative image in the text box and then record it again.
In order for stakeholders to be able to provide feedback, an administrator must grant them specific permissions in TFS. They can either be added to the Limited license group in Team Web Access or a custom group with specific permissions. If the stakeholders have a CAL and you are not going to use the Limited group, then make sure to grant the minimum permissions required, which are project-level permissions to create and view test runs and view project-level information, as well as area path permissions to view and edit work items in the respective nodes.
Regardless of which permissions approach you take, you should try to group the feedback stakeholders together in their own Windows group. Because providing feedback is probably the only way that they will interact with TFS, keeping them grouped together will simplify management and allow the Scrum Team to know exactly who their feedback stakeholders are.
Feedback requests generate a Feedback Request work item assigned to the creator of the request. The Description field contains the body of the email that was sent. Feedback Response work items are created to hold the feedback provided by the stakeholder using the tool. Remember that both Feedback Request and Feedback Response work item types are designated as Hidden types.
Instead, they are created using the appropriate tool, such as the Request Feedback link and Feedback client respectively. Gathering feedback from stakeholders is the responsibility of the Product Owner, not the Development Team. If the developers want to seek feedback from stakeholders or other domain experts, they should do it with the blessing of the Product Owner. If necessary, the Scrum Master can help facilitate this. If the Feedback client is being used inconsistently with the rules of Scrum, the Scrum Team should discuss it during the next Sprint Retrospective meeting and adapt accordingly.
She will sometimes send a request for feedback to a stakeholder in a remote office, along with a link to the test website. Andy the TFS administrator will add any new stakeholders to the Limited license group in Team Web Access so that they have adequate permissions.
Another way to use the Feedback client to provide feedback is for a stakeholder to start it directly. It can be found on the Start menu under Visual Studio When started, the client will be in voluntary feedback mode. Hopefully, the stakeholder will already know what application to start, what features or scenarios to evaluate and provide feedback on, and what team project to submit the feedback response to. Feedback that has been submitted voluntarily like this can be found in TFS by running the Feedback shared query.
This query returns work items that are in the Microsoft. FeedbackResponse Category work item type category. When viewing a Feedback Response work item, you will see many of the standard fields, such as title, created by, state, rating, area , and iteration. The more interesting data will be in the Notes field, as it contains the comments typed by the stakeholder and any references to audio, video, screenshots, or attached files.
Be aware that any files attached in the Feedback client will appear as Result Attachments links on the All Links tab and not as true work item attachments. Backlog team project Supporting the entire lifecycle of the product What should you name your team project?
Source control Set up the folder structure Choose a branching strategy Local workspaces vs. Where do bugs come from? In-Sprint vs. Acceptance test-driven development Keep the conversation going Collaborative specifications Executable specifications Acceptance test-driven development Test-driven development Automated acceptance testing Creating a test case Associating an automated test CodedUI CodeFirst Executing automated acceptance tests Reusing test cases Other acceptance-testing frameworks Acceptance Chapter burndown 8.
Improving 9. Part Two: How will the chosen work get done? Beginning Visual C Programming. Written for novice programmers who want to learn programming with C and the. NET framework, this book offers programming basics such as variables, flow control, and object oriented programming.
It then moves into web and Windows programming and data access databases and XML. The authors focus on the tool that beginners use most often t Discover how to turn requirements into working software increments - faster and more efficiently - using Visual Studio in combination with Scrum and Agile engineering practices.
Designed for software development teams, this guide delivers pragmatic, role-based guidance for exploiting the capabilities of Application Lifecycle Management ALM tools in Visual Studio and Team Foundation Server.
Team members will learn proven practices and techniques for implementing Scrum to manage an application's life cycle, as well as seamlessly plan, manage, and track their Scrum projects. Richard Hundhausen 2 books.
Comments
Post a Comment