no_tag - jmbeas on Diigo

19 Oct 09

Gojko Adzic » How to divide and conquer software projects effectively

gojko.net/...-software-projects-effectively - Preview

divisions by responsibility and business value are the best.
Poppendieck compared waterfall to a “defect injection process”, saying that if specifications written first, then test and code based on those specifications by different people, the chance of them matching is very small, and there is nobody really to blame for that. She proposed that specifications should be written in the form of tests straight away, and then the code written according to these tests, to eliminate one potential cause of mismatch (specifications-tests) and ensure that the other (specifications-code) is easy to verify. This effectively is the idea behing agile acceptance testing.

10 Oct 09

A Good Way to Change a Corporate Culture - Peter Bregman - HarvardBusiness.org

blogs.harvardbusiness.org/...est-way-to-change-a-corpo.html - Preview

Performance reviews and training programs define the firm's expectations. Financial reward systems reinforce them. Memos and communications highlight what's important. And senior leadership actions — promotions for people who toe the line and a dead end career for those who don't — emphasize the firm's priorities.
Now the head of the firm wanted to change the rules mid-game.
3 more annotations...
- We tend to conform to the behavior of the people around us.
- If you want to change the culture, you have to change the stories.
- To start a culture change all we need to do is two simple things:
  
  Do dramatic story-worthy things that represent the culture we want to create. Then let other people tell stories about it.
  Find other people who do story-worthy things that represent the culture we want to create. Then tell stories about them.

La Justicia aumenta la responsabilidad de las consultoras informáticas - Expansión.com

www.expansion.com/...1253478282.html - Preview

La Justicia incrementa las responsabilidades de las consultoras informáticas. Un Juzgado de Primera Instancia de Vitoria ha declarado ilícita la conducta de una gran consultora informática a la que se había encomendado la realización de una implantación informática del conocido programa de gestión empresarial ERP SAP y ha calificado como "abandono de obra" ilícito la no terminación del programa, sentando así un importante precedente acerca de la siempre controvertida cuestión relativa a la naturaleza y el régimen jurídico aplicable a este tipo de proyectos informáticos.
no cabe ninguna duda de que se trata de un contrato de arrendamiento de obra y no de un mero contrato de servicios, como sostenía la consultora
7 more annotations...
- la consultora, tras varios retrasos ocurridos y renegociaciones del plazo y del precio del contrato, acabó finalmente renunciando al proyecto
- La consultora justificaba el abandono alegando tres motivos:
- elevada rotación del personal
- consultor independiente de la empresa SAP
- cambios del alcance del proyecto que la cliente habría solicitado
- la empresa cliente no se encontraba obligada a pagar ninguno de los cambios alegados en tanto que no habían sido acordados por las partes.
- Esta sentencia constituye un significativo precedente acerca de la naturaleza de los contratos de implantación informática, que, al ser calificados como de arrendamiento de obra, implican una serie de importantes responsabilidades para la empresa de consultoría informática en el caso de que no se consiga el resultado perfecto que el cliente espera conforme a sus necesidades, o de que la consecución de dicho resultado sólo pueda obtenerse mediante operaciones y trabajos no previstos o presupuestados inicialmente por la consultora.
  - ¡Ya era hora, hombre! - on 2009-10-10
  Add Sticky Note

Practice Agile Software Development: How do you measure software quality?

www.practiceagile.com/...-measure-software-quality.html - Preview

"Quality of a product is satisfied customer" - This statement is so true, but at the same time it's so vague.
there are various metrics that can be collectively used to determine the quality of the code and measure customer satisfaction.
4 more annotations...
- All stories should meet the "Done Done" criteria each iteration.
- Set organization wide code coverage metrics that all teams adhere to.
- Monitor number of defects found by the Quality Assurance team and by the Customers.
- Monitor regression test results for every fix being delivered

Agility@Scale: Strategies for Scaling Agile Software Development

www.ibm.com/...integrity_debt - Preview

Educate human resources people. Make them aware of what “Certified Scrum Master” really means and let them think for themselves.
Act professional, don’t just claim to be certified.
2 more annotations...
- The agile community needs to put together a decent certification program, something that the Scrum Alliance has clearly failed at doing.
- The good news is that people such as Ron Jeffries and Chet Hendrickson, and others, are putting together a developer certification program. The really good news is that these are the right people to do this. The really bad news is that they’re doing it under the aegis of the Scrum Alliance, so whatever they accomplish will unfortunately be tainted by the fallout of the CSM debacle.

Jeff's Blog: Task Tracking is an Agile Smell

langrsoft.com/...k-tracking-is-agile-smell.html - Preview

The desire to manage tasks in an agile process is evidence that a team is not collaborating.
In lieu of tracking progress by marking off completed stories, they look at progress in terms of what tasks have been completed.

06 Oct 09

Gojko Adzic » Putting Selenium in the right place

gojko.net/...ng-selenium-in-the-right-place - Preview

