Tuesday, September 22, 2009

Orientation Weekend


Its already been one month since school started, but I want to tell you about Orientation Weekend, which kick-started my program at Carnegie Mellon.

It started Friday morning, at NASA Research Park in Mountain View, California, where I met my new classmates, faculty and team in Carnegie Mellon. The collaborative experience of being a part of a team-building process was exciting beyond my expectations.

Abby, my girlfriend, wished me luck as I left home Friday morning for an early drive down to CMU. After a 40 minute drive from San Bruno to Mountain View, I was ready to show the NASA security my passport. They said I only needed a driver's license. Inside, I expected things to look a little more impressive. Besides a gigantic hangar bay, everything else as far as I could see looked like a suburban university campus.

I pulled up at the Building 23 and went inside. About 50 other students had already arrived, sipping on coffee and having breakfast. It felt like a new company info session. The agenda was funny: A few talks here and there, followed by playing with Legos and some catered lunches. I could already sense where some of the pricey tuition was being spent.

A few hours later, something magical had happened. After a few conversations encouraged among the students, there was a very positive air filling the room. We were still slowly discovering our purpose in that room, but we all knew we were going to leave with something more than we came with at the end of that weekend.

Overall, we spent about 24 hours together that weekend. About 30% of the students were remote and had to fly back to their homes and families on Sunday. The part-time program allows remote collaboration as a way of participating in the program. The Lego game had been a way of discovering our own weaknesses when acting as a part of a team: things slow down, but end well after a few tries.

The events of those 24 hours were way too many for me to talk about in this blog post. Bill Portelli, the CEO of CollabNet gave us a talk. Dr. Martin Griss, the director of the Silicon Valley campus, had us playing with Legos. We went out to the Castro street of Mountain View for dinner with the faculty. I ended up having a few pints of beer with Dr. Stuart Evans, when our group went to the Tied House Brewery to celebrate the first night. He had just returned from England and I started chatting with him about my brief trip in London and Edinburgh. To my surprise, he was very knowledgeable about Persian culture, even compared to the average Iranian. Just when I was fascinated by his friendliness, charming English accent and exciting background with entrepreneurship and high-tech startups, he started talking about Hassanloo village, an archeologically significant site in Iran. He seemed to know a lot about the food and culture, and a few things about the language as well. I know that my family and most of my friends would describe running into someone that knowledgeable quite a rare experience. At the end of the night, I couldn't be any happier to be looking forward to my first course that he teaches: Elements of Software Management.

The experiences of this weekend were too overwhelming for me to reflect on in just a few paragraphs. But the big observation I made when it comes to your personal growth is that no matter what the cost is in time and money, just do it. You live only once!

Friday, September 18, 2009

Introducing Amin Ariana


Hi, and welcome to my blog. My name is Amin. I'm hoping to share some of my experiences here at Carnegie Mellon with you through my future writing.

More about me: I'm an Iranian-Canadian. I immigrated to Canada when I was 17 with a strong background in Math and programming. I received my bachelors in Computer Science with a minor in Psychology from University of Waterloo. Very early on, in my first year of college, I found myself to be somewhat of an entrepreneur. I learned how to write database and UI code from the scattered knowledge of a few friends. I wrote a Social Networking that I named "darxtudio.com" back in 1999. It had forums, photo sharing and user profiles. I signed up 150 of my friends, but didn't have enough skills at the time to scale it.

Since graduation I have worked at various companies either as a consultant or a software engineer. Two months before I started my graduate program in Software Management at Carnegie Mellon Silicon Valley, I was still a Software Design Engineer at Microsoft in Redmond. I was thinking about taking the next step in my career, but wasn't quite sure what it would look like. I contacted a few universities, such as Harvard, Stanford, CMU and Berkeley, for more information about their programs. About 30 days before the very last admission deadline, Dr. Jim Morris from Carnegie Mellon called me on the phone. I was very pleasantly surprised to be contacted by someone whose textbook-standard search algorithm I had studied in college. He encouraged me to apply, and my mind was already set.

I got over my procrastination and finally wrote the GMAT exam, very successfully despite my apprehention and the very short notice. My advice: "Don't be nervous. Just do it. Now! Start with the online practice exam."

At the same time, I started listening to the other voices in my head. I applied to a few startups in Silicon Valley and before hearing back from Carnegie Mellon, had an offer from Adify. Moving to California isn't a requirement of the program, but I wanted to make the commitment an integral part of my next two years. You may be wondering if everybody in this program is financially supported by their employer. I'm not, because of the transition. And I'm proud of the fact that I'm supporting myself in my personal and career growth. I'm a firm believer that if you put growth first, success will follow.

I have a lot more to share with you, but I need to manage my time to attend to my job and studying duties as well. One major skill you learn in this program is how to be successful at playing multiple roles. On that note, please come back to read more of my writings later.

Just remember: You start going forward only when you take the first step.

-Amin

Friday, May 1, 2009

Project and Process Management - Wrapping it Up!


