So, regardless of whether a change is imposed by the management of an organization, is requested by and driven by those most affected by the change, or any combination of both, the fundamental mathematics remain the same.
As a newbie to R I wanted to look at the source code of some of the libraries/packages that I’d installed via R Studio which I initially struggled to do as I wasn’t sure where the packages had been installed.
This week, DZone released its latest Refcard: Getting Started with Play Framework. If you're interested in learning more about the Play Framework or sharpening your skills, we decided to dig into the DZone archives and find some of the most popular posts we've had on the topic.
People aren’t resources! People finish work. If you don’t want us to finish projects, let’s decide which projects not to do. Then we can re-allocate people, if we want. But we don’t start with people. That’s crazy.
User stories are a powerful technique to capture the product functionality from the perspective of a user or customer. But how do we discover the right stories? When should they be written and how detailed should they be? Read this post to find out my answers to these questions.
Networking is a visual field. In fact, we can generalize and say all of IT is. Come to think of it, is there a technical field that isn’t? In this post, I’ll cover a handful of visualization tools that have recently helped me think through and communicate difficult Network Engineering stuff.
I’ve seen exhortations to think like Leonardo da Vinci or Albert Einstein, but these leave me cold. I can’t imagine thinking like either of these men. But here are a few famous computer scientists I could imagine emulating when trying to solve a problem. What would you add to the list?
I posted my slides for my Agile 2014 talk, Agile Projects, Program & Portfolio Management: No Air Quotes Required on Slideshare. It’s a bootcamp talk, so the majority of the talk is making sure that people understand the basics about projects. Walk before you run. That part.
During retrospection, when evaluating the quality and value of our artifacts for Epic, Feature and Story decomposition a common theme for our scrum teams is that these artifacts are by design barely sufficient and as such are ephemeral and provide no enduring value.
I like this system because I find the visual aspect very important. It gives me a sense of accomplishment, which I value. Since most of what I do is creative work, fighting procrastination and “resistance” is high on my list of priorities, and visual tools help me with that.
In my continued playing around with R and meetup data I wanted to group a data table by two variables – day and event – so I could see the most popular day of the week for meetups and which events we’d held on those days.