The Page Object pattern, popularised by Simon Stewart with WebDriver, seems to be the universally accepted best practice to manage UI tests efficiently and the preferred way to implement Selenium tests. However, at the recent CITCON Europe conference in Paris, Antony Marcano spoke against this and offered an alternative.
Marcano said that page objects focus on the wrong thing.
1 more annotations...
- When thinking about web site functionality, people don’t think about pages but about activities that span multiple pages. Focusing on goal oriented cross-page activities instead of page oriented functionality makes tests more natural, easier to understand and maintain.

04 Jul 09

Unhandled Exceptions » Blog Archive » Services, Anemic Domain Models, and ‘Where does my Business Logic Go?’

unhandled-exceptions.com/...here-does-my-business-logic-go - Preview

Services and Repositories can (and often need to be) aware of the entities they manipulate, but entities (usually) shouldn’t be aware of the services or repositories that manipulate THEM.
in a sense a repository is a just a ‘persistence-service’ for your domain.

20 Jun 09

NOOP.NL: Agile (Wrongfully) Assumes Craftsmanship

www.noop.nl/...lly-assumes-craftsmanship.html - Preview

People are not doing what they think is important.
Managers who want better results must acknowledge that they have to actively change the attitudes and behavior of their people. They must stimulate craftsmanship and discipline.

14 Jun 09

How do you convince your boss to TDD

misko.hevery.com/...-you-convince-your-boss-to-tdd - Preview

It is a skill that takes hours of practice to master. Don’t argue with someone over your experience; instead, make him live through the same experience.
Make sure you are reasonably good at TDD and have built a reasonably sized application before you try to show someone else how to do it.
9 more annotations...
- It took about one year before I felt that writing code test-first was the natural flow of things.
- Start something new in your free time and build it with TDD. Use it as a learning experience.
- Since you will be struggling a lot at the beginning, trying to bring TDD to an existing project may only fuel your boss’s feeling that TDD is not useful. Again, TDD is a skill and takes a while to develop.
- most of us add all kinds of interfaces and abstraction in the name of reusability. But what percent of the code you have written have you actually reused?
- Tests help ensure that your code is in fact reusable, because they force you to write classes that can be used both in production and in a test scenario.
- If you can’t write a test, you don’t have reusable code.
- If you write tests afterward, then at best the tests are an afterthought hacked on top of the production code; such tests are very unlikely to help us when you are refactoring, since they are likely to produce false negatives.
- Why is it that every discipline out there takes testing seriously except software? I believe it is because of the presumed inexpensive nature of fixing bugs.
- That isn’t a problem as long as, after you first code by hacking, you go back and write tests, or preferably, completely re-write the code test-first

08 Jun 09

¿Tester dedicado para equipos ágiles?

www.dosideas.com/...icado-para-equipos-agiles.html - Preview

- Se usa TDD con pruebas unitarias para construir el código de manera correcta
- Se usan pruebas de aceptación y QAS para construir el código que haga lo correcto ...

01 Jun 09

Kanban as Cure for “Failed Iterations”? | xProgramming.com

xprogramming.com/...cure-for-failed-iterations.htm - Preview

if we didn’t have a defined edge to the iteration, then no one could complain that we had failed if we got only nine out of ten things done that we “promised”.
4 more annotations...
- When the team tries to under-promise, this same manager or product owner will push them to commit to more: it’s part of that management pattern.
- a Kanban approach might fix this, because there is no defined point at which to apply this undue pressure.
- Now Kanban advocates will say that Kanban is better (what else would they say?) because it lets you have whatever rhythms you want rather than “imposing” one. Uh huh, yeah, and that’s why people who don’t cut the grass every week have yards that look like forests.
- My guess, however, is that just moving to Kanban in such a situation might be ignoring the real problem.

Automating Story Tests | xProgramming.com

xprogramming.com/...automating-story-tests.htm - Preview

When I say “story” test, I mean a test which has been provided to help the customer see that she has gotten what she asked for.
We use examples like this to ensure that we understand what our customer wants, and we show the results to our customer so that they’ll see what we’ve done. Ideally, they’ll see that we’ve done what they want; sometimes they’ll see that we’ve done something that they don’t want.
4 more annotations...
- If it doesn’t pass … we’ll need to run the test again.
- there is a chance we’ll break it. Therefore we need to run the test more than once.
- There is no test that is guaranteed to be needed only once.
- the only excuse for not automating these repeated tests is that we aren’t very good at automation.

04 May 09

DDD & Many to Many Object Relational Mapping

www.udidahan.com/...many-object-relational-mapping - Preview

A job can be posted to multiple job boards. And a job board can have multiple jobs posted. A regular many to many relationship. At this point, we’re not even going to complicate the association.

This is simply represented in the DB with an association table containing two columns for each of the entity tables’ ids.

In the domain model, developers can also represent this with the Job class containing a list of JobBoard instances, and the JobBoard class containing a list of jobs.

It’s intuitive. Simple. Easy to implement. And wrong.
But users don’t think like well-intentioned developers.
2 more annotations...
- While we could just leave the bi-directional/circular dependency between them, it would be preferable if we could make it uni-directional instead. To do that, we need to understand their relationship:
- For me, “aggregate root” is the DDD term for “only calling one method on one object in your service layer”. In other words, it’s use case specific, and not an inherent structural property of the domain model.