For our final assignment in the Project and Process Management class, our team was called on to consider our response to a scenario in which the fictional company described in the second assignment had started down the project execution path and had encountered some difficulties. We assessed the project status, revised the resource, cost and schedule estimates, and recommended actions to improve the project’s chances of success.

Key elements of this assignment including recognizing the project issues and their impact, determining their cause, considering the lessons learned, and formulating recommendations. Among the lessons we learned were that hiring and getting a new project team up and running can take longer than expected.

Much of our learning and in-depth analysis on this assignment came near the end of the week in which it was due. We had to get to the point of fully characterizing the whole set of issues in order to craft a response that tied together. Building on the collaborative strengths we developed on the second assignment, team members could comfortably ask each other for help and benefit from the various perspectives that each one of us offered. The report went through multiple stages of refinement before we were satisfied with it. This project incorporated significant contributions from each team member and reinforced both our learning to work as a team and our application of the course’s core principles in a business setting.

Wednesday, April 1, 2009

Project and Process Management - Midway through


For the next assignment in our Project and Process Management class, our team delivered a presentation recommending a specific software methodology to the Vice President of Engineering of a fictional company. Included in the presentation were the evaluation method for selecting the methodology, refinements to the process, estimates of schedule, budget and resource, assessment of risks, and recommended action.

Our team worked on the underlying content for this presentation over several weeks. We allocated the work among ourselves in order to work in parallel and provide opportunity for in-depth research. We explored alternative approaches and collaborated through frequent meetings and shared documents. In this period, our coach offered valuable insights about effectively positioning our content for senior management. In the third week of this assignment, we organized our conclusions into slides. Finally, we presented our findings to the senior management of this fictional company.

During this period, our team members learned from each other. Our team meetings gradually became more effective, and we leveraged each others’ strengths to organize a high quality presentation. The learning that took place on this task came from our growing as a team, from applying the academic principles in a business setting, and from framing our findings for a senior management audience.

Friday, February 20, 2009

Project and Process Management Class


The third course in the Software Management program is the Project and Process Management class. This course addresses software development processes in the context of Agile and traditional methods.

In the first three weeks, each team in the class researched and reported on a different process within the software development lifecycle. The teams then shared their conclusions with the other teams and responded to questions.

Learning was enabled in many ways. As individuals, students researched their designated areas, provided input to their team’s report, and shared in the authorship of the final deliverable. Within a given team, the process of collaborative research and writing created the environment in which team members learned from each other about the various aspects of the software process about which the team was writing. The sharing of conclusions across the teams enabled all of the teams to understand the end-to-end software development lifecycle. The feedback cycle of questions and answers among the teams allowed all of us to see how others viewed our work.

Our next assignment called on teams to apply the newly gained software development process knowledge in the context of the needs of a specific company’s development opportunity. I’ll discuss that in my next entry.

Friday, January 23, 2009

Finishing Up Metrics for Software Managers


In this entry, I’ll explain my reflections on the Metrics for Software Managers class.

The Masters in Software Management Program is built on the principles of problem-based learning. In the Metrics for Software Managers class, teams apply these principles by using academic concepts to address business problems. Through this experience, we learn to work as a team.

In the process of developing multiple team deliverables, team members begin to recognize that we bring in different perspectives and need to work out approaches for creating a unified deliverable. We are called on to utilize listening and communication skills in order to ensure that each team member’s ideas are considered.

When we give feedback on the proposals of other teams, and when we receive their feedback, we often learn that we have characterized the problems and solutions in very different ways. Similarly, our formal presentations of our proposals may differ significantly and represent a diverse set of approaches. The lessons learned from the experiences of working both as a team and across teams enable us to reframe our approach to problem solving.

Finally, the principles of change management that form the foundation of the final major assignment are directly applicable to many aspects of our work now and in the future. In the dynamic workplaces of today, change is the norm. A thoughtful understanding of change management principles will enable us to help our organization respond to the evolving context.

Wednesday, January 7, 2009

The Team's Learning Process


In this entry, I’ll explain our team’s learning processes in the Metrics for Software Managers class.

The primary course deliverables were developed in the context of our assigned teams. Early in the course our team learned to build on each others’ strengths, while also establishing a structure that enabled a rotation of key roles among team members for the various tasks. To complete our team deliverables required that we learn about team problem solving. This involved developing a shared understanding of both the stated problems and the associated principles of metrics, software management and change management.

Each of us had an opportunity to formally present part of our team’s proposal to our class. In some cases these presentations encompassed independent research that provided additional insight into core principles. Attending and discussing the presentations gave all of us the opportunity to learn from other teams’ approaches to the assignment and to hear other teams’ reactions to our proposals.

One aspect of the feedback loop entailed each student providing written feedback on the proposals of two other teams for each major assignment. This was a new experience for some of us and called on us to characterize these proposals in ways that would help the other teams learn. We also learned from the feedback given to us.

In my final entry, I’ll share my own learning reflections on this class.