- Technical Subject knowledge - Need not be expert in all areas, but need to understand things well enough to make better decisions.
- Be assertive, not aggressive though.
- Be cool under pressure.
- Competent.
- Integrity/Honesty.
- Ability to delegate tasks.
- Conduct meetings effectively (proper agenda, starting/ending on time, insisting full participation etc.,).
- Empathy - Understand and relate to individual's issues.
- Body language and tone is important (sometimes more than content).
- Tone is very important in meetings, conference calls and even on the email.
- Smile (even on the phone) helps a lot.
- Different people in the team want/appreciate different things. Need to understand that and communicate appropriately. There is no one way to communicate to a big diversified team.
- Create a positive atmosphere for the team and promote collaboration.
Sunday, October 3, 2010
Effective Leadership/Communication skills needed for a Manager
Recently, I got promoted to a development manager and being primarily a technical guy before, I'm trying to improve my leadership/communication skills. Below is my personal notes (gathered from various sources) on the qualities to possess to become a great manager.
Key Points for any Project (Traditional or Agile)
I'm using Scrum for the past 3+ years and have been ScrumMaster for most of this time. I embrace and advocate Scrum, but last week, I attended a FredPryor Seminar on project management, mainly to better understand the similarities and differences between traditional project management and Scrum. This also helped me in appreciating how basic project management skills applies to any industry. I want to highlight some of the common basic points which came up in the seminar, which are important irrespective of which methodology we are using.
- Kick-off meeting is important when starting projects (or Sprint in Agile) - I see this as similar to Sprint Planning in Agile. Everyone involved need to get a clear idea on what they are building.
- Team buy-in from the very beginning is critical.
- Brainstorming with the team on topics is important.
- Everyone (Team, Management, Stakeholders) agreeing on specific, realistic goals is important.
- Clear project definition and scope is very important. Avoid scope creep.
- Be SMART when defining a project (or Sprint in Agile) - Specific, Measurable, Achievable, Realistic, Timely.
- Risk Assessment - Understand constraints between Time, Cost and People. Often, when risk comes the trade-off is between one of these.
- Progress - Gantt-Chart in traditional project management becomes Burndown chart in Agile (at least on the high level).
- Meetings - Need to have team meetings on time, in regular schedule with a specific agenda. Full participation of team is important. Also, need to respect other's time and end the meeting on schedule. Finally, need to take meeting notes and follow up promptly.
- Team working collaboratively is very important. This will create a co-operative and productive atmosphere.
- Start the project with self-esteem and end it with self-esteem (for the team).
- Always recognize the team and celebrate success.
- Review all outstanding issues after the project (or Sprint in Agile) is done and see what can be improved - Similar to Sprint Retrospective.
Sunday, June 13, 2010
New Features in Eclipse 3.6 (Helios)
There are many interesting features coming up in Eclipse 3.6 code named as Helios . Below, I will discuss about some of these features which I came across.
Java/Plugin Development:
Eclipse Help :
Java/Plugin Development:
- Reports missing @Override notation if a method overrides a superclass method and has the notation missing. This only works for 1.6 code. Previously, we only had warnings when we added @Override but did not override a superclass method, but now this works the other way also. This would be helpful in removing the possibility of accidentally overriding a method.
- Variables view now has a new column (accessible by Layout->Select Column) to display the instance count of the variable.
- Package names in Java views can be customized by setting rules in Preferences->Java->Appearance->Abbreviate package names preference. For example, org.
eclipse .ui can be mapped to {UI} etc., - Users can see source of UI contributions using ALT +SHIFT +F3 in IDE. This is very similar to what PluginSpy used to provide, but now this functionality is provided by the platform. This also means that our
Eclipse RCP application can expose this functionality to end users. - -consoleLog program argument is now added to launch configuration of
Eclipse applications by default. This argument prints errors in Console view that normally go to ErrorLog to console. This would be very useful to debugEclipse RCP applications. - Console view now has option to open as OSGi console. This console is useful for plugin developers and can be used to interact with OSGi framework.
- "Add Artifact to Target Platform" dialog allows users to search a set of repositories for dependencies and add them to target platform.
- Resolving dependencies (similar to above point) is also available via quick fix, when there is a missing imported package.
- It is now possible to export contents of target platform to destination directory. You can get to this wizard by doing File->Export->Plug-in development->Target definition.
- Clients can now set an overlay image to Taskitem using TaskItem#setOverlayImage(Image).
- Clients can now set an overlay text to TaskItem using TaskItem#setOverlayText(String). Setting overlay image and text can be useful. For ex, this can be used to indicate the result of an operation which user kicked off in the application.
- Clients can now set the progress of an operation to TaskItem using TaskItem#setProgressState(int).
- Example for the above functionality can be seen in this snippet.
- Clients can now set the menu to application TaskItem using TaskItem#setMenu(Menu).
- Jobs progress can also be shown in Platform task bar. See this bug for more info on the API.
- Help UI footer can be customized by using the preference org.eclipse.help.base/footer.
- Help topics can now by sorted using sort attribute in toc and topic elements.
- Table of contents and help contents editors now report XML errors.
- Table of contents and help contents editors has spell check functionality.
- New extension points introduced to allow addition of buttons and frames to Help UI.
- "See" entries can now be added to Help index. i.e when user searches for a word, the results would appear and along with it "See" entries can also be displayed to direct users to related topics.
- Install wizard is now grouped by license. This means we no longer have to select each item and accept the license.
- We can now do compare in installation history i.e we can select any two installations from history and compare them by clicking on the compare button.
- Intro page can now have news feeds from multiple RSS news readers using EclipseRSSViewer.
- Users can now disable local history cleanup. This might help in faster shutdown since local history cleanup need not be done, but local history size would keep growing indefinitely.
- All 7 milestone releases and release candidates are done.
- Final release expected on June 23rd.
Saturday, June 12, 2010
Changing Eclipse RCP application workspace
We are developing an Eclipse RCP application and we wanted the default location of workspace to be under user's home directory and not under current directory (which is the default). By googling, I found that I can use -data program argument. But, when I put that option in .ini file it did not work. Some posts said that I should put the path argument after data in double quotes for it to work. But, that is not true either.
Finally, it turned out that I should specify the path in the next line after -data. Specifying the path in next line is the key here. So, in your application .ini file, it should look like:
-data
C:\MyAppWorkspace
Also, make sure that this (or any other program argument) appear before vm arguments.
But, we did not want to hardcode the path and instead wanted to point it to users home directory. For this, you could use:
-data
@user.home/MyAppWorkspace
This program argument can also be supplied as command line parameter. For example,eclipse .exe -data @user.home/MyAppWorkspace would work. Also, this could be supplied in the shortcut target in windows, if the application needs to be launched using double click.
In your RCP application, you can just specify these program arguments in "Launching" tab in your application .product editor. When you export your product, it will put the appropriate entry in your application .ini file.
Finally, it turned out that I should specify the path in the next line after -data. Specifying the path in next line is the key here. So, in your application .ini file, it should look like:
-data
C:\MyAppWorkspace
Also, make sure that this (or any other program argument) appear before vm arguments.
But, we did not want to hardcode the path and instead wanted to point it to users home directory. For this, you could use:
-data
@user.home/MyAppWorkspace
This program argument can also be supplied as command line parameter. For example,
In your RCP application, you can just specify these program arguments in "Launching" tab in your application .product editor. When you export your product, it will put the appropriate entry in your application .ini file.
Subscribe to:
Posts (Atom)