Home
04 | 09 | 2010
Notizie flash

IBM has opened a business analytics center in London to focus on services for the U.K.'s financial sector, which drives a major portion of the nation's economy. IBM said the center's initial focus will be on tracking risk positions across markets and assets classes.

IT Project Management
Sviluppo di una vision PDF Print E-mail
Written by Administrator   
Monday, 01 February 2010 17:27
There are no translations available.

Questo articolo idealmente continua l'articolo in cui trattavo i punti di attenzione principali quando si cambia ambiente di lavoro, ma lo specifica al caso in cui ci venga assegnato un team di professionisti IT. Qui vorrei trattare dell'importanza della creazione di una vision, un'idea, un punto di arrivo che ci indichi che cosa si vuole raggiungere con questo team.

Non vorrei sembrare americano o banalizzare troppo il concetto: la creazione di una propria vision è fondamentale e si tratta di un processo lungo che coinvolge sia aspetti personali (che cosa mi da la maggiore soddisfazione nel mio lavoro) che aspetti professionali (dove voglio arrivare). In aggiunta, tale processo non è statico, ma nell'evoluzione della carriera è soggetto a dei cambiamenti come reazione ad stimoli o semplicemente a una crescita personale.

La propria vision deve essere frutto di una riflessione personale, che ci costruiamo durante e a seguito dell'analisi della situazione in cui lavoreremo.

Ma ciò non basta. La propria idea di cosa si sarà “da grandi” deve essere condivisa dal gruppo di lavoro e (cosa difficile) non deve essere in contrasto con quella più generale dell'azienda. Per questo motivo alla fase di elaborazione personale deve seguire una fase di confronto prima con i propri superiori e poi con i propri collaboratori.

Una buona pratica può essere quella di discutere prima con i propri responsabile e poi tenere una o due sessioni di brainstorming, in modo da coinvolgere le persone e successivamente chiudere con decisioni e un impegno preciso a perseguire gli obiettivi.


( 0 Votes )
Last Updated on Thursday, 02 September 2010 12:02
 
Organizzazione di un team IT PDF Print E-mail
Written by Administrator   
Saturday, 06 February 2010 16:40
There are no translations available.

In questo articolo, che continua la serie degli articoli riferiti al cambio di lavoro/team/progetto, vorrei elencare una serie di azioni pratiche da valutare nel momento in cui si assume la guida di un nuovo team. Non mi sono concentrato sulle attività di pianificazione quanto sugli aspetti più soft, che si apprendono solo con l'esperienza.

L'articolo, per rimanere breve, si sviluppa come una check-list. Nel seguito, se necessario le varie tematiche saranno trattate in articoli singoli.

I contenuti sono orientati ad un team che deve sviluppare software, ma spero sarà possibile trarne spunti positivi anche per team coinvolti in altri campi.

  • Se siamo coinvolti in un progetto o ne dobbiamo assumere la responsabilità, cerchiamo di reperire tutte le informazioni possibili e soprattutto di verificare i contenuti del contratto (milestones, deliverables, SLA, exit criteria per il lavoro, aree di responsabilita ... ). Spesso infatti l'ignoranza di clausole o semplicemente di paragrafi del contratto porta a conseguenze disastrose.
  • Creiamo immediatamente un log delle attività/task da realizzare. Con un log di attività pregresse riusciamo subito ad avere una idea, magari imprecisa della situazione che stiamo affrontando. Un buon punto di partenza, di solito è il piano di lavoro (se esiste) ma anche le interviste con i membri del team o altri stakeholder (stando attenti a evitare di aggiungere deliverables che non sono nello scopo del progetto). Attenzione il piano di lavoro (o ancora meglio il project management plan) fa parte di una metodologia ben definita e deve sempre esistere, ma quello che dobbiamo fare qui è passare dalle attività presentate in un documento, a un controllo di cosa stiamo facendo e di cosa faremo a breve.
  • Definiamo gli obiettivi del nostro lavoro. Se siamo in assenza di piano di lavoro è importantissimo crearne uno. In caso contrario, data la vision e il backlog del lavoro, dovrebbe essere semplice definire gli obiettivi a breve e medio termine. Attenzione gli obiettivi dovranno essere documentati e accettati dal team e dai propri superiori.
    ( 0 Votes )
