Agile

[ryzam]

Selain dari team member mediu, siapa lagi yang ada pengalaman adopt
agile dalam development process ditempat kerja? Boleh share sedikit
difficulty, approach etc. Kalau dapat dijadikan pengalaman yang berguna

[Khairul]

Aku team member kat mediu. Aku belum fully practice 'agile' (aku ade buat agile secara tak langsung dan tanpa disedari) tapi aku nak share pendapat yang mungkin boleh beri manfaat pada orang lain.

Walauapa pun method yang kita nak guna dalam agile (scrum, xp, lean, crystal), kita perlu ada 'standard work' ataupun org panggil SOP (Standard Operating Procedure). Contohnya dalam scrum, ada product backlog, sprint backlog, dan burndown chart. Tapi bila nak update, bila nak review, etc?

Bila org baca SOP, "Oh, kita tak perlu SOP, nanti kita dikekang oleh SOP, tak 'agile'", etc. Kita perlu ingat, SOP ni kita yang set, dan ianya akan sentiasa berubah, tanam mindset sebagai 'cathedral builders' walaupun ada seorang pemotong batu. Kat jepun org panggil 'kaizen' (continuous improvement). Skrg ni tools yang paling berkesan untuk documenting continuous improvement ialah Wiki. Semua orang boleh ubah, kalau kita tak suka dengan 'standard work' yang sedia ada (discuss dulu) boleh ubah.

The difficulty of implementing any methodologies is always people. Tools (wiki, issue tracking) dah ada, cuma orang sahaja yang tak empower it with their knowledge and their thoughts on how things should be done.

Pada pendapat aku, approach yang terbaik untuk implement ape jenis methodology pun ialah, Kaizen.

References

- Training Within Industry  (Mass scale production training program for World War 2)

- Taiichi Ohno, Workplace Management, 1982

- Ohno, Taiichi (1988), Toyota Production System: Beyond Large-Scale Production

2009/1/15 ryzam <irwa...@gmail.com>

Selain dari team member mediu, siapa lagi yang ada pengalaman adopt
agile dalam development process ditempat kerja? Boleh share sedikit
difficulty, approach etc. Kalau dapat dijadikan pengalaman yang berguna

--
Regards,
MOHD KHAIRUL ANUAR
Software Developer

[Khairul]

Memandangkan takde orang yang reply. Aku ade terjumpa satu post pasal
pengalaman org dengan agile.

Dia ada 14 bahagian, cerita pasal agile. Tapi ini latest post,

My First Agile Project: The Last Mile
http://agilesoftwaredevelopment.com/blog/mattgrommes/my-first-agile-project-last-mile

On Jan 15, 10:32 am, Khairul <mkhai...@gmail.com> wrote:
> Aku team member kat mediu. Aku belum fully practice 'agile' (aku ade buat
> agile secara tak langsung dan tanpa disedari) tapi aku nak share pendapat
> yang mungkin boleh beri manfaat pada orang lain.
> Walauapa pun method yang kita nak guna dalam agile (scrum, xp, lean,
> crystal), kita perlu ada 'standard work' ataupun org panggil SOP (Standard
> Operating Procedure). Contohnya dalam scrum, ada product backlog, sprint
> backlog, dan burndown chart. Tapi bila nak update, bila nak review, etc?
>
> Bila org baca SOP, "Oh, kita tak perlu SOP, nanti kita dikekang oleh SOP,
> tak 'agile'", etc. Kita perlu ingat, SOP ni kita yang set, dan ianya akan
> sentiasa berubah, tanam mindset sebagai 'cathedral builders' walaupun ada
> seorang pemotong batu. Kat jepun org panggil 'kaizen' (continuous
> improvement). Skrg ni tools yang paling berkesan untuk documenting
> continuous improvement ialah Wiki. Semua orang boleh ubah, kalau kita tak
> suka dengan 'standard work' yang sedia ada (discuss dulu) boleh ubah.
>
> The difficulty of implementing any methodologies is always people. Tools
> (wiki, issue tracking) dah ada, cuma orang sahaja yang tak empower it with
> their knowledge and their thoughts on how things should be done.
>
> Pada pendapat aku, approach yang terbaik untuk implement ape jenis
> methodology pun ialah, Kaizen.
>
> References
> - Training Within

> Industry<http://en.wikipedia.org/wiki/Training_Within_Industry>

>   (Mass scale production training program for World War 2)
> - Taiichi Ohno, Workplace Management, 1982

> - Ohno, Taiichi (1988), *Toyota Production System: Beyond Large-Scale
> Production*
>
> 2009/1/15 ryzam <irwana...@gmail.com>

[Khairul]

Summary untuk My First Agile Project Series,
http://agilesoftwaredevelopment.com/blog/mattgrommes/my-first-agile-project-so-its-come-year-review

On Jan 16, 4:52 pm, Khairul <mkhai...@gmail.com> wrote:
> Memandangkan takde orang yang reply. Aku ade terjumpa satu post pasal
> pengalaman org dengan agile.
>
> Dia ada 14 bahagian, cerita pasal agile. Tapi ini latest post,
>

> My First Agile Project: The Last Milehttp://agilesoftwaredevelopment.com/blog/mattgrommes/my-first-agile-p...

[ryzam]

Agile ada flexibility. By the way agile amat berfungsi jika dilakukan
didalam team dan team itu tidak lebih dari 20 org.

[Khairul]

An Interview with Mary Poppendieck http://www.shmula.com/183/12-questions-with-mary-poppendieck
2. Mishkin Berteig said, August 21, 2006 @ 2:25 pm Mary, based on your
experience with lean environments and your experience with agile
environments, what do you think is the most important improvement or
change to be made to the Scrum methodology to make it more “lean”?

