AgileWorks Romania
11Jan/17Off

Code and beer

What

The code and beer idea is simple enough: we gather in the evening after work, in a pub, have a beer and write some code. It is a social coding event where you can share ideas with other developers. You can come and leave whenever you want.

Why would you come and join us

Meet other programmers
Work on your own project
Help others with their projects
Find someone who might help you with a specific topic
Pair with someone and learn new things
Just hang around and talk to people

How

Bring your laptop and some code that you'll be working on. If you don't have code then think about what you would like to practice during the evening.

There is no predefined agenda. We just meet and work on whatever we feel like.

Important

Please specify what you would like to do during the evening by answering the question "What would you like to practice?" when registering.

Also, as soon as you know you can no longer attend the meeting please change your RSVP to NO immediately. Consider this gesture a sign of respect towards other members of this group who might want to attend in your place.

The number of attendees is limited because of the difficulties of finding a big pub and making reservations for a big group.

Filed under: Comments Off
4Jan/17Off

Timisoara Agile Software Meetup

The program for this meetup will be published in the week preceding the event.

Filed under: Comments Off
29Dec/16Off

Code and beer

What

The code and beer idea is simple enough: we gather in the evening after work, in a pub, have a beer and write some code. It is a social coding event where you can share ideas with other developers. You can come and leave whenever you want.

Why would you come and join us

Meet other programmers
Work on your own project
Help others with their projects
Find someone who might help you with a specific topic
Pair with someone and learn new things
Just hang around and talk to people

How

Bring your laptop and some code that you'll be working on. If you don't have code then think about what you would like to practice during the evening.

There is no predefined agenda. We just meet and work on whatever we feel like.

Important

Please specify what you would like to do during the evening by answering the question "What would you like to practice?" when registering.

Also, as soon as you know you can no longer attend the meeting please change your RSVP to NO immediately. Consider this gesture a sign of respect towards other members of this group who might want to attend in your place.

The number of attendees is limited because of the difficulties of finding a big pub and making reservations for a big group.

Filed under: Comments Off
22Dec/16Off

Coding Dojo – Identify & fight systemic issues creating legacy code

This time we will try to create code we do not consider “legacy”. I’ll play the role of your client and use some techniques to make you fail. We’ll then discuss what techniques I have used, how they happen in real life, how to fight them in your project.


-------------------------------------------------------

A Coding Dojo is a team practice format that accelerates knowledge transfer and sharing skills between team members. With an experienced facilitator, it is also a way of learning by applying various techniques.

Objectives

The following skills are typical candidates for improvement during a dojo:

• Refactoring
• Simple design
• Clean code
• Improving pair programming technique
• How to safely modify code you don't understand (usually legacy code)
• Learning a new programming language
• Unit testing
• Test driven development

In addition, coding dojo can be used by a team as a collective and structured way of solving difficult or risky problems related to production, like fixing a bug or redesigning parts of the application.

How it works?

The basic format of a coding dojo:

• All developers and the facilitator gather in a room.
• The facilitator introduces the purpose and the format of the coding dojo.
• One laptop with a functional development environment is connected to a projector.
• Two developers pair program on the laptop. The others are in the room, watching the code changes.
• Every 7 minutes, one developer leaves the laptop and the next one from the room takes his place.
• After a specified period of time (usually around two hours), the dojo ends with a retrospective.

Filed under: Comments Off
14Dec/16Off

Code and beer

What

The code and beer idea is simple enough: we gather in the evening after work, in a pub, have a beer and write some code. It is a social coding event where you can share ideas with other developers. You can come and leave whenever you want.

Why would you come and join us

Meet other programmers
Work on your own project
Help others with their projects
Find someone who might help you with a specific topic
Pair with someone and learn new things
Just hang around and talk to people

How

Bring your laptop and some code that you'll be working on. If you don't have code then think about what you would like to practice during the evening.

There is no predefined agenda. We just meet and work on whatever we feel like.

Important

Please specify what you would like to do during the evening by answering the question "What would you like to practice?" when registering.

Also, as soon as you know you can no longer attend the meeting please change your RSVP to NO immediately. Consider this gesture a sign of respect towards other members of this group who might want to attend in your place.

The number of attendees is limited because of the difficulties of finding a big pub and making reservations for a big group.

Filed under: Comments Off
9Dec/16Off

Agile Talks #20

Hi,

Spring is coming. Let's celebrate this by having two talented women sharing their knowledge and experience with us.

First we have Steliana Moraru. In her presentation, The Hitchhikers's guide through the leadership and communication galaxy, she will share with us short case studies, lessons of successful communication or failed from working with technical teams & tech projects, useful for everyone in management & leadership position.

