This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Develop architectural values and principles - What Ive described here is very systematic and process driven, but may not work all the time for smaller teams on aggressive time schedules. Teams need some basic guidelines, values, or principles that will help them make appropriate architecture decisions without a lot of overhead.
So in thinking about this transformation, here are some simple questions and guidelines on where to focus efforts. The bigger the data, the more likely you will need to look at infrastructure to store, process, and manage larger data sets. agile software development. (56). crisis management. (3). it management. (34).
Labels: big data , cio , data management , data scientist , it management , microsoft. 1 comment: Isaac Sacolick 7:14 AM MS Access Post from 2003: Beware the Rogue ASP Our guideline is to not use Access for more than analysis, but unfortunately, people will take 'analysis' and stretch that," the CIO says.
Will you make all projects follow an agile practice, or will you set guidelines on when to use agile vs. other practices? Labels: agile software development , cio , it management , organizational change , product management , projectmanagement , software development. crisis management. (3).
Earlier this year, I posted, CIO Advice: Listen, Answer The Question, Provide Insights to provide CIOs (and really all executives and managers) some basic advice on how to respond to questions from senior executives. This post follows up with some basic guidelines on creating presentations for CIOs and other senior executives.
We organize all of the trending information in your field so you don't have to. Join 83,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content