//AMIS Technology Blog » Scrum

Posts tagged Scrum

SIG Event

Kom kennismaken met AMIS en doe mee met uitdagende projecten

0
7 months ago
by Robbrecht van Amerongen in , , , , , , , , , , , , , , , , , , , , ,
Hierbij nodigen we je uit om met ons kennis te komen maken.

Ben jij een (junior) Oracle consultant die een stap verder wil maken? Wil je verder groeien en ontwikkelen tot principal consultant? AMIS geeft je de kans om die stap te zetten.  Bij ons krijg je de ruimte om te experimenteren én te leren samen met de experts op je vakgebied.

Laat ons in een vrijblijvend gesprek vertellen welke mogelijkheden we je kunnen bieden. Neem voor een afspraak met een van onze consultants contact op met Eva.van.der.kleij@amis.nl of bel haar op 030-6016000. Je bent van harte welkom.

AMIS merkt dat haar concept van hoogwaardige en kennisintensieve dienstverlening erg succesvol is. Onze toekomst ziet er erg aantrekkelijk uit met interessante opdrachten bij toonaangevende klanten. Vandaar dat we op zoek zijn naar uitbreiding van ons team.

Denk niet direct dat je hiervoor te weinig kennis of ervaring hebt: jouw toekomstige ervaren collega’s doen niets liever dan jou verder helpen. Ons trainingsprogramma voorziet in een grote diversiteit aan opleidingen en tijdens onze interne kennissessies kun je op veel terreinen iets van je collega’s opsteken. Concreet hebben we de volgende vacatures:

SIG Event

Do not register bugs, Fix them!

5
2 years ago
by Robbrecht van Amerongen in , , , ,

For years I was a proponent of bug/issue management systems and worked with open systems like Jira or Bugzilla and also with a lot of proprietary systems. I’ve used these systems during the development and production/ support phase of the products. Every time I use these systems I spend too much time registering, evaluating and sorting issues. At the end of the project I always get stuck with a dozen of unspecified issues with a vague status. Why is this? Bug tracking systems are not bad. The entire process of registering and tracking bugs is wrong.

What the most effective thing to do when you discover a bug? Registered the bug in a system and track it? Does this solve the bug? It doesn’t.  You should be busy resolving the bug, not administrating and tacking it!

(more…)

SIG Event

Automatic testing Oracle Service Bus using Hudson, maven and SoapUI

0
3 years ago
by Robbrecht van Amerongen in , , , , , , , , , , , , ,
A lot of current projects are implementing some sort of service based architecture. Testing in this architecture becomes more complex. When implementing an OSB project with Scrum you test-automation is imperative. Scrum will require more frequent testing of your system. This is only feasible (in time and money) when you automate as much as possible.   Using soapUI you are able to create visually SOAP tests on your OSB implementation and running them against the defined infrastructure (develop, test, acceptance).  SoapUI enables with easy tools to implements verification and validation of the responses of your OSB implementation. When running the test you are also able to set limits in SLA response times on all the calls. This way you are able to monitor depreciation of performance in older parts of your OSB implementation when adding new services.   You can record and edit your SOAP test easy with the soapUI interface and edit it later. When you maven-enable your project it is quite easy running your tests when you implement the “maven-soapui-plugin” (see my other posting http://technology.amis.nl/blog/3061/automated-soap-testing-with-maven).  In the meantime version 3.0 of More >
SIG Event

Agile software development, the principles. Principle 11: The best architectures, requirements, and designs emerge from self-organizing teams.

1
3 years ago
by Robbrecht van Amerongen in , , , , , , , ,
This is the eleventh of 12 posts about the principles of agile software development. Purpose is to go back to the start of the agile manifesto (http://agilemanifesto.org/principles.html) and discuss the implementation of the 12 principles in real life software engineering. Goals of agility are to go deliver software of higher quality, faster, with a higher acceptance to end-users and able to follow the changing business requirements to strive for competitive advantage.   The question is: is this going to work in practice or is this only based on a nice marketing and sales story.   Principle 11: The best architectures, requirements, and designs emerge from self-organizing teams.   For a long time the engineering expertise (and also software engineering) was based upon the condition that you worked with specialists. These specialists emerged from the principle of division of labour and made it possible for these specialists to focus their attention on their specialism and create the best solution within their field of expertise. The Interaction designer designed a user interface, the architect created a global systems model, developers created code and More >
SIG Event

(Dutch) AMIS kennissessie Scrum

4 years ago
by Robbrecht van Amerongen in , , ,

Datum: dinsdag 3 maart  2009 Tijd: 16:30 tot 21:00, incl. diner Locatie: AMIS, Edisonbaan 15 in Nieuwegein Doelgroep: Deze sessie is interessant voor zowel developers, projectmanagers, consultants als sales medewerkers. Coördinator: Robbrecht van Amerongen

Scrum, Just enough, just in time…

Scrum is een methodiek die ons in staat stelt om snel kwalitatief hoogwaardige software op te leveren; er wordt ontwikkeld en opgeleverd wat volgens de inzichten van vandaag nodig is (in plaats van wat maanden geleden eens is bedacht).

(more…)
SIG Event

Agile software development, the principles. Principle 9 : Continuous attention to technical excellence and good design enhances agility

4 years ago
by Robbrecht van Amerongen in , , , , ,

This is the ninth of 12 posts about the principles of agile software development. Purpose is to go back to the start of the agile manifesto (http://agilemanifesto.org/principles.html) and discuss the implementation of the 12 principles in real life software engineering. Goals of agility are to go deliver software of higher quality, faster, with a higher acceptance to end-users and able to follow the changing business requirements to strive for competitive advantage.

The question is: is this going to work in practice or is this only based on a nice marketing and sales story.

Principle 9: Continuous attention to technical excellence and good design enhances agility.

The first time I looked at this principle I thought: “How is this possible”. Agility focuses on quickly delivering working software (reading: “Quick and dirty”). I experienced this is not true. Attention to technical excellence is making the agile process working better. Technical excellence can make the development process more flexible. In this context I would like to point out that there is a difference between technical excellence / good design compared to complex design and technical complexity. How many More >

Go to Top