Steliana has a diverse background that spans communication, marketing, program management & corporate social responsibility. A technology aficionado and a seasoned communication professional, she currently wears a few hats: Marketing & Communication Manager for MozaicWorks, Ph.D. candidate in Communication & Public Relations, and University teaching assistant.
Previously, she worked as communication and program manager for local and international organisations, focusing mainly on developing innovative projects that enabled the power of technology for the social good. She is passionate about how technology can change and develop communities, data in all forms (her Ph.D thesis is takling the Big Data subject), and working people who want to drive a positive change.


Second speaker is Maria Diaconu. She will be speaking about The role of the manger in an Agile Organization

Briefly about Maria: she is a tech entrepreneur, manager, start-up mentor & former programmer focused on building long-term innovative teams within the global organizations, including Mozaic Works & MozaicLabs. In her teams one of the main objectives is to increase the team members skills so that these can sustain the agility of the business they are part of. Also, Maria is the founder of AgileWorks community, the Agile Lean Software craftsmanship community active in 7 cities in Romania.


Agenda:

18:45 - 19:00 Arriving, socializing
19:00 - 19:10 Introduction
19:10 - 19:40 The Hitchhikers's guide through the leadership and communication galaxy
19:40 - 20:10 The role of the manager in an Agile Organization  
20:10 - 20:20 Break
20:20 - 21:10 Open Space - ask the speakers for more details or propose interesting topics
21:10 - 21:20 Closing

See you on 14h of March!

Filed under: Comments Off
7Dec/16Off

Timisoara Agile Software Meetup

The program for this meetup will be published in the week preceding the event.

Filed under: Comments Off
28Nov/16Off

Code and beer

What

The code and beer idea is simple enough: we gather in the evening after work, in a pub, have a beer and write some code. It is a social coding event where you can share ideas with other developers. You can come and leave whenever you want.

Why would you come and join us

Meet other programmers
Work on your own project
Help others with their projects
Find someone who might help you with a specific topic
Pair with someone and learn new things
Just hang around and talk to people

How

Bring your laptop and some code that you'll be working on. If you don't have code then think about what you would like to practice during the evening.

There is no predefined agenda. We just meet and work on whatever we feel like.

Important

Please specify what you would like to do during the evening by answering the question "What would you like to practice?" when registering.

Also, as soon as you know you can no longer attend the meeting please change your RSVP to NO immediately. Consider this gesture a sign of respect towards other members of this group who might want to attend in your place.

The number of attendees is limited because of the difficulties of finding a big pub and making reservations for a big group.

Filed under: Comments Off
22Nov/16Off

Coding Dojo – Implementing the Berlin Clock using TDD

This time, we are going to use test driven development (TDD) to implement the Berlin Clock. 

The specifications of this rather odd clock are:

The time is calculated by adding the lit rectangular lamps. 
The top lamp is a pump which is blinking on/off every two seconds. 
In the upper line of red lamps every lamp represents 5 hours. 
In the lower line of red lamps every lamp represents 1 hour. So if in the first line 2 lamps are lit and in the second line 3 lamps its 5+5+3=13h or 1 p.m. 
In the third line with tall lamps every lamp represents 5 minutes. 
There are 11 lamps, the 3rd, 6th, and 9th are red indicating the first quarter, half, and the last quarter of the hour. 
In the last line with yellow lamps every lamp represents 1 minute.

If you're wondering, this clock really exists in Berlin. Learn more about it on Wikipedia.

A Coding Dojo is a team practice format that accelerates knowledge transfer and sharing skills between team members. With an experienced facilitator, it is also a way of learning by applying various techniques. Objectives

The following skills are typical candidates for improvement during a dojo:

• Refactoring
• Simple design
• Clean code
• Improving pair programming technique
• How to safely modify code you don't understand (usually legacy code)
• Learning a new programming language
• Unit testing
• Test driven development

In addition, coding dojo can be used by a team as a collective and structured way of solving difficult or risky problems related to production, like fixing a bug or redesigning parts of the application.

How it works?

The basic format of a coding dojo:

• All developers and the facilitator gather in a room.
• The facilitator introduces the purpose and the format of the coding dojo.
• One laptop with a functional development environment is connected to a projector.
• Two developers pair program on the laptop. The others are in the room, watching the code changes.
• Every 7 minutes, one developer leaves the laptop and the next one from the room takes his place.
• After a specified period of time (usually around two hours), the dojo ends with a retrospective.

Filed under: Comments Off
15Nov/16Off

From Dogma to Light: Embracing The Agile Mindset

Are you disappointed or frustrated by the results of your Agile approach?


Have you put in place the roles, artifacts, practices and rituals and you did not realised the promised benefits? If so, you're not alone.


This is a classic problem, due to textbook Agile implementations that are rigid, mechanical, and driven by so-called "best practices" 

Join us to discuss about what it means to be agile. We will examine the most often overlooked, subjective, personal, and intangible pieces that are often missing from effective agile implementations.


Speaker: Ionut Grecu

Filed under: Comments Off