Last Updated on Monday, 08 February 2010 13:49
 
Maturity of an IT development group PDF Print E-mail
Written by Administrator   
Sunday, 06 December 2009 16:38

These are my point of attention to understand what is the "status of art" of a team/IT organization:

  • Project control and Planning
    • How do you do plan, do you follow any methodology?
    • What tools do you use when planning?
    • How do you perform project control?Are you using EVM (Earned Value Methodology)?
    • Are there common plans among team?
    • Does a time tracking system is on site?
    • Are there any formal milestones during the software lifecycle, where a phase is closed and a subsequent is opened?
      ( 0 Votes )
Last Updated on Thursday, 02 September 2010 10:21
 
Requirement Elicitation PDF Print E-mail
Written by Administrator   
Sunday, 20 December 2009 13:44

Following a list of some of the best elicitation techniques:

  • introspection: what would I want/need/desire if I were a user of the proposed system?
  • brainstorming: free association and generation of ideas for the proposed system
  • Post-It notes and white board: create, modify, group, and rearrange statements of needs and desires
  • paper prototypes: construct interfaces and operational scenarios.
  • questionnaires: which of the following features do you need/desire?
  • observation: watch people performing their work tasks
  • open-ended interviews: tell me how you would use the proposed system
  • focus groups: please tell us what you would want/need/desire in the proposed system
  • operational walkthroughs: development of scenarios by interacting with users (UML)
  • demonstrations: how to you like this interface? what should be added/removed/changed?
  • protocol analysis: document the tasks users perform and the features they would need in the proposed system
  • business case analysis: what features are needed to support the operations of our business?
  • JAD (joint application development) sessions: facilitated meetings with users
  • Work with the users: it is not always possible, but this technique gives the best result

( 0 Votes )
Last Updated on Wednesday, 01 September 2010 11:56
 
Start smoothly and profitably a new work PDF Print E-mail
Written by Administrator   
Saturday, 05 December 2009 17:33

In this article i gathered together a number of point of attention that I built when I was passing from one client to another. The final scope is giving a track of how to be fast in adapting to the new reality and to build a good reputation for the continuing of the work.

There will be two articles. In this article I will suggest my ideas about how to make a good impression and build a strong reputation that you will use for the next actions. In the next article I will propose an approach when entering in an IT organization.

Coming to the steps.

1) Gather data on the company and prepare yourself

The first step starts even before entering into the company and it consists in self preparation and in gathering as much data and impression as possible about the company. It is important to understand early the key points and what the best way to satisfy them is:

  • what are the company strategies
  • what are the objectives perceived from outside?
  • what are the problems the company is going trough?
  • what are the priorities of the company, with regard to our future role?

In order to do this we will have to:

  • Read everything that is possible to find about strategy, structure, performances and people (for this linkedin is usually a really good resource).
  • Find about outlook on performances of the firm. This is quite important because it gives ideas of how the company is perceived from the outside.
  • Look for people who know well the company. For example former employees and clients. Try to discuss with these persons about their idea on the company. If possible speack with the person which we are going to substitute
  • Speak with the new boss.
  • Prepare a list of topics to dig more once we will start working

At this point we must investigate the operational environment and functional domains that we will encounter. Since we are still not fully engaged, this is a good moment to find any lack in our preparation and to close it. My personal suggestion is to review our managerial abilities, maybe going trough a self-assessment in order to understand where we need improvement. Usually is a good practice to review subjects on team management and some to read some books about trasiction from one role to another.