Scrum should not be considered a static methodology, it should follow
its own advice (inspect and adapt) and evolve over time. One way to
make sure this happens is to keep up with what Scrum’s inventor, Jeff
Sutherland, is doing with it today. It is important that Scrum teams
focus on the whole product, not just developing software. At Jeff’s
company, this is accomplished by defining the end of a sprint as
successful live deployment at multiple customers’ production sites.
The whole development team is engaged not in making the product owner
happy, but in getting all targeted customer sites to go live on time.
This means sending out release candidates early and happily accepting
and adapting to the surprises they uncover. It makes the customers’
users and support people as much a part of the team as the developers.

According to Jeff, ScrumMasters must be true leaders who help teams
self-organize to meet commitments. The team must focus on and adapt to
customer needs dynamically, as part of every sprint. Architecture must
support incremental development. Disciplined development and
deployment practices must be in place. Product managers must have an
accurate, up-to-date assessment of what is possible, and may commit
only to what can be done within the team’s proven capacity. Finally,
senior management and company culture must be fully engaged in
supporting this way of working.


Salah satu perkara menarik ialah apabila disebut mengenai TPS (Toyota
Production System bukan Test Procedure Specification) orang akan cakap
software development is a 'Knowledge Creation Process' it is not an
existing procedure that can be replicated to make it work. But then,
Jeff Sutherland said, the Toyota Team went and manage an already
successful and efficient software company and double their
productivity and effectiveness. So how can a production team manage a
software development company unless there is a lot in common between
them? There is a lot to learn from TPS and the Toyota Way.

[ryzam]

As i said before agile have flexibility, it's not static and not 100%
can follow what you've read or hear, it can be as your guideline, it
is an art that comes with experience. For whom wanted to introduce
agile to their org, don't be surprise it maybe take a year to really
understand and change the common process in software development. Try
not to fanatic to follow all the agile process or change current
existing process totally, it cannot work like that.

[Khairul]

Change requires something to compare with. How did we do agile in the
last 9 months? Nobody knows, if the current developers who practices
agile left, what can the new developer learn from their predecessors?
Nothing! Because there is nothing to compare with and anything to
learn from. People try to adopt agile because they think they can
write less (or no more) documentation, no more processes that can
constraint them with their agility and flexibility. This is a very
misleading school of thought and mindset. Agile is a very disciplined
development and deployment practices.

The books gives us guideline, but if we want to implement it, we have
to write down our own agile process, adapt it to our own environment.
By writing down our own processes we can express what we understand,
so that we know how to explain it to others.

[Khairul]

ryzam, why don't you share your experience in implementing agile?

[Khairul]

There are some nice comments on this post,
http://agilesoftwaredevelopment.com/blog/janusz-gorycki/dont-use-scrum

[ryzam]

Really it's tough for me actually to implement agile, I'm not scrum
master and even I'm very new to this term. But for me if you cannot
follow 100% what agile/scrum process should do, you don't ignore all.
Because of flexibility offered in agile process, you can practice a
simple task first. For example if you take scrum process for status
update meeting where scrum state every team member should gather every
day in the morning about 30 min just to get feedback from the team
about the status of soft development. But here I'm not only handle one
project but various project and because of time constraint i push them
all to come in status update meeting and the it's not held every day
but 3 times a week.

[ryzam]

Ada sesiapa dari team saya yang boleh ceritakan pasal Agile, bagaimana
team Mediu execute agile dalam software development

[Khairul]

People always emphasis on the What is agile (or Why Agile is Good) but
forgets on the importance of How to implement Agile. From my point of
view is that agile practitioners (Mediu's team) does little to educate
people on agile and its implementation is very inconsistent. I know
firsthand of the difficulties on how to educate people to use a
process (Wiki, Mantis) in this environment. The resistance rate is
very high. You need a strong supporter or a very convincing argument
(with charts and graphs! People love those).

How does team mediu execute agile?
- Gather around for some discussion
- Sketch and draw on the whiteboard
- Print out the sketches
- Create a user story (in excel) and share it with team members
(through email).
- Create a burndown chart?

I don't know. This is just from what I see, these steps are not
written down anywhere. Agile itself is a very big subject, I don't
know which agile is being practiced, Scrum? Lean? Crystal? XP? Don't
expect people to read unless you can guide. If all you can do to guide
is, "Read this book", that is a very poor leadership and I guarantee
you that people won't read that book.

Come on people, skrg dah ada kertas, ada wiki, tulis la, takkan nak
pass from word of mouth lagi. Bukan zaman hang tuah.

[ryzam]

Thanks, feedback yang bagus, cuma implementation agile di MEDIU
sebenarnya consistent but the way we tackle the problem is not same
for every iteration, memang diakui tiada complete written in
documentation
but agile is about practices not a theory. InsyAllah i will start
thinking to write "How we do agile in MEDIU"

[Khairul]

Thank you for listening. 

I'd like to make clear the 'inconsistent' part. What I mean by consistent is, every morning you get up and go to work. That is consistent. At what time you go to work does not matter (8.00, 8.05, 8.10, 7.30) as long as you go to work. Everyday when you arrive at work, you punch in the access card, it does not matter whether you punch in at the front door, back door, side door but the important part is you punch the card. That is consistent.

[ryzam]

Just for your knowledge i start writing my experience in agile which
your can read here :

http://ryzam.blogspot.com/2009/02/how-i-do-agile-in-my-team-part-1.html