If you want to use something like VLC Player or another network streaming app that has trouble accessing the channel list, you can do use the following URL format:
would load channel 50.
A place to talk about technology.
Your client wants SharePoint, but not plain old SharePoint. They won’t let you hire a developer. You cannot deploy solutions to the server. We see this often while working for various government and commercial clients, and on the surface it looks like it will limit our ability to provide the solutions they need. However, there are many features of SharePoint right under the surface that are often overlooked. SharePoint can do a lot if you just know what's possible.
This session will discuss ways to create business solutions using SharePoint without complex programming or needing to deploy complied code solutions to the server. We will cover Functionality (Libraries & Lists, Metadata, Workflows, and Forms) and Visualization (List Views, Pages & Web Parts, Branding, and Reporting/Dynamic Content).
The audience for this session is anyone using SharePoint, in particular new users, content managers, and budding Power Users and Front End Developers in scenarios where they do not have access or control to fully customize the instance of SharePoint they are using. You will come out of this session with some out-of-the-box features and front end configurations that can be used to enhance your SharePoint sites.We hope to see you there!
|The Chumby One, running Zurk's Offline Firmware.|
In January 2013, one of the volunteers initiated an effort to create a company to acquire all of the remaining assets of Chumby Industries for the purpose of maintaining the service. That company, "Blue Octy, LLC", completed the transaction in mid-February.They created a temporary stub service that will allow the following devices and apps to boot to a clock:
|The Insignia Infocast 3.5 by Best Buy |
(similar to the Chumby One).
|My boys really enjoy the Sony Dash. We have it|
in our dining room.
|We have installed the Insignia Infocast 3.5 in our master |
bathroom media station.
Before I get into the rest of the Scrum for SharePoint Article Backlog, I wanted to take a moment to talk about what happens at the beginning. It is always important to start things out right, and a Scrum-based SharePoint project is no different.
This is an example of being Agile, right? I am reordering the Article Backlog based on new priority from the Blog Owner (me) and working on the top priority item first, just like we would do in Scrum.
As with everything, how a projects starts will vary based on the project and your particular environment. "It depends." I want to document some ways of handling Scrum for SharePoint and see what sticks. In fact, I am looking for your experiences, good and bad, for different ways for starting up a Scrum project that is building out a SharePoint site, application, or an entire farm.
Many questions come up at the beginning of an Agile Scrum project. In particular: When are we going to have time to set everything up? Good question. If you start your first Sprint developing against the Product Backlog but don't have a development/test and/or production infrastructure in place yet, what do you do?
Scrum is designed to be iterative, which means you have a Product Backlog of functionality that needs to be built, which may change over time, but there is no set project plan. Each Sprint takes a piece of that Product Backlog and builds it out within a certain time box. I'll explain more in future posts. For now, just know that a Sprint is between 2-4 weeks and is focused on developing a certain set of features. The list of items in the backlog changes as priorities change, but once a Sprint starts the priorities for that Sprint are set.
It is possible to build time in to each Sprint to handle infrastructure changes and additions. Even for environments that already exist, you are going to need time to adjust them to fit the needs of the project and Product Backlog. In fact, much of the infrastructure work may be totally outside the Scrum process. Infrastructure, in my opinion, makes a lot more sense as a waterfall project. That said, the development team may still need to be part of the process and it might be too much to ask them to do a lot of infrastructure and development environment work alongside actual development. Which is why I think it's good to start out with something in place before any development begins at all.
If no infrastructure exists—say you are building a brand new SharePoint farm or planning to migrate content from an older version of SharePoint—then more work needs to be done so the development team can hit the ground running at Sprint 1. Do not assume that the team will have time to set things up once they are working on user stories and committing to a certain amount of velocity for each sprint. While velocity can be adjusted to fit in time for administrative or overhead tasks, or user stories can be created to work on infrastructure things (is this even a good idea?), the team's focus will be on building out functionality and it will required a concerted effort to work on anything outside of development.
For environments that already have a full or partial SharePoint infrastructure, the job is much easier but there is still work to do. You need developer environments, a development/build server, a test infrastructure, and stuff like source control and something to manage the Agile process (SharePoint, maybe?). Things will go much smoother if they already exist or there is time to set these up before tackling the product backlog.
I guess my point is that while Scrum for SharePoint can be Agile, you still need to consider the foundation of the project team's resources before any development work begins.
In addition to infrastructure and development resources, the beginning of a Scrum project may also include an assessment of the initial Product Backlog, some agreement on initial team process, and maybe a cursory attempt at an overall architecture. Yes I said there might be some design before you start. Does that go against Agile? More on these topics in future posts.
So, what do you do before starting your Scrum for SharePoint projects?
Back to [Scrum for SharePoint: Article Backlog]
Next in series [Coming soon]