ÉnKép - takacsot

Original

Original

Nagyon jó előadás a Scrumról. A címmel ellentétben kb az előadás harmada szól az distributed team-ekről. A többi pedig a Scrum maga. Nagyon érdekes mellékes dolgok derülnek ki az aleőadásból.

 I’ve always considered Tom to have been the original agilist.

Original

 There's a mess I've heard about with quite a few projects recently. It works out like this:

 

• They want to use an agile process, and pick Scrum
• They adopt the Scrum practices, and maybe even the principles
• After a while progress is slow because the code base is a mess

What's happened is that they haven't paid enough attention to the internal quality of their software. If you make that mistake you'll soon find your productivity dragged down because it's much harder to add new features than you'd like. You've taken on a crippling TechnicalDebt and your scrum has gone weak at the knees. (And if you've been in a real scrum, you'll know that's a Bad Thing.)

 

Original

 

Tom Gilb munkájának eredményét már korábban is ismertem (lásd Evo). elérkezett az idő arrra, hogy megszerezzem egyik könyvét és meglássam, hogy a kivonatok, cikkek alapján az egész köny és a mögötte lévő tudás is olyan jó, mint gondoltam.

Kettős eredménye lett. Tudás és érték ott van. Fenomenális mű. Ott van minden, amiről beszélni akar. De a stílusa számomra kicsit nehézkes. Vagy ami talán jobb szó lenne rá az, hogy száraz. Fele olyan tempóben nem értem végig rajta, mint Rothman könyvén (erről majd később bővebben).

Két terület igazán fontos munkályában: a követelmények kezeláse és az evolutionarz delivery. Minden fejezet ezen két téma körül forog.

TOC

Igen jó összefoglaló

Kiválló hangulatú regény. Ugyan az írója korunkbeli, de hangulatilag roppant ódon regényt hozott össze. De pontosan ez adja azt a kiválló hangulatot, ami megragadott. Külön örömömre szolgál, hogy meglehetősen vaskos regényre sikerült, tehát tovább tartott, mint a legtöbb könyvem. 

Történetileg egyszerű, de hangulatos 19. századi angliai történet. Az angol mágia felemelkedésének története. Két mágus, aki a nagy ősőkön alapuló tudományt tanulmányoz. Barátokból ellenségek, majd partnerek lesznek. És mellékesen a tündék visszatérnek Angliába.

Vélemény

kiadónál

eKultura

Már korábban is írtam erről az irományról. korábban kb 45 oldal volt  most már laza 100 oldalra hízott. Azaz folyamatosan fejlesztik. Szóval megint csak kiválló mű.

Elérhetőség

Original

I’m not sure why, but I got the impression that lots of people think that messaging is only for huge systems in investment banks, not something that a small or a mid-size project should consider at all. This is false and now I’ll try to convince you.

In a nutshell, messaging allows us to reliably break up a single process into several parts which can then be executed asynchronously. They can be executed with different threads, or even on different machines. The parts communicate by sending each other messages. The messaging framework guarantees that messages get delivered to the right recipient and wake up the appropriate thread when a message arrives.

Fire and Forget

Messaging is a great solution when you want to ensure that something gets done, but you don’t really care about the results and you don’t want to wait for it to finish. This kind of behaviour can often be found when the last part of a process requires talking to an external system or some sort of batch processing.

Just leave it there when you’re done

Another very interesting case is when there is a resource intensive or a time consuming operation that we want to execute and we care about the results, such as generating a long report or processing transactions with external payment providers.

Share the load

Whenever lots of different agents can request some work to be done, consider messaging as a way to decouple requesters and workers.

Original

Original

The site

Feature-ök, story-k taskokból állnak. Többől is. Némely fejlesztőnél észrevettem, hogy egyszerre több taskon is dolgozik ugyan azzal a feature-vel kapcsolatban (daily standup során világosan látszik, hogy napról napra több taskot tesz fel, de ne teszi át a done állapotba). Miért lehet ez?

• Kicsik a taskok és többet is el tud végezni. Igen ez triviális, de lást entebb nem ez ahelyett, mert akkor a régiek kikerülnek in progress állapotból.
• Többen dolgoznak rajta, mint jelezték és azok munkája is az adott emberen keresztül jelenik meg. Uff! Pedig a daily standup pont erre van.
• Nem jól bontja fel a taskot. Olyan feladatokat határozott meg, amik kész volta nem egyértelműen meghatározható, csak a többi vagy éppen a teljes feature elkészítése után dönthető el.
• Hibásan értelmezi a taskot. Tipikusan kevesebbet értenek a taskba, mint ami oda tartozik. Pl "középréteg művelet implementálása" az üzleti logika kifejtését jelenti. De bizony ide tartozik a db és a kliens stubok kapcsolódó változtatása is. ez egyből több modult érint és emiatt kerül több task, mert akkor már "elkezdi" a UI-t is. Hasonló az előzőhöz.
• Nincs tisztában azza, hogyan is akarja megoldani a feladatot. Mindenbe belekap. Megint csak a hibás feladat felosztás egy variánsa.

És mit lehet tenni?

Did You Know? from Amybeth on Vimeo.

Original

Pénzügyi kontroll megteremtése: tessék írásban vezetni minden kiadást és bevételt. Aztán tessék csoportosítani és összegezni. Ez egy látszólag rendkívül egyszerű dolog - ugyanakkor mintha egy hatalmas szőrös kéz nyúlna ki az ember hátsó agyából (hah micsoda kép!) és akadályozná a rendszeres bevezetést.

Kilábalás az adósság csapdából

Rövidtávú biztonság: 3-6 havi tartalék és a mindenre kiterjedő biztosítás

Megvalósítom életem nagy céljait - és most elkezdem

Original

In my view, the purpose of the iteration planning is for the team to arrive at a commitment to some set of functionality that they feel reasonably confident they can complete in the coming iteration. The purpose is not to identify tasks. The purpose is not to estimate the number of hours for each of those tasks. The purpose is to figure out how many and which product backlog items they can commit to delivering in the coming iteration.

 

Original

 Cooper offers these “seven ingredients of a unique, superior product with real value for the customer”:

1. Meets customers’ needs better than competitive products.

2. Is a better-quality product than competitors’ (however the customer defines quality).

3. Has unique benefits and features for the customer.

4. Solves customers’ problems with competitive products.

5. Reduces the customer’s total in-use costs (better value-in-use).

6. Has highly visible benefits for users.

7. Is innovative or novel — the first of its kind on the market.

More importantly, he adds: “Note that product superiority is defined in the eyes of the customer!” While you may believe your product to be superior on one or more of these dimensions, it is ultimately up to the market to decide whether this is the case. Too often the view of product superiority and differentiation is different from those within the company versus those in the market.

Original

 Requirements

1. Can you name a number of non-functional (or quality) requirements?

2. What is your advice when a customer wants high performance, high usability and high security?

3. Can you name a number of different techniques for specifying requirements? What works best in which case?

4. What is requirements tracing? What is backward tracing vs. forward tracing?

5. Which tools do you like to use for keeping track of requirements?

6. How do you treat changing requirements? Are they good or bad? Why?

7. How do you search and find requirements? What are possible sources?

8. How do you prioritize requirements? Do you know different techniques?

9. Can you name the responsibilities of the user, the customer and the developer in the requirements process?

10. What do you do with requirements that are incomplete or incomprehensible?

Functional Design

1. What are metaphors used for in functional design? Can you name some successful examples?

2. How can you reduce the user's perception of waiting when some functions take a lot of time?

3. Which controls would you use when a user must select multiple items from a big list, in a minimal amount of space?

4. Can you name different measures to guarantee correctness of data entry?

5. Can you name different techniques for prototyping an application?

6. Can you name examples of how an application can anticipate user behavior?

7. Can you name different ways of designing access to a large and complex list of features?

8. How would you design editing twenty fields for a list of 10 items? And editing 3 fields for a list of 1000 items?

9. What is the problem of using different colors when highlighting pieces of a text?

10. Can you name some limitations of a web environment vs. a Windows environment?

Technical Design

1. What do low coupling and high cohesion mean? What does the principle of encapsulation mean?

2. How do you manage conflicts in a web application when different people are editing the same data?

3. Do you know about design patterns? Which design patterns have you used, and in what situations?

4. Do you know what a stateless business layer is? Where do long-running transactions fit into that picture?

5. What kinds of diagrams have you used in designing parts of an architecture, or a technical design?

6. Can you name the different tiers and responsibilities in an N-tier architecture?

7. Can you name different measures to guarantee correctness and robustness of data in an architecture?

8. Can you name any differences between object-oriented design and component-based design?

9. How would you model user authorization, user profiles and permissions in a database?

10. How would you model the animal kingdom (with species and their behavior) as a class system?

Construction

1. How do you make sure that your code can handle different kinds of error situations?

2. Can you explain what Test-Driven Development is? Can you name some principles of Extreme Programming?

3. What do you care about most when reviewing somebody else's code?

4. When do you use an abstract class and when do you use an interface?

5. Apart from the IDE, which other favorite tools do you use that you think are essential to you?

6. How do you make sure that your code is both safe and fast?

7. When do you use polymorphism and when do you use delegates?

8. When would you use a class with static members and when would you use a Singleton class?

9. Can you name examples of anticipating changing requirements in your code?

10. Can you describe the process you use for writing a piece of code, from requirements to delivery?

Algorithms

1. How do you find out if a number is a power of 2? And how do you know if it is an odd number?

2. How do you find the middle item in a linked list?

3. How would you change the format of all the phone numbers in 10,000 static html web pages?

4. Can you name an example of a recursive solution that you created?

5. Which is faster: finding an item in a hashtable or in a sorted list?

6. What is the last thing you learned about algorithms from a book, magazine or web site?

7. How would you write a function to reverse a string? And can you do that without a temporary string?

8. What type of language do you prefer for writing complex algorithms?

9. In an array with integers between 1 and 1,000,000 one value is in the array twice. How do you determine which one?

10. Do you know about the Traveling Salesman Problem?

Data Structures

1. How would you implement the structure of the London underground in a computer's memory?

2. How would you store the value of a color in a database, as efficiently as possible?

3. What is the difference between a queue and a stack?

4. What is the difference between storing data on the heap vs. on the stack?

5. How would you store a vector in N dimensions in a datatable?

6. What type of language do you prefer for writing complex data structures?

7. What is the number 21 in binary format? And in hex?

8. What is the last thing you learned about data structures from a book, magazine or web site?

9. How would you store the results of a soccer/football competition (with teams and scores) in an XML document?

10. Can you name some different text file formats for storing unicode characters?

Testing

1. Do you know what a regression test is? How do you verify that new changes have not broken existing features?

2. How can you implement unit testing when there are dependencies between a business layer and a data layer?

3. Which tools are essential to you for testing the quality of your code?

4. What types of problems have you encountered most often in your products after deployment?

5. Do you know what code coverage is? What types of code coverage are there?

6. Do you know the difference between functional testing and exploratory testing? How would you test a web site?

7. What is the difference between a test suite, a test case and a test plan? How would you organize testing?

8. What kind of tests would you include for a smoke test of an ecommerce web site?

9. What can you do reduce the chance that a customer finds things that he doesn't like during acceptance testing?

10. Can you tell me something that you have learned about testing and quality assurance in the last year?

Maintenance

1. What kind of tools are important to you for monitoring a product during maintenance?

2. What is important when updating a product that is in production and is being used?

3. How do you find an error in a large file with code that you cannot step through?

4. How can you make sure that changes in code will not affect any other parts of the product?

5. How do you create technical documentation for your products?

6. What measures have you taken to make your software products more easily maintainable?

7. How can you debug a system in a production environment, while it is being used?

8. Do you know what load balancing is? Can you name different types of load balancing?

9. Can you name reasons why maintenance of software is the biggest/most expensive part of an application's life cycle?

10. What is the difference between re-engineering and reverse engineering?

Configuration Management

1. Do you know what a baseline is in configuration management? How do you freeze an important moment in a project?

2. Which items do you normally place under version control?

3. How can you make sure that team members know who changed what in a software project?

4. Do you know the differences between tags and branches? When do you use which?

5. How would you manage changes to technical documentation, like the architecture of a product?

6. Which tools do you need to manage the state of all digital information in a project? Which tools do you like best?

7. How do you deal with changes that a customer wants in a released product?

8. Are there differences in managing versions and releases?

9. What is the difference between managing changes in text files vs. managing changes in binary files?

10. How would you treat simultaneous development of multiple RfC's or increments and maintenance issues?

Project Management

1. How many of the three variables scope, time and cost can be fixed by the customer?

2. Who should make estimates for the effort of a project? Who is allowed to set the deadline?

3. Do you prefer minimization of the number of releases or minimization of the amount of work-in-progress?

4. Which kind of diagrams do you use to track progress in a project?

5. What is the difference between an iteration and an increment?

6. Can you explain the practice of risk management? How should risks be managed?

7. Do you prefer a work breakdown structure or a rolling wave planning?

8. What do you need to be able to determine if a project is on time and within budget?

9. Can you name some differences between DSDM, Prince2 and Scrum?

10. How do you agree on scope and time with the customer, when the customer wants too much?

Original

 Australian scientists have reviewed a global pool of research into the effect of modern office design, concluding the switch to open-plan has led to lower productivity and higher worker stress.

Original

Original

 Semmi kiemelendő, mert jó összefoglaló. Kár, hogy még mindig figyelni kell ezekre.

Original

Before we held this retrospective, I think some of the team members felt that we would not gain much from doing a full-day retrospective this time around. We had made good progress on our action items from the previous retrospective, and the general feeling was that things were going basically well. What could we possibly need to change?

People, please don’t hold retrospectives only when your team feels like there’s a problem that needs to be dealt with. If you hold retrospectives on a regular basis, whether you feel like you “need” to or not, you will uncover issues before the become problems. In our case, we managed to uncover a number of issues during our retrospective that could easily have grown into much larger problems if we didn’t bother to think about them until the effect was obvious.

Original