In the case of IT role, I would suggest to strenghten the following:

  • Software engineering, with particular care to estimations and development methods
  • Itil and COBIT
  • "lean" concepts
  • Outsourging and IT services
  • New instruments and tools.

2) Define the objectives with our future boss

Before starting a new job or collaboration, we need to have clear what is expected from us and what is the strategy of the company that we are joining:

  • What the long term and short term objectives are?
  • What the strategies to pursue such objectives are?

It is important that our future boss will clarify these questions, so that we can compare these information with the ones we already gathered in the firt phase. To understand the objectives and strategy will enable us to discuss the other more important:

  • What my long term objectives are? What the short term?
  • Who will be my stakeholders, (i.e. the people that will have interest in the result of my work)? It is really important to clarify this aspect since it will drive us to identify the groups which we need to take care.
  • What will be my position in the organization?
  • Who will be the responsible for my evaluation? What will be the evaluation criteria?
  • In case of positive result, what is the career i should expect?

Now we must define a list of priorities and specific actions to work on. This is quite important as, when we start a new job, we can find two phasesi: a starting period and a full operational period. Starting period can last from four to six months. In such phase it is vital to obtain visible results (one or two at maximum) to get a serious credibility, which we will us as basys for the next phase.

Define short term objectives is fundamental to get a long and good career in a new company.

My suggestion, at this level, is to start elaborating your own vision to use as a reference for all the future decision. Given the vision, it will be easy to define a stretegy to follow to pursue our objectives.

From this momento it should be possible with our boss to produce a plan containing:

  • Activities (what I am supposed to do)
  • People 8who is working for me and possible new hiring)
  • Finance (what my limits are)
  • Business growth plan

Given the initial planning then we will:

  • Define the short term actions on people, systems and structures under our responsibility
  • Definire our learning agenda

3) Immediate action - Interviews
During the first weeks it is important to build a relationship network both in formal way (meeting) or informal ("coffee break"), in order to get additional information about the company. With regard to this it will be important to keep a series of meeting as earlier as possible  (even in the first week):

  • Remember to use an informal approach with the team members (or at least with team leaders) before going on with structured interviews. This allows us to immediately receive feedback about work habits, methodologies, expectations and ideas to improve the situation.
  • We should meet HR responsibles, in order to corectly understand the organization chart (real and theoretical) and to get as soon as possible an idea of the hiring process, of training and on the tools we have to influence our resources. We need also to understand what the salary, reward and promotion policies are.
  • We need to meet with staff at the same level as our and belonging to the organization which have a role not impacted by our work. We need to start building a network to build our idea of the situation. In particular we need to:
  • What about the opinion clients have about us? How do they perceive us? What are their biggest complaints? What are our strengths, according to them?
  • What are the most important policies and how do they impact on our work?
  • How other groups are organized? What is the methodology they use? What standards? Is it possible to use their approach?

If you work in IT it is also vital to understand logistic, and IT politics like disaster recovery, server management, hardware and software management . If we are entering in a pure IT company my suggestion is to take a look to the check-list"assessment of an IT group". In that checklist there are all the points to go trough in order to assess the status of a team/organization.

If we will be able to complete all the points that I enlightened, then the completion of an action plan should be easy to complete.


( 0 Votes )
Last Updated on Monday, 01 February 2010 18:08
 
« StartPrev123NextEnd »

Page 1 of 3
Shinystat
  • Italian - Italy
  • English (United Kingdom)
Archivio Articoli
< September 2010 >
Mo Tu We Th Fr Sa Su
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30      
Sondaggi
Quali sono i contenuti preferiresti di più in questo sito
 
Tag Clouds
Chi è online
We have 4 guests online
Pubblicità
Link consigliati:
Andy Johnson
Programming solutions for everyone
duegi render studio
3D modelling, rendering & animation
Nyx
Nyx propone innovativi sistemi basati sulla tecnologia RfId