<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Michael David Cobb Bowen on Medium]]></title>
        <description><![CDATA[Stories by Michael David Cobb Bowen on Medium]]></description>
        <link>https://medium.com/@mdcbowen?source=rss-f3440935c16b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fY3JkK0Pr32KHnbZ8QpV-w.png</url>
            <title>Stories by Michael David Cobb Bowen on Medium</title>
            <link>https://medium.com/@mdcbowen?source=rss-f3440935c16b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:46:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mdcbowen/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Efficient Unified Analytic Platform]]></title>
            <link>https://medium.com/full360/the-efficient-unified-analytic-platform-fa779a0c1847?source=rss-f3440935c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa779a0c1847</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[Michael David Cobb Bowen]]></dc:creator>
            <pubDate>Thu, 04 Feb 2021 21:54:54 GMT</pubDate>
            <atom:updated>2021-02-04T22:19:49.494Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GWgvHdi3-dWm3gn4WPAMtQ.jpeg" /></figure><p>There’s an ironic story about Jeff Bezos. Several years ago at Re:Invent, when he could be counted on to present, I watched him talk about his inability to predict the future of technology. <a href="https://youtu.be/O4MtQGRIIuA">What he said is constant</a> is people’s desire to want more for less money. So while he couldn’t tell what technology would win in the future, he could guarantee that AWS’ ability to employ economies of scale would keep them competitive. I was very impressed by that approach. The irony today is that many cloud customers complain most about the sometimes hidden costs of their IT appetites and their bills.</p><p>At Full 360, we have increased our appetites and expertise as managed service providers for cloud native data architectures. But we’ve also followed Bezos’ theory. Our customers want more, for less. That’s why we are particularly proud of <a href="https://elasticdw.com/">Elastic Data Warehouse</a> (eDW), the product we have been evolving since the first day we ran Vertica in the AWS cloud a decade ago.</p><p>There are several reasons why eDW provides more for less. The primary reason is that it was designed for massive scalability from the beginning. So we have never had to change anything basic about its architecture. When we were getting started, in the days before Redshift, we built one of the largest columnar data warehouse clusters ever in the AWS cloud. Secondly, our focus on reliability and ELT speed led us to develop tools and methodologies that integrated well. That included <a href="https://aws.amazon.com/blogs/big-data/upsert-into-amazon-redshift-using-aws-glue-and-sneaql/">SneaQL</a> and the PITbull Architecture. In 2019 we were all about <a href="https://insight.full360.com/the-evolution-of-data-warehousing-in-the-aws-cloud-cd31638c26e0">the evolution of data warehousing in the cloud</a>. We have always employed structured data lakes, and we were always about accelerating the speed of data we process. These built-in advantages of Full 360’s data platform allowed us to leverage our own professional services group to handle much <a href="https://full360.com/case-studies/">larger customers with complex requirements</a> than most companies our size. We have always been built for speed and efficiency. That translates to lower costs because we are sure-footed when it comes to data architecture and workload deployments.</p><p>In 2020 we had time to do some introspection and rethink what we had here. We’ve always had the confidence to do what so many skeptics said was ‘impossible’ in the enterprise data warehousing space, including innovations like ML for aircraft scheduling that integrates legacy systems. In partnership with industry experts we have realigned ourselves to work within the framework of <strong>Unified Cloud Analytics</strong>. Our unique strength in this area is that we are not far off in practice from the core of the vision. While many others will adopt this vision, we can say that we have been pioneers and notably that we have been successful in bringing down the overall costs of cloud-first data architecture and managed services. We have been rightsizing our customers’ implementations for many years.</p><p>The vision of Unified Cloud Analytics depends on two premises that we think are self-evident. The first is the emergence of <strong>cloud supremacy</strong>. More enterprise data is in the cloud today than is on premise. We expect that fraction to increase to 63% by the end of this year. Secondly, the emergence of the <strong>unified analytics warehouse</strong> is making its presence felt. Full 360 has been building multi-tier data architectures for years now, integrating traditional data warehouses with new data lakes and new realtime streams. We have long been aiming for mastery of multi-structured, multi-latency data in a single platform. That platform is the basis of Full 360&#39;s managed service business, and it is the principle behind the development of Elastic Data Warehouse.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yyZNS5vhS1Fb9DS2Pl-2tg.png" /></figure><p>It bears repeating that Vertica is the core of our eDW platform. We have reduced the complexity of managing Vertica in the cloud so that it is both approachable and affordable, even for SMB customers. The promise of elasticity has long been understood, but very few businesses have been able to reliably scale down or turn off their analytic data warehouses over the weekends. We have made it easy. In fact for our own purposes we even have Slack integrations that remind us at the end of the day to turn off multi-node clusters we have running for development and test. That’s efficiency.</p><p>You may have come to this point wondering why there’s a picture of Niagara Falls above. Did you know that engineers turned them off in 1969? It takes quite a bit of skill to pull that off, but the proper engineering can make it happen. We’ve made it easy to make such dramatic changes possible regularly in your AWS account, saving you money and headaches.</p><p><strong>Try ElasticDW Free for 90 days or forever for non-commercial use.<br> </strong><a href="https://www.vertica.com/landing-page/get-started-with-vertica-fast-with-full-360/"><strong>Get started today.</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa779a0c1847" width="1" height="1" alt=""><hr><p><a href="https://medium.com/full360/the-efficient-unified-analytic-platform-fa779a0c1847">The Efficient Unified Analytic Platform</a> was originally published in <a href="https://medium.com/full360">Full 360 (A Micro Focus Company)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Virtual Team Success: The Ideal Status Meeting]]></title>
            <link>https://medium.com/full360/virtual-team-success-the-ideal-status-meeting-ac0483ce352d?source=rss-f3440935c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac0483ce352d</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[meetings]]></category>
            <dc:creator><![CDATA[Michael David Cobb Bowen]]></dc:creator>
            <pubDate>Wed, 08 Jul 2020 21:28:37 GMT</pubDate>
            <atom:updated>2020-07-08T21:28:37.399Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P4_5KUB66scNhfBLi2KmEA.jpeg" /></figure><p><strong><em>Culture + Tools + Methodology = Virtual Team Success</em></strong></p><p>It turns out that if people did ideal status reports, most status meetings would run themselves. Nothing’s perfect, but everyone having their status report in hand is a good start. First off let’s consider the dynamics and parameters of a status meeting. If there are more than 8 people in the meeting and some of them are team leaders, then these team leaders should present the status for the team. Ideally, speakers should sit at the table, and other participants in the outside chairs. However, no chair at the table should be empty.</p><p>In the status meeting, everybody should know who the boss is. If there is no boss, follow form and try not to act as if you’re the boss. If you think there would be any controversy in that action whatsoever, start up the meeting like this: “I think the boss would expect us to have this status meeting, so let’s do it.”</p><h4>Structure: The Five Whats</h4><ul><li>What’s Up (optional)</li><li>What’s new</li><li>What’s next</li><li>What’s wrong</li><li>What For (optional)</li></ul><h4>What’s Up (Intro)</h4><p>At the start of the meeting there are three basic points. They shouldn’t take more than 2 minutes altogether. If you are all accustomed to what happens in a status meeting, or you’ve been following this structure for some time, you can skip this entire section, as all of the answers to the below three questions will be obvious.</p><p>- What is this meeting?<br>- Who’s here. who’s not?<br>- What’s the Agenda?</p><p>And so the meeting begins.</p><h4>What’s New (Work Done)</h4><p>Everybody in turn gets to read their report of work done and describe overall if it was a good week, bad week, partial week, unproductive, what ever single sentence works. Everybody should have at least some good news to share. Open up the meeting with this gives a sense of accomplishment. Ultimately even if only one person had a good week there is something the team can be proud of.</p><p>During this time, some brief questions might be asked. “So you finally fixed that issue, did you use the XYZ solution?”</p><p>Remember not to get bogged down in detail. What’s New should not take more than 10 minutes.</p><h4>What’s Next (Work To Do)</h4><p>In the second round, everyone will (in the same order) talk about what’s next. They should also have a good idea what the priority on those tasks should be, and therefore be able to say what they will spend the majority of their time on. They optionally should say whether or not the task is expected to be easy, ordinary, or tricky. If they think they will need help, now is the time to speak up. It’s not impressive to volunteer for something that’s bound to generate issues or problems.</p><p>Sometimes, based upon what was done, new assignments need to be handed out. The boss should make those assignments, but the person whose status it was should have an idea of what that assignment would be. The boss should say out loud whether this has a priority over other tasks or should just be added to the pile.</p><h4>What’s Wrong (Issues)</h4><p>Now we come to the issues. This is where everybody should have maximum focus. So once again, people should go around and state their issues. Now depending upon how good you are in doing meetings, you may combine the second round with the issues round. That is to day, let each person first say what they intend to do in the next work period and speak about current issues and dependencies they have. In ether case, here is how to handle issues.</p><p>For every issue brought up at the status meeting, you need to know <strong>SPUDD</strong>. Severity, priority, ugliness, dependency and difficulty. Sometimes these things are already understood. The most important thing is that the team leader and the parties responsible are unambiguous about all of that. Other people should simply be aware of the existence and nature of other people’s issues.</p><p><strong>Severity</strong> — What are the implications of this issue <em>right now</em>? Have an idea of whether or not an issue can become a problem or trouble, but don’t project importance on a current issue that it doesn’t possess at the moment. In other words, don’t cry wolf.</p><p><strong>Priority</strong> — Your boss or team leader should arrange your work according to the priorities of the team. You have a moment to get them to reconsider, but they have the final say. Make faces if you must, but understand what you are expected to be delivering.</p><p><strong>Ugliness</strong> — This can mean one of two things that should be one and the same, but often are not. Ugliness is about the extent to which you have to <em>break rules</em> in order to resolve the issue, eliminate the problem, or get out of trouble. Ugliness is also about the <em>optics</em> of the issue, problem or trouble. The better your relationship with your customer, the closer your sense of ugliness will match theirs. Sometimes that difference cannot be helped. Your boss or team leader is responsible for finessing such situations and closing that gap, but your attitude makes a difference.</p><p><strong>Dependency</strong> — It might be somebody else’s fault, but it’s your responsibility. So if you are relying on somebody else to do their job so that you can do your job, here is where you let everyone on the team know that. Remember it is also your responsibility to keep poking those people you need to get your job done. But keep in mind the politics of your organization. Sometimes going outside of official channels to do something makes your issue uglier than it ordinarily would be.</p><p><strong>Difficulty</strong> — All things being normal, is this an issue you’ve seen before or had been solved before? In other words, is it a no-brainer, a puzzle, a mystery, a black hole or a rabbit hole? Assigning these on a modified Fibonnaci scale is the best way to assess the time and effort required. In our next blog, we’ll talk about dealing with difficulty and dive deeper into these terms.</p><h4>What For (Outro)</h4><p>If you are the boss, or the process geek, at the end of the meeting, you should remind people what we are supposed to be accomplishing in the long view. If you have to give one person in particular a drubbing, do that offline outside of the meeting. If somebody deserves applause, make it short and sweet.</p><p>—</p><p>Everyone should leave a good status meeting with a sense of purpose, and of having unburdened themselves with the team. Everything should be out on the table.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac0483ce352d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/full360/virtual-team-success-the-ideal-status-meeting-ac0483ce352d">Virtual Team Success: The Ideal Status Meeting</a> was originally published in <a href="https://medium.com/full360">Full 360 (A Micro Focus Company)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Virtual Team Success: The Ideal Status Report]]></title>
            <link>https://medium.com/full360/virtual-team-success-the-ideal-status-report-e2aa597f642c?source=rss-f3440935c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2aa597f642c</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[methodology]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Michael David Cobb Bowen]]></dc:creator>
            <pubDate>Tue, 23 Jun 2020 23:41:26 GMT</pubDate>
            <atom:updated>2020-06-23T23:42:51.922Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SNHoDo3oCCxqxPzP4T0RTQ.jpeg" /></figure><p><strong><em>Culture + Tools + Methodology = Virtual Team Success</em></strong></p><p>In our continuing series, we talk about how to structure an ideal status report and an ideal status meeting. As a traveling consultant, I’ve had to do these for years, and sitting in 10,000 hours of meetings, I can assure you that they work and they are just enough but not too much. In a virtual business environment, the clarity of this status report will allow you to be crisp and concise. Even over Zoom. Simple. Effective.</p><h4>The three to five whats</h4><p>The core of a status report is only three whats. The core of a status meeting is five whats. But depending on how familiar your people are with what’s going on, you might want to include one or both of the other two. The bottom line is that the status report, and thus the status meeting is all about telling people what’s going on. So let’s get to it shall we? First the list:</p><ul><li>what’s up</li><li>what’s new</li><li>what’s next</li><li>what’s wrong</li><li>what for</li></ul><h3>What’s New (Work Done)</h3><p>If you do nothing else in your status report you must do a what’s new. This essentially says what work has been accomplished since the last status meeting. You should report on what <strong>you</strong> did in <strong>your</strong> assignment. If you were on vacation or got sidetracked, you should state that as well. If there was something you didn’t do but expected to do, mention that as well. In a perfect meeting, this will be known ahead of time, or displayed for everyone to see.</p><h3>What’s Next (Work Not Done/ Work To Do)</h3><p>What’s next is what you expect / plan / hope to do before the next status meeting. Easy. 80% of the time most of the people in the meeting will not have a copy of your prior status report. So if you feel bold and you are prepared to promise a lot, then go ahead and promise a lot. But remember the next meeting when you have to say what’s new you will be evaluated. It’s great to make all of your deliverables, but you’re going to mess up. Don’t tempt fate and try to impress people. Also don’t over-promise out of guilt for not finishing up the first time. You will get better at this over time. You should have a good understanding about what the priorities are for in your upcoming work. If you don’t know or aren’t sure of your team leader’s priorities, find out.</p><h3>What’s Wrong (Issues)</h3><p>Here’s where you get to do a little bit of explaining, but keep it very brief. If there are new issues with old problem, or you are waiting on a dependency, this is the place to put it. If there are no issues, don’t leave ‘What’s Wrong’ off of the report. Actually state that you have no issues. IE write ‘None’.</p><p>This issues list is a special part of the report and requires a little detail. You want to make sure that you have an idea what the problem is. “It doesn’t work” is not quite good enough. If you know something is wrong but you don’t know what is causing that problem, you should state the problem something like this. Depending upon whether or not you have a formal issue tracking system like Jira or Trello, your issue should have a number or a date associated with it. The What on this shouldn’t go too deep. Just identify the issue, the priority, and whose help you need to resolve the issue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/556/1*BDKmfgVnrUAWQuZzrFBteA.png" /><figcaption>Issues with some detail</figcaption></figure><p>While we’re at it. It helps to get some perspective on what’s wrong. Think of the severity in the following way.</p><ul><li><strong>Issue</strong><br>This is something that you or your team would normally be able handle on your own, but something went wrong. It’s an issue because it might affect your budget, schedule, quality, or deliverable. It’s something that can be worked around, but ultimately needs fixing. Maybe you think it’s a small low-priority issue that might wait until the next status meeting to on the chance it can be resolved before then, but don’t make that gamble. The last thing you want is for it to become a problem, and then people start asking who knew what and when. Deal with issues before they become problems.</li><li><strong>Problem</strong><br>A problem is something you can’t solve and cannot be worked around in a short amount of time. It compromises your intent, and/or your standards. You don’t want to let it remain. A problem often requires an uncomfortable conversation, but it also may be swept under the rug. That could lead to trouble. Deal with problems before they become trouble.</li><li><strong>Trouble</strong><br>Trouble is when the consequences of the problem are costly. It’s more than just a black mark on your record, it involves people you are not usually accountable to, like your boss’s boss, some powerful authority, or many, many people. You don’t get out of trouble without pain, and unlike problems you don’t get props for getting out of trouble. You merely survive, if you do.</li></ul><p>These examples might help you categorize what’s wrong. Check out their particular contexts.</p><ul><li>“I have an <em>issue</em> with this stupid keyboard.”</li><li>“Our customer keep bringing up <em>issues</em> about the fonts on the inventory website.”</li><li>“The <em>problem</em> is that I cannot get started on the project because we’re waiting for my security sign-off.”</li><li>“If we don’t get this insurance <em>problem</em> resolved by next Friday, we’re going to lose our certification.”</li><li>“Our security guy quit and he changed all of the passwords to the database. He’s in <em>trouble</em>, and so are we.”</li><li>“We’ve got <em>trouble</em>. The contract fell through and they just issued a press release about layoffs.”</li></ul><p>In all cases, anything that surprises you needs to be brought up as an issue in your status report. This puts you well on the road to accountability and transparency. Plus, you set a good example for everyone else.</p><p>Next up we’ll talk about the ideal status meeting and a methodology for handling issues, problems and trouble.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2aa597f642c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/full360/virtual-team-success-the-ideal-status-report-e2aa597f642c">Virtual Team Success: The Ideal Status Report</a> was originally published in <a href="https://medium.com/full360">Full 360 (A Micro Focus Company)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Virtual Team Success: Project Management]]></title>
            <link>https://medium.com/full360/virtual-team-success-project-management-9f9813e2fa44?source=rss-f3440935c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f9813e2fa44</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[accounting]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[planning]]></category>
            <dc:creator><![CDATA[Michael David Cobb Bowen]]></dc:creator>
            <pubDate>Thu, 07 May 2020 15:52:39 GMT</pubDate>
            <atom:updated>2020-05-07T15:52:39.850Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/999/1*Niz_NpMUEP9r2fQW-Hv5Qg.jpeg" /></figure><p><strong><em>Culture + Tools + Methodology = Virtual Team Success</em></strong></p><p>In this continuing series about communications for our business, we are discussing tools and tactics for keeping our minds focused on the right things at the right time. In the first issue, we covered instant communications between ourselves and our partners and customers. Here we talk about some specialized channels of communications.</p><h4>Communicating Secrets</h4><p>As much as we love working with <strong>Slack</strong>, we don’t trust it. In fact, when it comes to secrets, there are only a few communications channels that we do trust, and not too much if we can help it.</p><p><strong>Keybase</strong><br>When it comes to communicating secrets, we are obligated to ensure that it is done securely. We don’t even say passwords over the phone in voice communications. We treat all of our tools with the expectation that they can be hacked. <a href="https://keybase.io/"><strong>Keybase</strong></a> allows us to be as confident as possible that we will not be hacked or have our messages intercepted. Keybase has been around for several years and have improved their product quite nicely. It is trusted enough so that it can be used as a code repository and a cryptocurrency wallet. We used to use Dropbox. Not good enough.</p><p>As part of our jobs, we rotate supporting our customers. That means we need to share passwords between each other. Since we are all virtual, there is no sneakernet. It must go over the wires. We are confident in using Keybase. We use it for passwords and software license codes owned by the company. Also when there are confidential HR materials sent for things like clearances and being bonded for our customers, this is the app.</p><p>As a backup, we use <a href="https://www.signal.org/"><strong>Signal</strong></a> which is maturing nicely and now supports voice, video and attachments.</p><p>While I’m on the subject of sneakernet, it is important to remember that when your team makes a decision to select a communication tool it is more important that nobody hates it than everybody loves it. Since there is no alternative, the team member who hates using tool X may decide it’s not worth communicating through that channel. In that case everyone loses.</p><h4>Project &amp; Time Management</h4><p>Of all the controversies in the world, few get as irritating as how to log the hours you work and expenses your company incurs in a comprehensive and reliable fashion. We are no exception, and we have gone through multiple iterations of drama on this front. We have finally settled on a combination of four tools cleverly integrated together by our own engineers. It is, after all, what we do.</p><p><strong>Wrike</strong><br>The primary communicative face of these four is a tool called <a href="https://www.wrike.com/"><strong>Wrike</strong></a>. Wrike provides a central platform for organizing and communicating all of our billable and non-bilable work. We have worked to make it tightly integrated with <strong>Harvest</strong> and <strong>Xero</strong> our back-end accounting systems. We also have disciplined ourselves to working tightly with the legal documents &amp; quotes we author in <strong>Quotient</strong>.</p><p>Whenever we have an impromptu meeting in a Slack channel that takes more than a few minutes, whoever called the meeting is responsible for putting a link to the task in Wrike that we spent our time in a meeting for that purpose. So this kind of tracking insures that we don’t have meetings just for the sake of having meetings. Over time we develop an implicit understanding of whether we are communicating in order to think out loud and clarify, brainstorm or bring up an issue. (And of course that is a subject for later in the series). We hate wasting time, and our customers need to know.</p><p>We have evolved our configuration of Wrike over time. We have it where we want it. A major improvement in how we do business is matching how we author &amp; negotiate projects with how we manage them. Since we provide professional services to our customers, we have to negotiate a statement of work (SOW). To build our SOWs we use <a href="https://www.quotientapp.com/">Quotient</a>. It provides a consistent framework for how we present our services to a prospect. As we do, we have customized it specific to our needs. The meat of a statement of work consists of descriptions of what is to be done and how much it will cost. We have, for each costed unit of work, the following details.</p><p>- Item<br>- Description<br>- Key Activities<br>- Key Deliverables<br>- Acceptance Criteria<br>- Assumptions</p><p>Each of the key activities is an identifiable <strong><em>task</em></strong> in Wrike. These tasks roll up to a <strong><em>deliverable</em></strong> like ‘Final Design Document’. These tasks and deliverables match one to one between our SOW and Wrike. When we enter time against a task in Wrike, our integration periodically sweeps the Wrike server to place transactions in <a href="https://www.getharvest.com/"><strong>Harvest</strong></a> which has its own integrations with <a href="https://www.xero.com/us/"><strong>Xero</strong></a>, our accounting and billing system. Both are very popular in their own right. When a deliverable is marked complete, we can then bill our customer for that unit of work. This tight integration has a direct impact on our cash flow and everyone on our project teams is keyed into this fact.</p><p>Like many companies, we use a hybrid approach to project management. We are required to understand costs and possible cost overruns in a waterfall style. So we will always tie our costs to a hierarchy within a project. We also need to work in an agile context because the unexpected is always a part of the process, and we need to manage that risk. Wrike accommodates this dual footing by allowing flexibility in reporting.</p><p>At our <a href="https://insight.full360.com/five-simple-secrets-for-running-virtual-teams-7609ac469923">weekly status meetings</a> which we call the ‘Big Top’, each of us is required to speak about whether our Wrike tasks are Done or Not Done. We have a conference in Slack, and must share the screen in front of everyone and have some explaining to do. We can report this <em>Kanban</em> style or in a custom template.</p><p>After that pass, we use Wrike again to show in a <em>Gantt </em>style the hours we have committed to tasks for the coming week. This is how we stay on schedule and on budget even when we have project team members working thousands of miles apart. We get accountability because we have the right systems that communicate the right signals, and we are disciplined to use them properly. It wasn’t easy, but if we didn’t, we’d be in trouble. It has definitely been worth the journey.</p><h4>Incident Response</h4><p>Speaking of trouble tickets, we use <a href="https://www.pagerduty.com/"><strong>PagerDuty</strong></a> to track all of the possible alarms and warnings that we build into our systems. Staff are on call and will be scheduled via PagerDuty. We track incidents there as with any trouble ticket system. However, we make sure that these incidents are integrated into Slack and via email. Most of these alerts are triggered by custom rules built into <strong>AWS CloudWatch</strong>. But most importantly, we are tying these directly to the Service Level Agreements with our customers. In order to be responsible stewards of our customer’s data, computing assets and functioning application systems, we need to be tied into a process that gets our attention and backs up the promises we make. This is the management side of DevOps.</p><p>We use these administrative systems in coordination to manage our time, to discipline our processes and to maintain accountability for the work we do. As a virtual team of creative individuals we keep our personal commitments to use them and structure our communications within our company. These are the kinds of key activities that lots of other companies have considered at length which is why we can use their tools. We think what we’ve learned can help you too.</p><p>Coming up in the next guides, we will talk about knowledgebases, runbooks and maintaining archives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f9813e2fa44" width="1" height="1" alt=""><hr><p><a href="https://medium.com/full360/virtual-team-success-project-management-9f9813e2fa44">Virtual Team Success: Project Management</a> was originally published in <a href="https://medium.com/full360">Full 360 (A Micro Focus Company)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Virtual Team Success]]></title>
            <link>https://medium.com/full360/virtual-team-success-17976e8d4246?source=rss-f3440935c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/17976e8d4246</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[quarantine]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[home-office]]></category>
            <dc:creator><![CDATA[Michael David Cobb Bowen]]></dc:creator>
            <pubDate>Tue, 28 Apr 2020 17:45:57 GMT</pubDate>
            <atom:updated>2020-04-28T17:45:57.415Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SXkcAYhptcuJq0IxeOdqYg.jpeg" /></figure><p><strong><em>Culture + Tools + Methodology = Virtual Team Success</em></strong></p><p>How are we working during the pandemic? Well, to be honest, in much the same way we worked through the very hard times in Venezuela encountered by our LATAM group. We worked as a team, physically separated but united in purpose and method. We have had an internationally distributed team running our business at Full 360 for over five years now. How do we do it? What’s the magic? In this series, I will talk about communications.</p><p><strong>Structured Communications</strong><br>Something that probably isn’t recognized enough about organizations of developers such as we have is that we are very sensitive to electronic communications. If you think teenagers with their smartphones are sensitive, we are even moreso. We are likely to get at least 100 emails per day. Plus a several dozen texts and direct messages. We can expect to get alerts from systems that fail. It helps to know where each kind of communication is done most effectively, between humans and humans, humans and machines and machine to machine.</p><p>Let’s first start with human to human. Obviously we do this through several media. Text, audio, video, graphics and combinations of those.</p><p><strong>Slack</strong><br><a href="https://slack.com/">Slack</a> is our primary mode of communication. Slack is excellent, but we have made it right for us. It is primarily one for text. But we also use it for audioconferences.</p><p>Slack is organized into channels that we design. We created some general purpose channels. All of these start with an underscore so that they are sorted at the top. These are channels like _general, _health, _articles, _projects, _support, _infosec and _random. Some of these are conversational as you would expect, others like _support and _knowledgebase are populated by bots as well as by us. So if there’s a trouble ticket generated by our customer, for example, we will always see it in _support. That is because we have machines programmed to do that particular task of aiding our communications.</p><p>Additionally we have channels that are all about our customers and their projects. We maintain an internal channel, and also one where customers are invited to participate. So for each of our major customers we will have at least two channels for the developers, project managers etc.</p><p>We have learning channels. So when somebody comes across an interesting lesson for a particular service we provide, we can all keep up. We note that these are temporary and should point to more permanent documents in the knowledgebase.</p><p>Many of our employees speak Spanish. We have overcome any shyness in being a small but multilingual company. So it is common to see English, Spanglish and Spanish in channels. We don’t restrain the way people communicate — whatever works.</p><p>In conferencing, Slack allows the full set of functions. Audio, video, text and screen sharing. Most of all, however we use simple audio conferencing. At one time in the past we had VOIP phones. We no longer use them because of Slack.</p><p><strong>Email</strong><br>We almost never use email for internal communications. The primary reason is that there are personal channels in Slack. If I have a message I want to share with only one other person, I can communicate with them one on one in their personal channel. I do use email when talking to customer prospects, partners, or when I want to copy my boss in for formal communications.</p><p>We have integrated Slack with tools like <a href="https://mailclark.ai/"><strong>MailClark</strong></a> which makes email conversations public within Slack and organizes email chains with external customers. Also, any emails to our generic accounts like info@full360.com or sales@full360.com will be replicated to the _opportunities channel.</p><p><strong>Alternatives: WhatsApp, Skype &amp; Zoom</strong><br>These are alternatives that we use mostly because our customers and partners do. When they initiate a conference, we are obliged to use their system of choice. Since we are certified at the ISO 27001 standard, we are required to have a COOP strategy. COOP stands for continuity of operations. So if our primary systems fail, or heaven forbid something happens to one of our officers, we have to have a backup. WhatsApp is our official backup to Slack. We use the free / personal versions of these tools.</p><p><strong>GotoMeeting</strong><br>When it comes to larger companywide functions where we expect to have more than 10 participants, we use <a href="https://www.gotomeeting.com/">GotoMeeting</a>. It is also our choice for presentations to external customers and partners. GotoMeeting allows us to give control of presentations to different individuals and offers the use of external phone numbers. This is especially useful for international customers or those who do not have the application loaded on their machines. It is a bit more of a formal tool, as you can use it to send invitations to anyone with an email address. It is a highly reliable program and although it’s somewhat costly, we have found that it is better than pretty much all of the alternatives.</p><p>I hope these experiences help guide you in your communications tactics and strategies. Coming up in the next guides, we will talk about secure communications, incident response, knowledgebases and project management tools.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17976e8d4246" width="1" height="1" alt=""><hr><p><a href="https://medium.com/full360/virtual-team-success-17976e8d4246">Virtual Team Success</a> was originally published in <a href="https://medium.com/full360">Full 360 (A Micro Focus Company)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When You Work from Home Nothing is NSFW]]></title>
            <link>https://mdcbowen.medium.com/when-you-work-from-home-nothing-is-nsfw-4cce87b25cc0?source=rss-f3440935c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4cce87b25cc0</guid>
            <category><![CDATA[employee-engagement]]></category>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Michael David Cobb Bowen]]></dc:creator>
            <pubDate>Tue, 17 Mar 2020 20:27:37 GMT</pubDate>
            <atom:updated>2020-03-17T20:27:37.480Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BMHi9mV8Di1GFVp5W4OCCg.jpeg" /></figure><p>Now that your boss and people around your office are starting to think about allowing you to work from home, you might need some ammunition to push them over the edge. I have been working from home for almost 10 years as part of a virtual company of software engineers and AWS consultants. There are some downsides and <a href="https://insight.full360.com/five-simple-secrets-for-running-virtual-teams-7609ac469923">tricks to being productive</a>, but these days I’m counting my blessings. I’ll give you a bunch of benefits you may not have considered.</p><p>I work at home with flexible hours.</p><p>So I don’t have to commute, I don’t put a lot of miles on my car. So my car insurance is cheaper. I don’t sit around in useless meetings. I don’t worry about sexual harassment or a hostile workplace. I don’t have to pay for lunch at an expensive or sketchy joint near the office. I’m not tempted to get too wasted during happy hour and then ‘wait for traffic to die down’. I don’t listen to talk radio or other stupid media on my way to and from work. I don’t have to deal with public transportation. I don’t know whose ‘copter is the ‘Eye in the Sky’. I don’t have road rage and I don’t have to deal with others who get it. I don’t feel jealous of that luxury sports car that passed me, or those guys in the carpool lane. I don’t have to drive behind that sketchy pickup truck.</p><p>I don’t have to pretend like I’m busy when I’m not. I don’t worry about overtime keeping me away from meals and family. I discipline myself to be productive. I multitask without guilt. I don’t have to buy expensive clothing I don’t use anywhere else but work. I have exactly the right sized office with everything I want in it and I’m not jealous of anyone else’s office. Annoying people I’d rather not deal with don’t drop in on my unexpectedly. When I need to focus, I can do whatever I need to do to focus, smoke, drink coffee, listen to music, take a short walk.</p><p>I never forget something at home. I can get out of bed at 7:30 and make an 8:00 meeting right on time. I use exactly the electronic tools I want to use to get my job done. I don’t have to ask for a better monitor or desk chair. I don’t have to share access to my workstation with some administrator. I never have to wait in line to use the printer. I don’t snack needlessly on junk from a vending machine. I don’t have to eat mystery meat from a cafeteria. I don’t have to worry about missing a delivery at home. I can curse out loud when dealing with bullshit. I can say the word ‘bullshit’. Nothing is NSFW. I can watch the clock all I want, or not watch it at all. I don’t have to adjust my attitude. I can fart in peace.</p><p>I suffer no uncomfortable elevator rides or security checkpoints. I work at my own pace, with my own brand of air freshener (burning sage). I don’t concern myself with the weather. Nobody steals my pens or erases my whiteboard. My bathroom is always clean, well, as clean as I want it. I can shower or change clothes in the middle of the day. My entire library is right here. My clean desk policy is my own. I can decompress from stressful business. People take scheduling time with me much more seriously.</p><p>That’s work / life balance, and it is more precious than you can imagine. So if the tide is turning against this as the new normal, be the holdout. It’s worth it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4cce87b25cc0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Evolution of Data Warehousing in the AWS Cloud]]></title>
            <link>https://medium.com/full360/the-evolution-of-data-warehousing-in-the-aws-cloud-cd31638c26e0?source=rss-f3440935c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd31638c26e0</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Michael David Cobb Bowen]]></dc:creator>
            <pubDate>Tue, 04 Feb 2020 19:31:43 GMT</pubDate>
            <atom:updated>2020-02-04T19:31:43.325Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/926/1*kqtRg-Ie8EWMdShj9uJcEA.jpeg" /></figure><p>Our company has been designing cloud architectures for BI and Data Warehousing for a decade in the Amazon cloud. There are several new features we have been implementing over the past several years at my firm as we evolve our own expertise in satisfying our customers. Allow me to share them with you.</p><p><strong>Cloud Implementation of Big / Fast / Wide</strong><br>The first thing we did back in 2012 was get our hands on <strong>Vertica</strong>, the commercialization of Michael Stonebraker’s <a href="http://db.lcs.mit.edu/projects/cstore/">C-Store</a> project at MIT. At the time, Vertica was on version 4 or 5, I forget which. What I do remember was that when we got the multi-node clusters working up on AWS it was a breakthrough. This was before Snowflake. This was before Redshift. So we were learning denormalized models. At the time people were asking what is ‘big data’ and our definition has roughly centered around the idea that big data means that you regularly make sets of transforms or transactions that you cannot really test before hand, and tend to be expensive if you have to do them a second time.</p><p>But more important to us and to our customers was Wide. This means you can integrate multiple DW applications and have more than 256 columns of data — no more horizontal partitioning of fact tables and data models. (Vertica can handily do 4500 columns wide). This was the basis of a lot of new integrations we did.</p><p>Fast was important as well. Most financial DWs were only refreshing MTD data on a nightly basis. We got workloads that were continuous and updated the DW continuously. All under nice control.</p><p><strong>Producer Ingestor Transformer<br>T</strong>he next thing we did, learning from the Fast innovations, was that we could have continual idempotent processes running against the DW from any number of streams. Breaking up these processes by leveraging AWS S3 allowed us to optimize each input stream by building its own <strong>Producer</strong>. For us, a Producer is a task that takes data from a source, does a small bit of cleansing and dumps that data into a standardized format.</p><p>An <strong>Ingestor</strong> is a process that moves data from the data store (S3) into the database as smartly and as efficiently as the DW can handle it. Since our Producers created a <a href="https://insight.full360.com/what-is-the-role-of-a-structured-data-lake-in-dw-cbc8682cc815">structured data lake</a> in the first place, the Ingestor can do restatements, incremental loads, or any special kind of update, merge or replacement we choose. Again, every different application will have different requirements.</p><p>A <strong>Transformer</strong> uses the power of a sharded multi-node database engine on giant AWS EC2 instances to use easily understandable SQL statements and make set transformations on data. Essentially any stored procedure is done in this manner, thus making the strategy of ELT rather than ETL.</p><p><strong>Containers &amp; Scale Out</strong><br>The next thing we did was to containerize our producers, ingestors and transformers. With this we added a great deal of monitoring of these processes through <strong>Cloudwatch</strong> and ultimately streamlined the process of development and deployment of these containers. We added service discovery with <strong>Consul</strong> for the database engine nodes. We invented <a href="https://www.youtube.com/watch?v=FWVI93hUtGM">SneaQL</a> to create the conditional executions in ANSI standard SQL. We stored this SQL separate from the database as we iterated over best practices. It made working with containers less cumbersome in our CI/CD process.</p><p>Launching our producers, consumers and ingestors in Amazon’s Elastic Container Service (ECS) paved the way for us to scale out horizontally and provide high availability for all of the data streams we manage.</p><p><strong>Multitier Database Architecture</strong><br>One of the things we quickly learned, especially in dealing with website backends, is that a lot of data is provided via APIs and NoSQL sources like <strong>Hadoop</strong>. Also, there are a large number of transactional data that is best handled in-memory with tech like <strong>Redis</strong> or <strong>VoltDB</strong>. Our work with online gaming companies showed that our DW architecture was flexible enough to orchestrate data workloads for complex applications. So once we mastered Producers and Consumers (a consumer is an ingestor &amp; transformer in one) we discovered we could publish and subscribe to everything our customers wanted. This paved the way for our latest innovative practices.</p><p><strong>Plug &amp; Play Data Engineering </strong><br>One of the things we have been able to learn in our history of building on our <strong>PITbull Framework</strong> (Producer Ingestor Transformer) is what languages work best. Our engineers have had the opportunity to learn the AKKA framework in <strong>Scala</strong>. We build a DSL (domain specific language) in Ruby for our first producers, then went to <strong>JRuby</strong> to run faster. We have worked in <strong>Python</strong> for our Lambdas. We are now closing ranks around <strong>Go.</strong></p><p>Let me say something about Lambdas, although it wasn’t automatic, using ECS prepared us for serverless <strong>Fargate</strong>. We don’t necessarily build for serverless just to say that we do, we go about it on a case by case basis. Some more complex tasks simply don’t make sense and the economics of serverless processing can vary widely depending on how you code and how smartly you benchmark performance.</p><p>New technologies are evolving all of the time. That includes Redshift and technologies like Athena and Redshift Spectrum. <strong>Apache Spark</strong> has a big role to play. Recently we have mastered the art of horizontal scale out for <strong>Tableau</strong> servers running on AWS. But the fundamental architectural discipline we have makes the applications we build very close to future-proof. We started off being vendor agnostic and it has served our customers well, in addition to making our staff more well-rounded.</p><p><strong>On the Horizon</strong><br>We are very proud of an <strong>AI</strong> (using TensorFlow) application we have developed for the airline industry. We will be publishing more about that in 2020. What makes me particularly excited are two big things that I think are going to revolutionize the industry.</p><p>The first is <strong>Apache Beam</strong>. After all I have learned in the past 25 years in this industry, this is probably the most revolutionary framework to come about. Ever time I take an hour or two to study up, I come away more impressed. If you haven’t heard about it, check it out. Basically it sets in theory what we learned in practice — batch processing is just another form of stream processing and all data applications are about managing streams. Streams with different temporalities for different purposes.</p><p>That is why I am convinced that <strong>Kafka</strong> is a large part of the future of Data Warehousing. I believe we will be replacing the databases in certain applications with streaming services like Kafka and Kinesis. The kind of data objects we serve in those streams will be very interesting indeed. So bone up message buses and KSQL. It’s the future.</p><p><strong>In Summary &amp; Predictions</strong><br>We have learned a great deal about what DW can do when it is architected in the cloud and subjected to the disciplines of DevOps. Our applications are more highly available, easier to maintain and expand, more interoperable and vendor independent, more secure and capable of handling more diverse loads and types of data. Infrastructure as code had demonstrated to us that we can quickly standup DWs. VLDB has become a great deal more inexpensive and approachable.</p><p>So I’ll predict, after the discontinuation of Netezza by IBM (we do migrations), that Teradata is not long for this earth. Also the popularity of Postgres combined with the logic of SneaQL and the reliability of RDS is going to gut Oracle in the DW space. MySQL is officially a toy. Says me.</p><p>I’ve heard rumors that GCP is under threat from Google to rapidly gain market share. I think that’s something of an impossible task and I hope they don’t go away. Amazon and Microsoft are not a good duopoly — we need Google in this cloud space. I don’t believe that hybrid clouds are a really safe place to be long-term.</p><p>I expect a shakeout in the data science boom, and I reiterate what I’ve always said. The tools will make data science easier and easier. It’s not about the tools; the real value is in knowing an industry in depth.</p><p>The future is bright. The frameworks are evolving. The tools will get easier to use. Custom data applications that are industry specific is the way to go. Multi-tier streaming, storage and querying is the future. Never forget <a href="http://www.principles-wiki.net/principles:gall_s_law">Gall’s Law</a>.</p><p>One more observation tangential to DW. That is decentralization of data and blockchain. My rule of thumb with regard to organizations is clear. “Decentralize until it hurts, then centralize until it works.” But there’s going to be a lot of work involved with rearchitecting all data collection to be GDPR and CCPA compliant. So I would focus more on making centralized PII data more manageable and guarantee such compliance before pushing data out into the boonies. The secret message is to think about what kind of data objects you can stream in a Kafkaesque data environment.</p><p>We continue to innovate for our customers. We are fortunate in our position as a managed service provider to keep our platform up to date. We are especially lucky that our customers and partners keep challenging us to do more. Stay tuned.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd31638c26e0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/full360/the-evolution-of-data-warehousing-in-the-aws-cloud-cd31638c26e0">The Evolution of Data Warehousing in the AWS Cloud</a> was originally published in <a href="https://medium.com/full360">Full 360 (A Micro Focus Company)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five Simple Secrets for Running Virtual Teams]]></title>
            <link>https://medium.com/full360/five-simple-secrets-for-running-virtual-teams-7609ac469923?source=rss-f3440935c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/7609ac469923</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Michael David Cobb Bowen]]></dc:creator>
            <pubDate>Fri, 24 Jan 2020 18:30:23 GMT</pubDate>
            <atom:updated>2020-01-24T18:30:49.992Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0EgGfD7mJ02SnCzBYDKsIw.jpeg" /></figure><p>I work for a cool company that got rid of its NYC office the year I joined. From that moment forward, everybody in the company of a couple dozen people worked from home. Not just in the US, but in Australia and South America as well as Europe. How we have managed to stay strong and focused as an organization took a bit of experimentation, but we think we’ve found a formula that works. I’m now entering my 10th year. Here’s what we learned.</p><p>Ironically, the first step to success in running a strong virtual team is done <strong>face to face</strong>. You must have a company-wide function. We call it an IRL (for In Real Life). At an IRL you establish social connections face to face. If you don’t do this at least once a year, your virtual team can collapse or just become abstracted. In other words, you need to establish leadership and camaraderie in person, just like every other business. Every IRL I attend, I learn something new about people I’ve known for years. There’s something, dare I say it, magical about physical companionship. Even something as simple as seeing how somebody walks is valuable in filling out a depth of empathy. After all empathy is the key to <em>wanting</em> to make your team work well.</p><p>Secondly, you need to settle on <strong>standard collaboration tools</strong>. Nothing can undermine a virtual team like using WeChat for three months then changing to Slack, then changing to something else. Of course you need to learn by trying alternatives, but sooner or later the standard needs to get written in stone. Counterintuitively, you need to pay more attention to the downsides of such a tool than the advantages. What we have learned is that it’s a great deal more important for virtual teams to <em>like</em> using the collaborative tools. If five people say an application is ‘meh’, that’s better than three loving it and two hating it. When you run a virtual team there is not likely to be a sneakernet alternative. If employees don’t like it, the work won’t get done. Or it will get done in a silo. I’ll review the tools we have decided and our evolutions in another post.</p><p>Thirdly, you will want to have <strong>regular Town Hall meetings</strong>. These are a two or three hour meeting once a month where employees are invited to present and leadership gives detailed updates on the state of the company. Also some fraction of that meeting needs to be completely personal. What’s new in your life, etc. Basic kinds of social media questions are perfect. “Name 3 things about yourself that almost nobody knows.” Our Town Halls are run at a leisurely pace. It is more important that we spend the time together than rush through the agenda. As we have become used to Town Halls, people are more willing to speak up in front of the whole company even on controversial subjects. In this regard, bad news is good news because we don’t become passive-aggressive in our communications.</p><p>Fourthly, you need to have <strong>weekly standups / status meetings</strong> where the progress of projects and all other to-dos are aired in the departments. Take 90 minutes and get into the weeds. Have a Done / Not Done pass. No excuses or explanations, just say the task and whether or not it was done. Next pass you talk about your week. Third pass you talk about what’s on the next week’s agenda and the priorities. Finally you take issues that are outstanding and you setup sessions to deal with them. Every Friday is judgment day. Prepare for it, have no excuses.</p><p>Finally, you must have a <strong>knowledgebase</strong>. No matter how well you communicate immediately and on regular schedules, there needs to be a place where all of the ‘been there, learned that’ gets recorded. I think Confluence is both a good and a bad tool, but it is the very least you should do. Runbooks, policies and procedures, onboarding notes, formal communications. There is really no end to the kinds of documents that should be easily available to your teams. Remember that TL;DR is the enemy. These should be as comprehensive and complete as is possible. But also remember that things should be easy to find. Don’t bury things deep in hierarchies. Ironcially the search function on your knowledgebase may not work as well as those on the internet.</p><p>These channels of collaboration allow us to communicate in different contexts. Over time, we learned where to prioritize and the place to put information so that organization becomes more clear. Sometimes a single post is enough. Sometimes things should be broadcast, communicated through multiple channels and followed up as well. With these fundamentals you should be well on your way — but remember they will only work as your team agrees to use them, and of course different members of the team will their own styles. Stiil, you must insist on this kind of conformity. If people are still sending emails and you have decided on Slack, copy and paste the email into Slack until they get the message. Iterate through the process and gently remind people to keep doing it. Your virtual team will feel much more responsive and at home.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7609ac469923" width="1" height="1" alt=""><hr><p><a href="https://medium.com/full360/five-simple-secrets-for-running-virtual-teams-7609ac469923">Five Simple Secrets for Running Virtual Teams</a> was originally published in <a href="https://medium.com/full360">Full 360 (A Micro Focus Company)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starting and Growing a BI Department from Scratch]]></title>
            <link>https://medium.com/full360/starting-and-growing-a-bi-department-from-scratch-f44c63c328c5?source=rss-f3440935c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f44c63c328c5</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[business-intelligence]]></category>
            <dc:creator><![CDATA[Michael David Cobb Bowen]]></dc:creator>
            <pubDate>Wed, 08 Jan 2020 21:30:33 GMT</pubDate>
            <atom:updated>2020-01-08T21:30:33.854Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*k-GSx2FE1Zevtq1Ig2t7Sw.png" /></figure><p>Sometimes we fall into opportunities that allow us to start fresh. Not much could be better in that regard than beginning and growing a new business intelligence function in your company. I’ve learned a lot of lessons over the years. Here’s my advice.</p><p>Make sure your company can settle on one front-end tool. This is crucial. You should start simple — something that everyone can use with minimal training and can read data from the most popular databases. I recommend Pentaho as an open source contender.</p><p>Hire two people and make sure they are cross-trained. One person is your front-end specialist who can also do requirements documentation. The other person is your business analyst who can also program the front end. Make sure they are both lovable people who over communicate. Make sure everybody knows them and trusts them. You focus on the backend (assuming that you are the most technically proficient). That means you do DBA work + database design work. You build all of the ETL and you learn every data source in your company.</p><p>Your business analyst will start brainstorming what the various departments want in order to provide direction before they become requirements. The business systems analyst should know the roadmap to building what comes next. This person is responsible not only for requirements, but training and testing. Their reputation depends on delivering exactly what the customer asked for. Insure that every application has a release schedule and make hard calls about what’s in next and what’s pushed back.</p><p>My experience tells me that very few departments, even those hungry for data will hire full time systems analysts who will keep up with tech and implementation methodology. It might be controversial, but I say the systems analysts should stay with the tech team.</p><p>Your front-end specialist should know every trick in the book when it comes to changing fonts, colors, charts, pull-downs, filters, sql, writeback and securing reports for different groups. Give the people what they want. Make sure that when they navigate the system that they never get lost. Give the customers two or three ways to see the same thing, but ultimately narrow them down to one view.</p><p>You / your backend specialist should get the most powerful servers, the most capacious backup, the most comprehensive language (well, bash + Python and/or Go) to run your data management. Refine data designs and create alerts and alarms for when data that should be there doesn’t get there. You should know that your sources are failing before your customers (or at least within the first five minutes).</p><p>These are the three primary skillsets for a good BI department. You should be able to master them in 2 years starting from scratch.</p><p>The toughest question you will ever answer is “What were we thinking?” two years after an application was built. If you can answer that easily and get the same answer from both your department and the customers, you’re doing it right.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f44c63c328c5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/full360/starting-and-growing-a-bi-department-from-scratch-f44c63c328c5">Starting and Growing a BI Department from Scratch</a> was originally published in <a href="https://medium.com/full360">Full 360 (A Micro Focus Company)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Citizenship & The Lost Report Card]]></title>
            <link>https://mdcbowen.medium.com/citizenship-the-lost-report-card-a1d1448916a2?source=rss-f3440935c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1d1448916a2</guid>
            <category><![CDATA[ethics]]></category>
            <category><![CDATA[values]]></category>
            <category><![CDATA[character]]></category>
            <category><![CDATA[citizenship]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Michael David Cobb Bowen]]></dc:creator>
            <pubDate>Sun, 10 Nov 2019 21:33:00 GMT</pubDate>
            <atom:updated>2019-11-10T21:38:28.925Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*5kbOhMbGPFQ_eiNz" /></figure><p>It occurred to me this morning that when I was a kid in elementary school that we used to be graded on a lot more than what we knew, but how we behaved. ‘Makes good use of time’ was the one where I always needed to improve. That’s because I was a smart-ass, finished my work early, got bored and started daydreaming. Well, that and I’m lazy. But I know this, because I was graded on it. And with all the ruckus going on over the complete breakdown in trust and authority all over it’s rather interesting what solutions are being proposed.</p><p>Now naturally since we’re Americans and we like to congratulate ourselves in our ability to make something (rather than just nothing) out of race, there’s a game afoot telling white people how they ought to think and behave and telling black people how they ought to think and behave. The ignorant assumption of course is that you add up all the diversity numbers and it will work out remainder zero. Except we’re supposed to be indivisible with liberty and justice for all, but everybody keeps saying that diversity is the solution.</p><p><strong>You can’t have diversity without division. The opposite of diversity is conformity.</strong></p><p>So that means you have to teach everybody the same thing and hold everybody to the same standard of behavior. Hey wait a minute — that’s what public school is supposed to be about, right? That’s why we had the Brown Decision to get us all in the same schools. But what if they didn’t teach anybody how to behave? Hmm.</p><p>I specifically remember that as time went by in elementary school, the Citizenship &amp; Work Habits side of the report card got smaller and smaller. The public middle schools basically reduced them to one line for each class you attended. What did you get in math? B, S, S? What exactly does an ‘S’ in Citizenship mean? Basically nothing. Hell, I wonder if they even use the word ‘citizenship’ here in Los Angeles for fear of insulting our Mexican national neighborhood residents. So I googled around to see if I could find any old school report cards. Not from LA Unified School District, but I did find some remarkable images.</p><p>I find it almost impossible to believe that any public school in America would consider such a detailed and rigorous evaluation of the character of children. It seems almost unthinkable. I mean look at this. ‘Treats members of the visiting team with hospitality”. “Shares good times with others whenever possible”. “Subordinates his own will to the larger purposes and ideals of life.” These are things we all know to be essential to good character These are all virtues we acknowledge. So why on earth do we not teach them to children? What was the breaking point? When did GPA and test scores become more important than anything else?</p><p>Now I attended Catholic middle school and high school and measures of character, as well as discipline for lapses in character were all part and parcel of the spirit of belonging to the school. One sought to bring honor and respect to one’s school by exemplifying virtue in all these ways. And I know all of my small ‘a’ atheist pals out there can’t seem to find a way to understand how you can teach virtuous citizenship without summary intimidation and invocation of fire and brimstone from an ‘imaginary’ supreme being, but I guess they forget that nuns and priests are people too. And people have different ways of inspiring and teaching to standards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*KpKS5qPgkUd45at8" /></figure><p>The point of course is to have standards and these are the kinds of standards I think too many Americans simply don’t feel beholden to. They think perhaps that these are just optional — that you can function perfectly well in society and the worse thing that’s going to happen to you is that somebody down the line is going to call you an ‘asshole’ or a ‘douchebag’. Other than that, it’s all whatever dude.</p><p>I am inclined to believe that whenever we get into ‘this conversation’ things get so far carried away into the identity troughs of ‘race, creed, color, ethnicity, physical ability, sexual preference, gender’ that people simply don’t have space in their brains for character. It must completely blow their minds to imagine that character might be measured in other terms than these fetishized diversity buckets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*Fx3NHZUqxngvea14" /></figure><p>It’s really hard to find in front of a paywall any sort of accounting for this set of measures. But I found a scanned copy from the Internet Archive. They are called the Upton-Chassell Scale and I have a copy for you.</p><p>Now on first glance this is clearly a mix in importance. The author is quick to point out.</p><p><em>It is interesting to note in Chart I, for example, that it is the consensus of opinion that a habit such as “Puts on or removes wraps quickly,” listed on p. 22, is of trivial importance, since it is rated as i, and should, therefore, receive comparatively little attention from the teacher; while a habit like “Tells the truth without flinching or compromise, trying to give a correct impression,” given on p. 24, which is rated 10, is of primary importance and should be carefully considered when the teacher is making out the report card.</em></p><p>I often hear from people who begrudge conservatism its wisdom and other such folks whose motivations are opaque to me, that the benefit of all such things from the ‘olden days’ are negated owing to some inherent racist content or explicit racist implementation. So it would not surprise me in the least if at some point it were determined through some cockamamie finger-pointing posing as research, that white teachers were singularly unable to be consistent in their evaluations of non-white students when it came to these measures of character and citizenship. OK, let’s stipulate that to be the case for 1919 but that somehow through the magic of the Civil Rights Movement, that white people have been sufficiently re-educated to give this idea a second-chance. Why not? What have we got to lose? Wouldn’t you like to know this about public school students? Is there any situation in which these questions are inappropriate? I don’t think so. I think these are things that anyone would notice in children and indeed ought to notice.</p><p>I don’t have the complete set of these report card images but there is an extensive list of citizenship metrics in the document. So have at it.</p><p>Now while I’m at this let’s get an idea of whom exactly this Horace Mann character was, since there appears to be something to the fact that much of this reporting by Upton and Chassell was done at Horace Mann Elementary School. The great and powerful Wikipedia says this of Mann’s Congressional career:</p><p><em>In the spring of 1848 he was elected to the </em><a href="https://en.wikipedia.org/wiki/United_States_Congress"><em>United States Congress</em></a><em> as a </em><a href="https://en.wikipedia.org/wiki/Whig_party_(United_States)"><em>Whig</em></a><em>, to fill the vacancy caused by the death of </em><a href="https://en.wikipedia.org/wiki/John_Quincy_Adams"><em>John Quincy Adams</em></a><em>. His first speech in that body was in advocacy of its right and duty to exclude </em><a href="https://en.wikipedia.org/wiki/Slavery"><em>slavery</em></a><em> from the territories, and in a letter in December of that year he said: “I think the country is to experience serious times. Interference with slavery will excite civil commotion in the South. But it is best to interfere. Now is the time to see whether the Union is a rope of sand or a band of steel.” Again he said: “I consider no evil as great as slavery, and I would pass the </em><a href="https://en.wikipedia.org/wiki/Wilmot_Proviso"><em>Wilmot Proviso</em></a><em> whether the South rebel or not.” During the first session, he volunteered as counsel for </em><a href="https://en.wikipedia.org/wiki/Pearl_incident"><em>Drayton and Sayres</em></a><em>, who were indicted for stealing 76 slaves in the </em><a href="https://en.wikipedia.org/wiki/District_of_Columbia"><em>District of Columbia</em></a><em>, and at the trial was engaged for 21 successive days in their defense. In 1850, he was engaged in a controversy with </em><a href="https://en.wikipedia.org/wiki/Daniel_Webster"><em>Daniel Webster</em></a><em> in regard to the extension of slavery and the </em><a href="https://en.wikipedia.org/wiki/Fugitive_Slave_Law"><em>Fugitive Slave Law</em></a><em>. Mann was defeated by a single vote at the ensuing nominating convention by Webster’s supporters; but, on appealing to the people as an independent anti-slavery candidate, he was re-elected, serving from April 1848 until March 1853.</em></p><p>Well that ain’t hay. But wait, look at that last measure of character. “Recognizes moral purpose in the universe, and reverences a Higher Power”. Geez, I dunno. Could we even have such a question posed of our children here in America? Leaving that nit to be picked by such people as find it appealing let us review then, the top categories from <a href="https://www.evernote.com/shard/s6/sh/95ae6a81-c76d-4093-897f-26723d8d1ca8/3b292be8b222302c2b2f962d9340d5ce">the Upton-Chassell document</a>.</p><ul><li>Takes Care of His Health.</li><li>Keeps a Good posture.</li><li>Is Orderly</li><li>Exercises Thrift.</li><li>Is Prompt.</li><li>Thinks Clearly and Purposefully</li><li>Has a Sense of Humor</li><li>Is Refined</li><li>Is Characterized by Helpful Initiative</li><li>Is Self-Reliant</li><li>Exercises Self-Control</li><li>Lives up to the Traditions of Sportsmanship</li><li>Stands for Fair Play</li><li>Is Courageous</li><li>Is Honest and Truthful</li><li>Is Trustworthy</li><li>Has a Sense of Civic Responsibility</li><li>Is Obedient</li><li>Is Generous</li><li>Is Courteous and Considerate</li><li>Is Cooperative</li><li>Is Broadminded</li><li>Is Loyal</li><li>Has a Fine Sense of Appreciation and Seeks to Express It.</li></ul><p>Character counts. So why do we not count character?</p><p><em>Originally published at </em><a href="https://cobb.typepad.com/cobb/2014/08/citizenship-the-lost-report-card.html"><em>https://cobb.typepad.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1d1448916a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>