From CRUD to Domain-Driven Fluency

www.udidahan.com/...-crud-to-domain-driven-fluency - Preview

For instance, in an HR system, the process of interviewing candidates - wouldn’t you just insert, update, and delete these Appointment objects?
If I were to put on my domain-driven hat, I would describe those requirements differently – interview appointments have a lifecycle: proposed, accepted, cancelled, etc. It seems that only a user of the role HR Interviewer should be able to make appointments for themselves
3 more annotations...
- Later, when the candidate accepts the meeting, we could have the following method on ICandidate – void Accept(IAppointment); that would obviously check that the candidate is the right person for that interview, the appointment’s current state (not cancelled), etc – finally updating its state.
- Contrast this with a more traditional O/R mapping solution
- As you can see, we’ve got simpler, more expressive, and more testable code when employing the domain model pattern, than using “just” O/R mapping. I’m not saying that the domain model pattern doesn’t need O/R mapping in the background for it to work. But that’s just it - the persistence gunk needs to be in the background and the business logic needs to be encapsulated.

25 Apr 09

The Scatology of Agile Architecture

blog.objectmentor.com/...catology-of-agile-architecture - Preview

Complex systems designed from scratch never work.
However, there are architectural issues that need to be resolved up front. There are design decisions that must be made early.
6 more annotations...
- LDUF is absolutely essential
- In some circles this early spate of architectural thought is called Iteration 0.
- When I work on FitNesse, I spend a lot of time thinking about how I should implement a new feature. For most features I spend an hour or two considering alternative implementations. For larger features I’ve spent one or two days batting notions back and forth. There have been times when I’ve even drawn UML diagrams
- On the other hand, I don’t allow those early design plans to dominate once I start TDDing.
- Even if I don’t follow them they helped me to understand and constrain the problem. They gave me the context to evaluate the new solution that TDD helped me to discover.
- If you are working in an Agile team, don’t feel guilty about taking a day or two to think some issues through. Indeed, feel guilty if you don’t take a little time to think things through. Don’t feel that TDD is the only way to design. On the other hand, don’t let yourself get too vested in your designs. Allow TDD to change your plans if it leads you in a different direction.

15 Apr 09

Ruminations » Blog Archive » Beware the Hero

testobsessed.com/...beware-the-hero - Preview

The Hero mindset is deeply ingrained in the software industry culture.
the industry actually breeds heroes by making bug fixing an activity for junior people. They work hard, stay late, and get kudos from customers (or customer proxies)… and think that this is what being a good developer is about.
1 more annotations...
- It’s a deep irony that the apparently-irreplaceable-heroes can actually be the biggest impediments to success.

06 Apr 09

Bounded Context - DDD Step By Step

dddstepbystep.com/...bounded-context.aspx - Preview

A Bounded Context can be considered as a miniature application, containing it's own Domain, own code and peristsence mechanisms.

Within a Bounded Context, there should be logical consistency, each Bounded Context should be independent of any other Bounded Context.

Communication to and from a Bounded Context is done via a Context Map

Blogged Command Query Separation as an Architectural Concept - DDD Step By Step

dddstepbystep.com/...-an-architectural-concept.aspx - Preview

The concept of applying CQS at an architectural level says, our Domain and transactional operations will use the Repositories, but for Reporting operations, we will use a separate mechanism. The Command is the Domain operations, the Query is the Reporting operations.

26 Mar 09

James Shore: Stumbling Through Mediocrity

jamesshore.com/...mbling-Through-Mediocrity.html - Preview

there's really no point in Agile for the sake of Agile.
I'm no longer interested in helping people find the lowest-impact way to slap an Agile sticker on their door.

jmbeas 's Library tagged no_tag → View Popular

Gojko Adzic » How to divide and conquer software projects effectively

A Good Way to Change a Corporate Culture - Peter Bregman - HarvardBusiness.org

La Justicia aumenta la responsabilidad de las consultoras informáticas - Expansión.com

Practice Agile Software Development: How do you measure software quality?

Agility@Scale: Strategies for Scaling Agile Software Development

Jeff's Blog: Task Tracking is an Agile Smell

Gojko Adzic » Putting Selenium in the right place

Unhandled Exceptions » Blog Archive » Services, Anemic Domain Models, and ‘Where does my Business Logic Go?’

NOOP.NL: Agile (Wrongfully) Assumes Craftsmanship

How do you convince your boss to TDD

¿Tester dedicado para equipos ágiles?

Kanban as Cure for “Failed Iterations”? | xProgramming.com

Automating Story Tests | xProgramming.com

DDD & Many to Many Object Relational Mapping

From CRUD to Domain-Driven Fluency

The Scatology of Agile Architecture

Ruminations » Blog Archive » Beware the Hero

Bounded Context - DDD Step By Step

Blogged Command Query Separation as an Architectural Concept - DDD Step By Step

James Shore: Stumbling Through Mediocrity

Selected Tags

Sponsored Links

Top Contributors

Groups interested in no_tag

KDR Tau Chapter

alwaha

1PPPRET-PM

Web 2.0 Tools

Erotica

Digital Citizenship/Cyberbullying Video Clips