Technical Bank

There is a thin line between a ScrumMaster and a facilitator. A ScrumMaster doesn’t need to work on the user story or design solutions, but he or she should understand user stories, technology, and the people behind the project in order to become a better ScrumMaster. ScrumMasters are not event managers. Rather, a good ScrumMaster will remove impediments, and a better one will prevent the impediments from forming and affecting the team to begin with. How?  Start the day the right way Many who manage projects are tuned into their day on automatic pilot: They open the laptop and stare at the screen, usually reading their emails. Why? Because that is how we connect to ongoing work from where we left off yesterday. In order to become the better ScrumMaster, leave your seat and meet with the people around you. Team members, extended team members, and colleagues will ask us whether we've seen or read a particular email. Our answer will be no, but we can listen to their issues through imp

In this part, we'll start off by adding another XSLT file (for the news item pages), and then move on to look at how we can integrate standard .Net User Controls to Umbraco. Also available in this series: Getting Started with Umbraco: Part 1 Getting Started with Umbraco: Part 2 Getting Started with Umbraco: Part 3 Getting Started with Umbraco: Part 4 Adding the newsList Macro Create a new XSLT file (and macro) in the back-end and call it newsList . In this XSLT file we'll be using a non-standard entity, which is the HTML entity &\mdash; . In order to use this entity we need to define it in the entity list in the XSLT doctype declaration at the top of the file. To add the mdash entity add the following code within the square brackets directly after the defined non-breaking space entity: < ! ENTITY mdash " &#x2014; " > We'll save a variable so that we can easily access the newsList node in order to get its child nodes. Directly after the currentPage p