Technical Bank

I came across this weird scenario wherein we were migrating old legacy project coded in Vb.net into Sitecore. So during this process, we had to migrate in a prioritized manner which made difficult to share analytics across two different projects. So I have just noted down what I did in order to accomplish the same. Assume we have a scenario with two different projects which are utilized for same Website (Some pages in Sitecore and Some pages in any other framework ). Let's Assume Sitecore Project named as " CodeYourWaySitecore " and other project named as  " CodeYourWayLegacy " For  CodeYourWaySitecore  and  CodeYourWayLegacy  (“ CodeYourWayLegacy.demo.com ” and “ CodeYourWayLegacy.demo.com ”)  are hosted on different websites.   By default in session, analytics work for each individual site.  Identifying and merging contacts at the end of the session allows for post-session interactions(assuming the contacts have been identified) but does nothing to add

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

Imagine how great (and maybe mildly spooky) it would be if, every time you were about to make a bad decision, someone would materialize out of the mist and say, “Whoa, there, let’s stop and reconsider this.” Thanks to Gilberto Urueta Sanroman and his article at Scrum Alliance, you may not need such supernatural assistance to avoid mistakes in scrum. He compiles a list of 10 scrum mistakes for your team not to make: Scrum Process Too many tasks in progress Behavior-oriented management Not having a clear goal Making decisions for the team Focusing only on efficiency Trying to centralize control Missing visualization No team-building activities No environment in which to fail Forgetting about quality Heeding the Mist Whether because stories have not matured enough or the deployment system is not ready, tasks can pile up, and if you proceed into the next sprint taking on new stories while the old stories are largely incomplete, you can bet  no one  is going to be happy in the end. Sometime